From: Paul V. <pau...@us...> - 2009-10-26 00:10:07
|
Update of /cvsroot/firebird/manual/src/docs/firebirddocs In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv8965/src/docs/firebirddocs Modified Files: docbuilding-howto.xml Log Message: Fixed some typos and changed wording; see Revision History (rev. 1.6.1) Index: docbuilding-howto.xml =================================================================== RCS file: /cvsroot/firebird/manual/src/docs/firebirddocs/docbuilding-howto.xml,v retrieving revision 1.21 retrieving revision 1.22 diff -b -U3 -r1.21 -r1.22 --- docbuilding-howto.xml 24 Oct 2009 16:14:04 -0000 1.21 +++ docbuilding-howto.xml 26 Oct 2009 00:09:50 -0000 1.22 @@ -11,7 +11,7 @@ <surname>Vinkenoog</surname> </author> - <edition>24 Oct 2009 â Document version 1.6</edition> + <edition>26 Oct 2009 â Document version 1.6.1</edition> </articleinfo> <section id="docbuildhowto-intro"> @@ -659,7 +659,7 @@ and again. How to do this depends on your OS. Consult its documentation if necessary.</para> </section> - <section id="docbuildhowto-buidling-output-docs"> + <section id="docbuildhowto-building-output-docs"> <title>Building the HTML and PDF docs</title> <para>If you've made it here in one piece, you are finally ready to build the Firebird docs. @@ -745,7 +745,7 @@ symlink, all the future builds will go fine. (This may not work on Windows, however.)</para> </warning> - <section id="docbuildhowto-buidling-non-english"> + <section id="docbuildhowto-building-non-english"> <title>Building non-English sets with <parameter>-Dsfx</parameter></title> <para>To build documentation sets in non-English languages (in so far as they are available) @@ -771,7 +771,7 @@ </warning> </section> - <section id="docbuildhowto-buidling-subsets"> + <section id="docbuildhowto-building-subsets"> <title>Building subsets with <parameter>-Did</parameter></title> <para>The examples given so far all produce the entire docset (for one language). Usually, @@ -796,7 +796,7 @@ <para>As you can see from the last example, command-line arguments can be combined.</para> </section> - <section id="docbuildhowto-buidling-other-basesets"> + <section id="docbuildhowto-building-other-basesets"> <title>Building a different base set with <parameter>-Dbase</parameter></title> <para>Since January 2006, the Firebird Release Notes have been integrated with the manual @@ -830,7 +830,7 @@ outputs, each with a unique filename.</para> </section> - <section id="docbuildhowto-buidling-defaults"> + <section id="docbuildhowto-building-defaults"> <title>Setting default values in <filename>build.xml</filename></title> <para>Do you often find yourself building the same base set, language version, and/or @@ -849,7 +849,7 @@ </blockquote> </section> - <section id="docbuildhowto-buidling-conclusion"> + <section id="docbuildhowto-building-conclusion"> <title>Building the docs â conclusion</title> <para>That's it â you are now a certified Firebird doc builder. Congratulations!</para> @@ -908,8 +908,8 @@ <para>If a PDF build ends with <literal>BUILD</literal> <literal>SUCCESSFUL</literal> but a couple of lines above it says <quote><computeroutput>No files processed. No files were selected...</computeroutput></quote> and indeed the PDF file isn't there, this may be caused by - spaces and/or other <quote>naughty</quote> characters in the file path. See the warning at the - end of <link linkend="docbuildhowto-buidling-output-docs"><citetitle>Building the HTML and PDF + spaces and/or other <quote>naughty</quote> characters in the file path. See the warning in <link + linkend="docbuildhowto-building-output-docs"><citetitle>Building the HTML and PDF docs</citetitle></link>.</para> <para>If a PDF build succeeds but you find ugly things within the produced document, have a look @@ -1186,7 +1186,7 @@ following page, and you can move on to the next problem.</para> <section id="docbuildhowto-pdfimprove-widows-noid"> - <title id="docbuildhowto-pdfimprove-widows-noid">When there is no DocBook ID</title> + <title>When there is no DocBook ID</title> <para>What if the element has no DocBook id? You'll have to search on (part of) the title/header then. This is a bit trickier, because the title may contain a line break in @@ -1739,6 +1739,55 @@ <para><citetitle>License notice</citetitle> â (C) 2003â2007 -> 2003â2009.</para> </revdescription> </revision> + + <revision> + <revnumber>1.6.1</revnumber> + + <date>26 Oct 2009</date> + + <authorinitials>PV</authorinitials> + + <revdescription> + <para><citetitle>Building the HTML and PDF docs</citetitle> â Fixed the IDs of this + section and five of its subsections, which contained the word + <quote><literal>buidling</literal></quote> instead of + <quote><literal>building</literal></quote>:<itemizedlist spacing="compact"> + <listitem> + <para><literal>docbuildhowto-buidling-output-docs</literal></para> + </listitem> + + <listitem> + <para><literal>docbuildhowto-buidling-non-english</literal></para> + </listitem> + + <listitem> + <para><literal>docbuildhowto-buidling-subsets</literal></para> + </listitem> + + <listitem> + <para><literal>docbuildhowto-buidling-other-basesets</literal></para> + </listitem> + + <listitem> + <para><literal>docbuildhowto-buidling-defaults</literal></para> + </listitem> + + <listitem> + <para><literal>docbuildhowto-buidling-conclusion</literal></para> + </listitem> + </itemizedlist></para> + + <para><citetitle>If things go wrong</citetitle> â Fixed link to <citetitle>Building the + HTML and PDF docs</citetitle>: <literal>buidling</literal> -> + <literal>building</literal>. In the same sentence, the words <quote>at the end + of</quote> have been changed to <quote>in</quote>, because the link target is not at the + end of the section (it's just before the first subsection).</para> + + <para><citetitle>When there is no DocBook ID</citetitle> â Removed ID attribute from + title element, because it was a) unnecessary, and b) a duplicate of the section ID and + therefore illegal.</para> + </revdescription> + </revision> </revhistory></para> </appendix> |