From patchwork Wed Dec 12 23:48:19 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [v3] docbook vs. texlive > 2007 From: Benjamin Kosnik X-Patchwork-Id: 205689 Message-Id: <20121212154819.4d7133d2@oakwood> To: Benjamin De Kosnik Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org Date: Wed, 12 Dec 2012 15:48:19 -0800 Fixup for a typo, on trunk and 4.7 -benjamin 2012-12-12 Benjamin Kosnik * doc/xml/manual/documentation_hacking.xml: Fix validation issue. diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml index 91d16dd..05c05a6 100644 --- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml +++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml @@ -383,6 +383,8 @@ refman.out + + A log of the compilation of the converted LaTeX form to pdf. This is a linear list, from the beginning of the @@ -394,10 +396,20 @@ incorrect, or will have clues at the end of the file with the dump of the memory usage of LaTeX. - + + If the error at hand is not obvious after examination, a + fall-back strategy is to start commenting out the doxygen + input sources, which can be found in + doc/doxygen/user.cfg.in, look for the + INPUT tag. Start by commenting out whole + directories of header files, until the offending header is + identified. Then, read the latex log files to try and find + surround text, and look for that in the offending header. + +
Markup @@ -872,7 +884,7 @@ make XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh" - If the issue is not obvious after examination, or if one + If the error at hand is not obvious after examination, or if one encounters the inscruitable Incomplete \ifmmode error, a fall-back strategy is to start commenting out parts of the XML document (regardless of what