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="http://www.doxygen.org">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="http://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="http://www.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.
293 <section xml:id="doxygen.rules"><info><title>Generating the Doxygen Files</title></info>
296 The following Makefile rules run Doxygen to generate HTML
297 docs, XML docs, XML docs as a single file, PDF docs, and the
298 man pages. These rules are not conditional! If the required
299 tools are not found, or are the wrong versions, the rule may
304 <screen><userinput>make doc-html-doxygen</userinput></screen>
308 <screen><userinput>make doc-xml-doxygen</userinput></screen>
312 <screen><userinput>make doc-xml-single-doxygen</userinput></screen>
316 <screen><userinput>make doc-pdf-doxygen</userinput></screen>
320 <screen><userinput>make doc-man-doxygen</userinput></screen>
324 Generated files are output into separate sub directories of
325 <filename class="directory">doc/doxygen/</filename> in the
326 build directory, based on the output format. For instance, the
327 HTML docs will be in <filename class="directory">doc/doxygen/html</filename>.
331 Careful observers will see that the Makefile rules simply call
332 a script from the source tree, <filename>run_doxygen</filename>, which
333 does the actual work of running Doxygen and then (most
334 importantly) massaging the output files. If for some reason
335 you prefer to not go through the Makefile, you can call this
336 script directly. (Start by passing <literal>--help</literal>.)
340 If you wish to tweak the Doxygen settings, do so by editing
341 <filename>doc/doxygen/user.cfg.in</filename>. Notes to fellow
342 library hackers are written in triple-# comments.
347 <section xml:id="doxygen.debug">
348 <info><title>Debugging Generation</title></info>
351 Sometimes, mis-configuration of the pre-requisite tools can
352 lead to errors when attempting to build the
353 documentation. Here are some of the obvious errors, and ways
354 to fix some common issues that may appear quite cryptic.
358 First, if using a rule like <code>make pdf</code>, try to
359 narrow down the scope of the error to either docbook
360 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
361 doc-pdf-doxygen</code>).
364 Working on the doxygen path only, closely examine the
365 contents of the following build directory: <filename
366 class="directory">build/target/libstdc++-v3/doc/doxygen/latex</filename>.
367 Pay attention to three files enclosed within, annotated as follows.
373 <emphasis>refman.tex</emphasis>
377 The actual latex file, or partial latex file. This is generated
378 via <command>doxygen</command>, and is the LaTeX version of the
379 Doxygen XML file <filename>libstdc++-api.xml</filename>. Go to a specific
380 line, and look at the generated LaTeX, and try to deduce what
381 markup in <filename>libstdc++-api.xml</filename> is causing it.
387 <emphasis>refman.log</emphasis>
391 A log created by <command>latex</command> as it processes the
392 <filename>refman.tex</filename> file. If generating the PDF fails
393 look at the end of this file for errors such as:
395 ! LaTeX Error: File `xtab.sty' not found.
397 This indicates a required TeX package is missing. For the example
398 above the <package>texlive-xtab</package> package needs to be
405 <emphasis>refman.out</emphasis>
409 A log of the compilation of the converted LaTeX form to PDF. This
410 is a linear list, from the beginning of the
411 <filename>refman.tex</filename> file: the last entry of this file
412 should be the end of the LaTeX file. If it is truncated, then you
413 know that the last entry is the last part of the generated LaTeX
414 source file that is valid. Often this file contains an error with
415 a specific line number of <filename>refman.tex</filename> that is
416 incorrect, or will have clues at the end of the file with the dump
417 of the memory usage of LaTeX.
423 If the error at hand is not obvious after examination, a
424 fall-back strategy is to start commenting out the doxygen
425 input sources, which can be found in
426 <filename>doc/doxygen/user.cfg.in</filename>, look for the
427 <literal>INPUT</literal> tag. Start by commenting out whole
428 directories of header files, until the offending header is
429 identified. Then, read the latex log files to try and find
430 surround text, and look for that in the offending header.
435 <section xml:id="doxygen.markup"><info><title>Markup</title></info>
439 In general, libstdc++ files should be formatted according to
440 the rules found in the
441 <link linkend="contrib.coding_style">Coding Standard</link>. Before
442 any doxygen-specific formatting tweaks are made, please try to
443 make sure that the initial formatting is sound.
447 Adding Doxygen markup to a file (informally called
448 <quote>doxygenating</quote>) is very simple. The Doxygen manual can be
450 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.stack.nl/~dimitri/doxygen/download.html#latestman">here</link>.
451 We try to use a very-recent version of Doxygen.
456 <classname>deque</classname>/<classname>vector</classname>/<classname>list</classname>
457 and <classname>std::pair</classname> as examples. For
458 functions, see their member functions, and the free functions
459 in <filename class="headerfile">stl_algobase.h</filename>. Member
460 functions of other container-like types should read similarly to
461 these member functions.
465 Some commentary to accompany
466 the first list in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html">Special
467 Documentation Blocks</link> section of the Doxygen manual:
470 <orderedlist inheritnum="ignore" continuation="restarts">
472 <para>For longer comments, use the Javadoc style...</para>
477 ...not the Qt style. The intermediate *'s are preferred.
483 Use the triple-slash style only for one-line comments (the
484 <quote>brief</quote> mode).
490 This is disgusting. Don't do this.
496 Some specific guidelines:
500 Use the @-style of commands, not the !-style. Please be
501 careful about whitespace in your markup comments. Most of the
502 time it doesn't matter; doxygen absorbs most whitespace, and
503 both HTML and *roff are agnostic about whitespace. However,
504 in <pre> blocks and @code/@endcode sections, spacing can
505 have <quote>interesting</quote> effects.
509 Use either kind of grouping, as
510 appropriate. <filename>doxygroups.cc</filename> exists for this
511 purpose. See <filename class="headerfile">stl_iterator.h</filename>
512 for a good example of the <quote>other</quote> kind of grouping.
516 Please use markup tags like @p and @a when referring to things
517 such as the names of function parameters. Use @e for emphasis
518 when necessary. Use @c to refer to other standard names.
519 (Examples of all these abound in the present code.)
523 Complicated math functions should use the multi-line format.
524 An example from <filename class="headerfile">random.h</filename>:
528 <literallayout class="normal">
530 * @brief A model of a linear congruential random number generator.
533 * x_{i+1}\leftarrow(ax_{i} + c) \bmod m
540 One area of note is the markup required for
541 <literal>@file</literal> markup in header files. Two details
542 are important: for filenames that have the same name in
543 multiple directories, include part of the installed path to
544 disambiguate. For example:
548 <literallayout class="normal">
549 /** @file debug/vector
550 * This file is a GNU debug extension to the Standard C++ Library.
556 The other relevant detail for header files is the use of a
557 libstdc++-specific doxygen alias that helps distinguish
558 between public header files (like <filename class="headerfile">random</filename>)
559 from implementation or private header files (like
560 <filename class="headerfile">bits/c++config.h</filename>.) This alias is spelled
561 <literal>@headername</literal> and can take one or two
562 arguments that detail the public header file or files that
563 should be included to use the contents of the file. All header
564 files that are not intended for direct inclusion must use
565 <literal>headername</literal> in the <literal>file</literal>
570 <literallayout class="normal">
571 /** @file bits/basic_string.h
572 * This is an internal header file, included by other library headers.
573 * Do not attempt to use it directly. @headername{string}
579 Be careful about using certain, special characters when
580 writing Doxygen comments. Single and double quotes, and
581 separators in filenames are two common trouble spots. When in
582 doubt, consult the following table.
585 <table frame="all" xml:id="table.doxygen_cmp">
586 <title>HTML to Doxygen Markup Comparison</title>
588 <tgroup cols="2" align="left" colsep="1" rowsep="1">
589 <colspec colname="c1"/>
590 <colspec colname="c2"/>
595 <entry>Doxygen</entry>
616 <entry><i></entry>
617 <entry>@a word</entry>
621 <entry><b></entry>
622 <entry>@b word</entry>
626 <entry><code></entry>
627 <entry>@c word</entry>
631 <entry><em></entry>
632 <entry>@a word</entry>
636 <entry><em></entry>
637 <entry><em>two words or more</em></entry>
649 <section xml:id="doc.docbook"><info><title>Docbook</title></info>
652 <section xml:id="docbook.prereq"><info><title>Prerequisites</title></info>
655 <table frame="all" xml:id="table.docbook_prereq">
656 <title>Docbook Prerequisites</title>
658 <tgroup cols="3" align="center" colsep="1" rowsep="1">
659 <colspec colname="c1"/>
660 <colspec colname="c2"/>
661 <colspec colname="c3"/>
666 <entry>Version</entry>
667 <entry>Required By</entry>
674 <entry>docbook5-style-xsl</entry>
675 <entry>1.76.1</entry>
680 <entry>xsltproc</entry>
681 <entry>1.1.26</entry>
686 <entry>xmllint</entry>
688 <entry>validation</entry>
692 <entry>dblatex</entry>
694 <entry>pdf output</entry>
698 <entry>pdflatex</entry>
699 <entry>2007-59</entry>
700 <entry>pdf output</entry>
704 <entry>docbook2X</entry>
706 <entry>info output</entry>
710 <entry>epub3 stylesheets</entry>
712 <entry>epub output</entry>
720 Editing the DocBook sources requires an XML editor. Many
721 exist: some notable options
722 include <command>emacs</command>, <application>Kate</application>,
723 or <application>Conglomerate</application>.
727 Some editors support special <quote>XML Validation</quote>
728 modes that can validate the file as it is
729 produced. Recommended is the <command>nXML Mode</command>
730 for <command>emacs</command>.
734 Besides an editor, additional DocBook files and XML tools are
739 Access to the DocBook 5.0 stylesheets and schema is required. The
740 stylesheets are usually packaged by vendor, in something
741 like <filename>docbook5-style-xsl</filename>. To exactly match
742 generated output, please use a version of the stylesheets
744 to <filename>docbook5-style-xsl-1.75.2-3</filename>. The
745 installation directory for this package corresponds to
746 the <literal>XSL_STYLE_DIR</literal>
747 in <filename>doc/Makefile.am</filename> and defaults
748 to <filename class="directory">/usr/share/sgml/docbook/xsl-ns-stylesheets</filename>.
752 For processing XML, an XSLT processor and some style
753 sheets are necessary. Defaults are <command>xsltproc</command>
754 provided by <filename>libxslt</filename>.
758 For validating the XML document, you'll need
759 something like <command>xmllint</command> and access to the
760 relevant DocBook schema. These are provided
761 by a vendor package like <filename>libxml2</filename> and <filename>docbook5-schemas-5.0-4</filename>
765 For PDF output, something that transforms valid Docbook XML to PDF is
766 required. Possible solutions include <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://dblatex.sourceforge.net">dblatex</link>,
767 <command>xmlto</command>, or <command>prince</command>. Of
768 these, <command>dblatex</command> is the default.
769 Please consult the <email>libstdc++@gcc.gnu.org</email> list when
770 preparing printed manuals for current best practice and
775 For Texinfo output, something that transforms valid Docbook
776 XML to Texinfo is required. The default choice is <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://docbook2x.sourceforge.net/">docbook2X</link>.
780 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/IDPF/epubcheck">epubcheck</link> is necessary.
784 <section xml:id="docbook.rules"><info><title>Generating the DocBook Files</title></info>
788 The following Makefile rules generate (in order): an HTML
789 version of all the DocBook documentation, a PDF version of the
790 same, and a single XML document. These rules are not
791 conditional! If the required tools are not found, or are the
792 wrong versions, the rule may end in an error.
796 <screen><userinput>make doc-html-docbook</userinput></screen>
800 <screen><userinput>make doc-pdf-docbook</userinput></screen>
804 <screen><userinput>make doc-xml-single-docbook</userinput></screen>
808 Generated files are output into separate sub directores of
809 <filename class="directory">doc/docbook/</filename> in the
810 build directory, based on the output format. For instance, the
811 HTML docs will be in <filename
812 class="directory">doc/docbook/html</filename>.
816 If the Docbook stylesheets are installed in a custom location,
817 one can use the variable <literal>XSL_STYLE_DIR</literal> to
818 override the Makefile defaults. For example:
823 make <literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal> doc-html-docbook
829 <section xml:id="docbook.debug">
830 <info><title>Debugging Generation</title></info>
833 Sometimes, mis-configuration of the pre-requisite tools can
834 lead to errors when attempting to build the
835 documentation. Here are some of the obvious errors, and ways
836 to fix some common issues that may appear quite cryptic.
840 First, if using a rule like <code>make pdf</code>, try to
841 narrow down the scope of the error to either docbook
842 (<code>make doc-pdf-docbook</code>) or doxygen (<code>make
843 doc-pdf-doxygen</code>).
847 Working on the docbook path only, closely examine the
848 contents of the following build directory:
849 <filename class="directory">build/target/libstdc++-v3/doc/docbook/latex</filename>.
850 Pay attention to three files enclosed within, annotated as follows.
857 <emphasis>spine.tex</emphasis>
861 The actual latex file, or partial latex file. This is generated
862 via <command>dblatex</command>, and is the LaTeX version of the
863 DocBook XML file <filename>spine.xml</filename>. Go to a specific
864 line, and look at the generated LaTeX, and try to deduce what
865 markup in <filename>spine.xml</filename> is causing it.
871 <emphasis>spine.out</emphasis>
875 A log of the conversion from the XML form to the LaTeX form. This
876 is a linear list, from the beginning of the
877 <filename>spine.xml</filename> file: the last entry of this file
878 should be the end of the DocBook file. If it is truncated, then
879 you know that the last entry is the last part of the XML source
880 file that is valid. The error is after this point.
887 <emphasis>spine.log</emphasis>
891 A log of the compilation of the converted LaTeX form to pdf. This
892 is a linear list, from the beginning of the
893 <filename>spine.tex</filename> file: the last entry of this file
894 should be the end of the LaTeX file. If it is truncated, then you
895 know that the last entry is the last part of the generated LaTeX
896 source file that is valid. Often this file contains an error with
897 a specific line number of <filename>spine.tex</filename> that is
905 If the error at hand is not obvious after examination, or if one
906 encounters the inscruitable <quote>Incomplete
907 \ifmmode</quote> error, a fall-back strategy is to start
908 commenting out parts of the XML document (regardless of what
909 this does to over-all document validity). Start by
910 commenting out each of the largest parts of the
911 <filename>spine.xml</filename> file, section by section,
912 until the offending section is identified.
918 <section xml:id="docbook.validation"><info><title>Editing and Validation</title></info>
921 After editing the xml sources, please make sure that the XML
922 documentation and markup is still valid. This can be
923 done easily, with the following validation rule:
927 <userinput>make doc-xml-validate-docbook</userinput>
931 This is equivalent to doing:
936 xmllint --noout --valid <filename>xml/index.xml</filename>
941 Please note that individual sections and chapters of the
942 manual can be validated by substituting the file desired for
943 <filename>xml/index.xml</filename> in the command
944 above. Reducing scope in this manner can be helpful when
945 validation on the entire manual fails.
949 All Docbook xml sources should always validate. No excuses!
954 <section xml:id="docbook.examples"><info><title>File Organization and Basics</title></info>
957 <literallayout class="normal">
958 <emphasis>Which files are important</emphasis>
960 All Docbook files are in the directory
963 Inside this directory, the files of importance:
964 spine.xml - index to documentation set
965 manual/spine.xml - index to manual
966 manual/*.xml - individual chapters and sections of the manual
967 faq.xml - index to FAQ
968 api.xml - index to source level / API
970 All *.txml files are template xml files, i.e., otherwise empty files with
971 the correct structure, suitable for filling in with new information.
973 <emphasis>Canonical Writing Style</emphasis>
977 member function template
978 (via C++ Templates, Vandevoorde)
980 class in namespace std: allocator, not std::allocator
982 header file: iostream, not <iostream>
985 <emphasis>General structure</emphasis>
1020 <section xml:id="docbook.markup"><info><title>Markup By Example</title></info>
1024 Complete details on Docbook markup can be found in the
1025 <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://tdg.docbook.org/tdg/5.0/ref-elements.html">DocBook Element Reference</link>.
1026 An incomplete reference for HTML to Docbook conversion is
1027 detailed in the table below.
1030 <table frame="all" xml:id="table.docbook_cmp">
1031 <title>HTML to Docbook XML Markup Comparison</title>
1033 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1034 <colspec colname="c1"/>
1035 <colspec colname="c2"/>
1040 <entry>Docbook</entry>
1046 <entry><p></entry>
1047 <entry><para></entry>
1050 <entry><pre></entry>
1051 <entry><computeroutput>, <programlisting>,
1052 <literallayout></entry>
1055 <entry><ul></entry>
1056 <entry><itemizedlist></entry>
1059 <entry><ol></entry>
1060 <entry><orderedlist></entry>
1063 <entry><il></entry>
1064 <entry><listitem></entry>
1067 <entry><dl></entry>
1068 <entry><variablelist></entry>
1071 <entry><dt></entry>
1072 <entry><term></entry>
1075 <entry><dd></entry>
1076 <entry><listitem></entry>
1080 <entry><a href=""></entry>
1081 <entry><ulink url=""></entry>
1084 <entry><code></entry>
1085 <entry><literal>, <programlisting></entry>
1088 <entry><strong></entry>
1089 <entry><emphasis></entry>
1092 <entry><em></entry>
1093 <entry><emphasis></entry>
1097 <entry><quote></entry>
1104 And examples of detailed markup for which there are no real HTML
1105 equivalents are listed in the table below.
1108 <table frame="all" xml:id="table.docbook_elem">
1109 <title>Docbook XML Element Use</title>
1111 <tgroup cols="2" align="left" colsep="1" rowsep="1">
1112 <colspec colname="c1"/>
1113 <colspec colname="c2"/>
1117 <entry>Element</entry>
1124 <entry><structname></entry>
1125 <entry><structname>char_traits</structname></entry>
1128 <entry><classname></entry>
1129 <entry><classname>string</classname></entry>
1132 <entry><function></entry>
1134 <para><function>clear()</function></para>
1135 <para><function>fs.clear()</function></para>
1139 <entry><type></entry>
1140 <entry><type>long long</type></entry>
1143 <entry><varname></entry>
1144 <entry><varname>fs</varname></entry>
1147 <entry><literal></entry>
1149 <para><literal>-Weffc++</literal></para>
1150 <para><literal>rel_ops</literal></para>
1154 <entry><constant></entry>
1156 <para><constant>_GNU_SOURCE</constant></para>
1157 <para><constant>3.0</constant></para>
1161 <entry><command></entry>
1162 <entry><command>g++</command></entry>
1165 <entry><errortext></entry>
1166 <entry><errortext>In instantiation of</errortext></entry>
1169 <entry><filename></entry>
1171 <para><filename class="headerfile">ctype.h</filename></para>
1172 <para><filename class="directory">/home/gcc/build</filename></para>
1173 <para><filename class="libraryfile">libstdc++.so</filename></para>