ftmemsim-valgrind/docs/xml/tech-docs.xml
Mark Wielaard a489f40f78 docs: Make sure all elements that need it have an id tag.
When generating HTML it is useful if every element that can be referenced
has a stable id. If it doesn't a random one is generated which makes it
harder to link to parts of the manual on the website. It also generates
spurious diffs. Explicitly add an id tag for the sect2 and sect3 elements
in dh-manual, a unique id for each legalnotice element and for each
FAQ question and answer.
2020-06-09 11:23:46 +02:00

28 lines
1.0 KiB
XML

<?xml version="1.0"?> <!-- -*- sgml -*- -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"
[ <!ENTITY % vg-entities SYSTEM "vg-entities.xml"> %vg-entities; ]>
<book id="tech-docs" xreflabel="Valgrind Technical Documentation">
<bookinfo>
<title>Valgrind Technical Documentation</title>
<releaseinfo>&rel-type; &rel-version; &rel-date;</releaseinfo>
<copyright>
<year>&vg-lifespan;</year>
<holder><ulink url="&vg-devs-url;">Valgrind Developers</ulink></holder>
</copyright>
<legalnotice id="tech-legal">
<para>Email: <ulink url="mailto:&vg-vemail;">&vg-vemail;</ulink></para>
</legalnotice>
</bookinfo>
<xi:include href="design-impl.xml" parse="xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="manual-writing-tools.xml" parse="xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="../../callgrind/docs/cl-format.xml" parse="xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
</book>