1 <section xmlns="http://docbook.org/ns/docbook" version="5.0"
2 xml:id="appendix.porting.doc" xreflabel="Documentation Hacking">
3 <?dbhtml filename="documentation_hacking.html"?>
5 <info><title>Writing and Generating Documentation</title>
7 <keyword>ISO C++</keyword>
8 <keyword>documentation</keyword>
9 <keyword>style</keyword>
10 <keyword>docbook</keyword>
11 <keyword>doxygen</keyword>
15 <section xml:id="doc.intro">
17 <title>Introduction</title>
20 Documentation for the GNU C++ Library is created from three
21 independent sources: a manual, a FAQ, and an API reference.
24 The sub-directory <filename class="directory">doc</filename>
25 within the main source directory contains
26 <filename>Makefile.am</filename> and
27 <filename>Makefile.in</filename>, which provide rules for
28 generating documentation, described in excruciating detail
29 below. The <filename class="directory">doc</filename>
30 sub-directory also contains three directories: <filename
31 class="directory">doxygen</filename>, which contains scripts and
32 fragments for <command>doxygen</command>, <filename
33 class="directory">html</filename>, which contains an html
34 version of the manual, and <filename
35 class="directory">xml</filename>, which contains an xml version
39 Diverging from established documentation conventions in the rest
40 of the GCC project, libstdc++ does not use Texinfo as a markup
41 language. Instead, Docbook is used to create the manual and the
42 FAQ, and Doxygen is used to construct the API
43 reference. Although divergent, this conforms to the GNU Project
44 recommendations as long as the output is of sufficient quality,
46 <link xmlns:xlink="http://www.w3.org/1999/xlink"
47 xlink:href="http://www.gnu.org/prep/standards/standards.html#Documentation">
52 <section xml:id="doc.generation">
54 <title>Generating Documentation</title>
58 Certain Makefile rules are required by the GNU Coding
59 Standards. These standard rules generate HTML, PDF, XML, or man
60 files. For each of the generative rules, there is an additional
61 install rule that is used to install any generated documentation
62 files into the prescribed installation directory. Files are
63 installed into <filename class="directory">share/doc</filename>
64 or <filename class="directory">share/man</filename> directories.
68 The standard Makefile rules are conditionally supported, based
69 on the results of examining the host environment for
70 prerequisites at configuration time. If requirements are not
71 found, the rule is aliased to a dummy rule that does nothing,
72 and produces no documentation. If the requirements are found,
73 the rule forwards to a private rule that produces the requested
78 For more details on what prerequisites were found and where,
79 please consult the file <filename>config.log</filename> in the
80 libstdc++ build directory. Compare this log to what is expected
81 for the relevant Makefile conditionals:
82 <literal>BUILD_INFO</literal>, <literal>BUILD_XML</literal>,
83 <literal>BUILD_HTML</literal>, <literal>BUILD_MAN</literal>,
84 <literal>BUILD_PDF</literal>, and <literal>BUILD_EPUB</literal>.
88 Supported Makefile rules:
94 <emphasis>make html</emphasis>
97 <emphasis>make install-html</emphasis>
101 Generates multi-page HTML documentation, and installs it
102 in the following directories:
105 <filename>doc/libstdc++/libstdc++-api.html</filename>
108 <filename>doc/libstdc++/libstdc++-manual.html</filename>
115 <emphasis>make pdf</emphasis>
118 <emphasis>make install-pdf</emphasis>
122 Generates indexed PDF documentation, and installs it as
126 <filename>doc/libstdc++/libstdc++-api.pdf</filename>
129 <filename>doc/libstdc++/libstdc++-manual.pdf</filename>
136 <emphasis>make man</emphasis>
139 <emphasis>make install-man</emphasis>
143 Generates man pages, and installs it in the following directory:
146 <filename class="directory">man/man3/</filename>
149 The generated man pages are namespace-qualified, so to look at
150 the man page for <classname>vector</classname>, one would use
151 <command>man std::vector</command>.
158 <emphasis>make epub</emphasis>
161 <emphasis>make install-epub</emphasis>
165 Generates documentation in the ebook/portable electronic
166 reader format called Epub, and installs it as the
170 <filename>doc/libstdc++/libstdc++-manual.epub</filename>
177 <emphasis>make xml</emphasis>
180 <emphasis>make install-xml</emphasis>
184 Generates single-file XML documentation, and installs it
185 as the following files:
188 <filename>doc/libstdc++/libstdc++-api-single.xml</filename>
191 <filename>doc/libstdc++/libstdc++-manual-single.xml</filename>
198 Makefile rules for several other formats are explicitly not
199 supported, and are always aliased to dummy rules. These
200 unsupported formats are: <emphasis>info</emphasis>,
201 <emphasis>ps</emphasis>, and <emphasis>dvi</emphasis>.
205 <section xml:id="doc.doxygen"><info><title>Doxygen</title></info>
207 <section xml:id="doxygen.prereq"><info><title>Prerequisites</title></info>
209 <table frame="all" xml:id="table.doxygen_prereq">
210 <title>Doxygen Prerequisites</title>
212 <tgroup cols="3" align="center" colsep="1" rowsep="1">
213 <colspec colname="c1"/>
214 <colspec colname="c2"/>
215 <colspec colname="c3"/>
220 <entry>Version</entry>
221 <entry>Required By</entry>
228 <entry>coreutils</entry>
240 <entry>doxygen</entry>
241 <entry>1.7.6.1</entry>
246 <entry>graphviz</entry>
248 <entry>graphical hierarchies</entry>
252 <entry>pdflatex</entry>
253 <entry>2007-59</entry>
254 <entry>pdf output</entry>
263 Prerequisite tools are Bash 2.0 or later,
264 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.doxygen.nl">Doxygen</link>, and
265 the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.gnu.org/software/coreutils/">GNU
266 coreutils</link>. (GNU versions of find, xargs, and possibly
267 sed and grep are used, just because the GNU versions make
272 To generate the pretty pictures and hierarchy
274 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.graphviz.org">Graphviz</link> package
275 will need to be installed. For PDF
276 output, <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://tug.org/applications/pdftex/">
277 pdflatex</link> is required as well as a number of TeX packages
278 such as <package>texlive-xtab</package> and
279 <package>texlive-tocloft</package>.
283 Be warned the PDF file generated via doxygen is extremely
284 large. At last count, the PDF file is over three thousand
285 pages. Generating this document taxes the underlying TeX
286 formatting system, and will require the expansion of TeX's memory
287 capacity. Specifically, the <literal>pool_size</literal>
288 variable in the configuration file <filename>texmf.cnf</filename> may
289 need to be increased by a minimum factor of two. Alternatively, using
290 <userinput>LATEX_CMD=lualatex</userinput> might allow the docs to be
291 build without running out of memory.
295 <section xml:id="doxygen.rules"><info><title>Generating the Doxygen Files</title></info>
298 The following Makefile rules run Doxygen to generate HTML
299 docs, XML docs, XML docs as a single file, PDF docs, and the
300 man pages. These rules are not conditional! If the required
301 tools are not found, or are the wrong versions, the rule may
306 <screen><userinput>make doc-html-doxygen</userinput></screen>
310 <screen><userinput>make doc-xml-doxygen</userinput></screen>
314 <screen><userinput>make doc-xml-single-doxygen</userinput></screen>
318 <screen><userinput>make doc-pdf-doxygen</userinput></screen>
322 <screen><userinput>make doc-man-doxygen</userinput></screen>
326 Generated files are output into separate sub directories of
327 <filename class="directory">doc/doxygen/</filename> in the
328 build directory, based on the output format. For instance, the
329 HTML docs will be in <filename class="directory">doc/doxygen/html</filename>.
333 Careful observers will see that the Makefile rules simply call
334 a script from the source tree, <filename>run_doxygen</filename>, which
335 does the actual work of running Doxygen and then (most
336 importantly) massaging the output files. If for some reason
337 you prefer to not go through the Makefile, you can call this
338 script directly. (Start by passing <literal>--help</literal>.)
342 If you wish to tweak the Doxygen settings, do so by editing
343 <filename>doc/doxygen/user.cfg.in</filename>. Notes to fellow
344 library hackers are written in triple-# comments.
349 <section xml:id="doxygen.debug">
350 <info><title>Debugging Generation</title></info>
353 Sometimes, mis-configuration of the pre-requisite tools can
354 lead to errors when attempting to build the
355 documentation. Here are some of the obvious errors, and ways
356 to fix some common issues that may appear quite cryptic.
360 First, if using a rule like <code>make pdf</code>, try to
361 narrow down the scope of the error to either docbook
362 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
363 doc-pdf-doxygen</code>).
366 Working on the doxygen path only, closely examine the
367 contents of the following build directory: <filename
368 class="directory">build/target/libstdc++-v3/doc/doxygen/latex</filename>.
369 Pay attention to three files enclosed within, annotated as follows.
375 <emphasis>refman.tex</emphasis>
379 The actual latex file, or partial latex file. This is generated
380 via <command>doxygen</command>, and is the LaTeX version of the
381 Doxygen XML file <filename>libstdc++-api.xml</filename>. Go to a specific
382 line, and look at the generated LaTeX, and try to deduce what
383 markup in <filename>libstdc++-api.xml</filename> is causing it.
389 <emphasis>refman.log</emphasis>
393 A log created by <command>latex</command> as it processes the
394 <filename>refman.tex</filename> file. If generating the PDF fails
395 look at the end of this file for errors such as:
397 ! LaTeX Error: File `xtab.sty' not found.
399 This indicates a required TeX package is missing. For the example
400 above the <package>texlive-xtab</package> package needs to be
407 <emphasis>refman.out</emphasis>
411 A log of the compilation of the converted LaTeX form to PDF. This
412 is a linear list, from the beginning of the
413 <filename>refman.tex</filename> file: the last entry of this file
414 should be the end of the LaTeX file. If it is truncated, then you
415 know that the last entry is the last part of the generated LaTeX
416 source file that is valid. Often this file contains an error with
417 a specific line number of <filename>refman.tex</filename> that is
418 incorrect, or will have clues at the end of the file with the dump
419 of the memory usage of LaTeX.
425 If the error at hand is not obvious after examination, a
426 fall-back strategy is to start commenting out the doxygen
427 input sources, which can be found in
428 <filename>doc/doxygen/user.cfg.in</filename>, look for the
429 <literal>INPUT</literal> tag. Start by commenting out whole
430 directories of header files, until the offending header is
431 identified. Then, read the latex log files to try and find
432 surround text, and look for that in the offending header.
437 <section xml:id="doxygen.markup"><info><title>Markup</title></info>
441 In general, libstdc++ files should be formatted according to
442 the rules found in the
443 <link linkend="contrib.coding_style">Coding Standard</link>. Before
444 any doxygen-specific formatting tweaks are made, please try to
445 make sure that the initial formatting is sound.
449 Adding Doxygen markup to a file (informally called
450 <quote>doxygenating</quote>) is very simple. See the
451 <link xmlns:xlink="http://www.w3.org/1999/xlink"
452 xlink:href="https://www.doxygen.nl/download.html#latestman">Doxygen
453 manual</link> for details.
454 We try to use a very-recent version of Doxygen.
459 <classname>deque</classname>/<classname>vector</classname>/<classname>list</classname>
460 and <classname>std::pair</classname> as examples. For
461 functions, see their member functions, and the free functions
462 in <filename class="headerfile">stl_algobase.h</filename>. Member
463 functions of other container-like types should read similarly to
464 these member functions.
468 Some commentary to accompany
469 the first list in the <link xmlns:xlink="http://www.w3.org/1999/xlink"
470 xlink:href="https://www.doxygen.nl/manual/docblocks.html">Special
471 Documentation Blocks</link> section of the Doxygen manual:
474 <orderedlist inheritnum="ignore" continuation="restarts">
476 <para>For longer comments, use the Javadoc style...</para>
481 ...not the Qt style. The intermediate *'s are preferred.
487 Use the triple-slash style only for one-line comments (the
488 <quote>brief</quote> mode).
494 This is disgusting. Don't do this.
500 Some specific guidelines:
504 Use the @-style of commands, not the !-style. Please be
505 careful about whitespace in your markup comments. Most of the
506 time it doesn't matter; doxygen absorbs most whitespace, and
507 both HTML and *roff are agnostic about whitespace. However,
508 in <pre> blocks and @code/@endcode sections, spacing can
509 have <quote>interesting</quote> effects.
513 Use either kind of grouping, as
514 appropriate. <filename>doxygroups.cc</filename> exists for this
515 purpose. See <filename class="headerfile">stl_iterator.h</filename>
516 for a good example of the <quote>other</quote> kind of grouping.
520 Markdown can be used for formatting text. Doxygen is configured to
521 support this, and it is a good compromise between readable comments
522 in the C++ source and nice formatting in the generated HTML.
523 Please format the names of function parameters in either code font
524 or italics. Use underscores or @e for emphasis when necessary.
525 Use backticks or @c to refer to other standard names.
526 (Examples of all these abound in the present code.)
530 Complicated math functions should use the multi-line format.
531 An example from <filename class="headerfile">random.h</filename>:
535 <literallayout class="normal">
537 * @brief A model of a linear congruential random number generator.
540 * x_{i+1}\leftarrow(ax_{i} + c) \bmod m
547 One area of note is the markup required for
548 <literal>@file</literal> markup in header files. Two details
549 are important: for filenames that have the same name in
550 multiple directories, include part of the installed path to
551 disambiguate. For example:
555 <literallayout class="normal">
556 /** @file debug/vector
557 * This file is a GNU debug extension to the Standard C++ Library.
563 The other relevant detail for header files is the use of a
564 libstdc++-specific doxygen alias that helps distinguish
565 between public header files (like <filename class="headerfile">random</filename>)
566 from implementation or private header files (like
567 <filename class="headerfile">bits/c++config.h</filename>.) This alias is spelled
568 <literal>@headername</literal> and can take one or two
569 arguments that detail the public header file or files that
570 should be included to use the contents of the file. All header
571 files that are not intended for direct inclusion must use
572 <literal>headername</literal> in the <literal>file</literal>
577 <literallayout class="normal">
578 /** @file bits/basic_string.h
579 * This is an internal header file, included by other library headers.
580 * Do not attempt to use it directly. @headername{string}
586 Be careful about using certain, special characters when
587 writing Doxygen comments. Single and double quotes, and
588 separators in filenames are two common trouble spots. When in
589 doubt, consult the following table.
592 <table frame="all" xml:id="table.doxygen_cmp">
593 <title>HTML to Doxygen Markup Comparison</title>
595 <tgroup cols="2" align="left" colsep="1" rowsep="1">
596 <colspec colname="c1"/>
597 <colspec colname="c2"/>
602 <entry>Doxygen</entry>
603 <entry>Markdown</entry>
627 <entry><i></entry>
628 <entry>@a word</entry>
629 <entry>_word_ or *word*</entry>
633 <entry><b></entry>
634 <entry>@b word</entry>
635 <entry>**word** or __word__</entry>
639 <entry><code></entry>
640 <entry>@c word</entry>
641 <entry>`word`</entry>
645 <entry><em></entry>
646 <entry>@a word</entry>
647 <entry>_word_ or *word*</entry>
651 <entry><em></entry>
652 <entry><em>two words or more</em></entry>
653 <entry>_two words or more_</entry>
665 <section xml:id="doc.docbook"><info><title>Docbook</title></info>
668 <section xml:id="docbook.prereq"><info><title>Prerequisites</title></info>
671 <table frame="all" xml:id="table.docbook_prereq">
672 <title>Docbook Prerequisites</title>
674 <tgroup cols="3" align="center" colsep="1" rowsep="1">
675 <colspec colname="c1"/>
676 <colspec colname="c2"/>
677 <colspec colname="c3"/>
682 <entry>Version</entry>
683 <entry>Required By</entry>
690 <entry>docbook5-style-xsl</entry>
691 <entry>1.76.1</entry>
696 <entry>xsltproc</entry>
697 <entry>1.1.26</entry>
702 <entry>xmllint</entry>
704 <entry>validation</entry>
708 <entry>dblatex</entry>
710 <entry>pdf output</entry>
714 <entry>pdflatex</entry>
715 <entry>2007-59</entry>
716 <entry>pdf output</entry>
720 <entry>docbook2X</entry>
722 <entry>info output</entry>
726 <entry>epub3 stylesheets</entry>
728 <entry>epub output</entry>
736 An XML editor is recommended for editing the DocBook sources. Many
737 exist: some notable options
738 include <command>emacs</command>, <application>Kate</application>,
739 or <application>Conglomerate</application>.
743 Some editors support special <quote>XML Validation</quote>
744 modes that can validate the file as it is
745 produced. Recommended is the <command>nXML Mode</command>
746 for <command>emacs</command>.
750 Besides an editor, additional DocBook files and XML tools are
755 Access to the DocBook 5.0 stylesheets and schema is required. The
756 stylesheets are usually packaged by vendor, in something
757 like <filename>docbook5-style-xsl</filename>. To exactly match
758 generated output, please use a version of the stylesheets
760 to <filename>docbook5-style-xsl-1.75.2-3</filename>. The
761 installation directory for this package corresponds to
762 the <literal>XSL_STYLE_DIR</literal>
763 in <filename>doc/Makefile.am</filename> and defaults
764 to <filename class="directory">/usr/share/sgml/docbook/xsl-ns-stylesheets</filename>.
768 For processing XML, an XSLT processor and some style
769 sheets are necessary. Defaults are <command>xsltproc</command>
770 provided by <filename>libxslt</filename>.
774 For validating the XML document, you'll need
775 something like <command>xmllint</command> and access to the
776 relevant DocBook schema. These are provided
777 by a vendor package like <filename>libxml2</filename> and <filename>docbook5-schemas-5.0-4</filename>
781 For PDF output, something that transforms valid Docbook XML to PDF is
782 required. Possible solutions include <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://dblatex.sourceforge.net">dblatex</link>,
783 <command>xmlto</command>, or <command>prince</command>. Of
784 these, <command>dblatex</command> is the default.
785 Please consult the <email>libstdc++@gcc.gnu.org</email> list when
786 preparing printed manuals for current best practice and
791 For Texinfo output, something that transforms valid Docbook
792 XML to Texinfo is required. The default choice is <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://docbook2x.sourceforge.net/">docbook2X</link>.
796 For epub output, the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://sourceforge.net/projects/docbook/files/epub3/">stylesheets</link> for EPUB3 are required. These stylesheets are still in development. To validate the created file, <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://github.com/w3c/epubcheck">epubcheck</link> is necessary.
800 <section xml:id="docbook.rules"><info><title>Generating the DocBook Files</title></info>
804 The following Makefile rules generate (in order): an HTML
805 version of all the DocBook documentation, a PDF version of the
806 same, and a single XML document. These rules are not
807 conditional! If the required tools are not found, or are the
808 wrong versions, the rule may end in an error.
812 <screen><userinput>make doc-html-docbook</userinput></screen>
816 <screen><userinput>make doc-pdf-docbook</userinput></screen>
820 <screen><userinput>make doc-xml-single-docbook</userinput></screen>
824 Generated files are output into separate sub-directores of
825 <filename class="directory">doc/docbook/</filename> in the
826 build directory, based on the output format. For instance, the
827 HTML docs will be in <filename
828 class="directory">doc/docbook/html</filename>.
832 The <userinput>doc-html-docbook-regenerate</userinput> target will
833 generate the HTML files and copy them back to the libstdc++ source tree.
834 This can be used to update the HTML files that are checked in to
839 If the Docbook stylesheets are installed in a custom location,
840 one can use the variable <literal>XSL_STYLE_DIR</literal> to
841 override the Makefile defaults. For example:
846 make <literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal> doc-html-docbook
852 <section xml:id="docbook.debug">
853 <info><title>Debugging Generation</title></info>
856 Sometimes, mis-configuration of the pre-requisite tools can
857 lead to errors when attempting to build the
858 documentation. Here are some of the obvious errors, and ways
859 to fix some common issues that may appear quite cryptic.
863 First, if using a rule like <code>make pdf</code>, try to
864 narrow down the scope of the error to either docbook
865 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
866 doc-pdf-doxygen</code>).
870 Working on the docbook path only, closely examine the
871 contents of the following build directory:
872 <filename class="directory">build/target/libstdc++-v3/doc/docbook/latex</filename>.
873 Pay attention to three files enclosed within, annotated as follows.
880 <emphasis>spine.tex</emphasis>
884 The actual latex file, or partial latex file. This is generated
885 via <command>dblatex</command>, and is the LaTeX version of the
886 DocBook XML file <filename>spine.xml</filename>. Go to a specific
887 line, and look at the generated LaTeX, and try to deduce what
888 markup in <filename>spine.xml</filename> is causing it.
894 <emphasis>spine.out</emphasis>
898 A log of the conversion from the XML form to the LaTeX form. This
899 is a linear list, from the beginning of the
900 <filename>spine.xml</filename> file: the last entry of this file
901 should be the end of the DocBook file. If it is truncated, then
902 you know that the last entry is the last part of the XML source
903 file that is valid. The error is after this point.
910 <emphasis>spine.log</emphasis>
914 A log of the compilation of the converted LaTeX form to pdf. This
915 is a linear list, from the beginning of the
916 <filename>spine.tex</filename> file: the last entry of this file
917 should be the end of the LaTeX file. If it is truncated, then you
918 know that the last entry is the last part of the generated LaTeX
919 source file that is valid. Often this file contains an error with
920 a specific line number of <filename>spine.tex</filename> that is
928 If the error at hand is not obvious after examination, or if one
929 encounters the inscruitable <quote>Incomplete
930 \ifmmode</quote> error, a fall-back strategy is to start
931 commenting out parts of the XML document (regardless of what
932 this does to over-all document validity). Start by
933 commenting out each of the largest parts of the
934 <filename>spine.xml</filename> file, section by section,
935 until the offending section is identified.
941 <section xml:id="docbook.validation"><info><title>Editing and Validation</title></info>
944 After editing the xml sources, please make sure that the XML
945 documentation and markup is still valid. This can be
946 done easily, with the following validation rule:
950 <userinput>make doc-xml-validate-docbook</userinput>
954 This is equivalent to doing:
959 xmllint --noout --valid <filename>xml/index.xml</filename>
964 Please note that individual sections and chapters of the
965 manual can be validated by substituting the file desired for
966 <filename>xml/index.xml</filename> in the command
967 above. Reducing scope in this manner can be helpful when
968 validation on the entire manual fails.
972 All Docbook xml sources should always validate. No excuses!
977 <section xml:id="docbook.examples"><info><title>File Organization and Basics</title></info>
980 <literallayout class="normal">
981 <emphasis>Which files are important</emphasis>
983 All Docbook files are in the directory
986 Inside this directory, the files of importance:
987 spine.xml - index to documentation set
988 manual/spine.xml - index to manual
989 manual/*.xml - individual chapters and sections of the manual
990 faq.xml - index to FAQ
991 api.xml - index to source level / API
993 All *.txml files are template xml files, i.e., otherwise empty files with
994 the correct structure, suitable for filling in with new information.
996 <emphasis>Canonical Writing Style</emphasis>
1000 member function template
1001 (via C++ Templates, Vandevoorde)
1003 class in namespace std: allocator, not std::allocator
1005 header file: iostream, not <iostream>
1008 <emphasis>General structure</emphasis>
1043 <section xml:id="docbook.markup"><info><title>Markup By Example</title></info>
1047 Complete details on Docbook markup can be found in the
1048 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://tdg.docbook.org/tdg/5.0/ref-elements.html">DocBook Element Reference</link>.
1049 An incomplete reference for HTML to Docbook conversion is
1050 detailed in the table below.
1053 <table frame="all" xml:id="table.docbook_cmp">
1054 <title>HTML to Docbook XML Markup Comparison</title>
1056 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1057 <colspec colname="c1"/>
1058 <colspec colname="c2"/>
1063 <entry>Docbook</entry>
1069 <entry><p></entry>
1070 <entry><para></entry>
1073 <entry><pre></entry>
1074 <entry><computeroutput>, <programlisting>,
1075 <literallayout></entry>
1078 <entry><ul></entry>
1079 <entry><itemizedlist></entry>
1082 <entry><ol></entry>
1083 <entry><orderedlist></entry>
1086 <entry><il></entry>
1087 <entry><listitem></entry>
1090 <entry><dl></entry>
1091 <entry><variablelist></entry>
1094 <entry><dt></entry>
1095 <entry><term></entry>
1098 <entry><dd></entry>
1099 <entry><listitem></entry>
1103 <entry><a href=""></entry>
1104 <entry><ulink url=""></entry>
1107 <entry><code></entry>
1108 <entry><literal>, <programlisting></entry>
1111 <entry><strong></entry>
1112 <entry><emphasis></entry>
1115 <entry><em></entry>
1116 <entry><emphasis></entry>
1120 <entry><quote></entry>
1127 And examples of detailed markup for which there are no real HTML
1128 equivalents are listed in the table below.
1131 <table frame="all" xml:id="table.docbook_elem">
1132 <title>Docbook XML Element Use</title>
1134 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1135 <colspec colname="c1"/>
1136 <colspec colname="c2"/>
1140 <entry>Element</entry>
1147 <entry><structname></entry>
1148 <entry><structname>char_traits</structname></entry>
1151 <entry><classname></entry>
1152 <entry><classname>string</classname></entry>
1155 <entry><function></entry>
1157 <para><function>clear()</function></para>
1158 <para><function>fs.clear()</function></para>
1162 <entry><type></entry>
1163 <entry><type>long long</type></entry>
1166 <entry><varname></entry>
1167 <entry><varname>fs</varname></entry>
1170 <entry><literal></entry>
1172 <para><literal>-Weffc++</literal></para>
1173 <para><literal>rel_ops</literal></para>
1177 <entry><constant></entry>
1179 <para><constant>_GNU_SOURCE</constant></para>
1180 <para><constant>3.0</constant></para>
1184 <entry><command></entry>
1185 <entry><command>g++</command></entry>
1188 <entry><errortext></entry>
1189 <entry><errortext>In instantiation of</errortext></entry>
1192 <entry><filename></entry>
1194 <para><filename class="headerfile">ctype.h</filename></para>
1195 <para><filename class="directory">/home/gcc/build</filename></para>
1196 <para><filename class="libraryfile">libstdc++.so</filename></para>