Update of /cvsroot/boost/boost/libs/date_time/xmldoc
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv18723

Modified Files:
      Tag: RC_1_34_0
        date_time_docs_howto.html 
Log Message:
fixed HTML code (this caused the inspect tool to detect broken links, but that 
wasn't the actual problem)

Index: date_time_docs_howto.html
===================================================================
RCS file: /cvsroot/boost/boost/libs/date_time/xmldoc/date_time_docs_howto.html,v
retrieving revision 1.1
retrieving revision 1.1.4.1
diff -u -d -r1.1 -r1.1.4.1
--- date_time_docs_howto.html   13 Jul 2005 04:04:12 -0000      1.1
+++ date_time_docs_howto.html   17 Jul 2006 04:09:03 -0000      1.1.4.1
@@ -27,12 +27,12 @@
     <li><A href="#xsl_mods">Making further changes to the 
date_time_fo_stylesheet</A></li>
   </ol>
   <hr>
-  <A name="exclusive_html"><h3>Building Exclusive Date Time HTML 
Documentation</h3></A>
+  <h3><a name="exclusive_html">Building Exclusive Date Time HTML 
Documentation</a></h3>
   <p>No modifications are necessary to build an exclusive set of date time 
html documentation. Simply run bjam:<br>
   <div class="screen">bjam --v2 date_time_doc</div><br>
-  The resulting html can be found in <font class="fname">xmldoc/html</font>. 
NOTE: the stylesheet may not be present. It can be copied from the <font 
class="fname">$BOOST_ROOT/doc/html</font> directory.</p>
+  The resulting html can be found in <font class="fname">xmldoc/html</font>. 
NOTE: the stylesheet may not be present. It can be copied from the <font 
class="fname">$BOOST_ROOT/doc/html</font> directory.<br />
   <hr>
-  <a name="exclusive_pdf"><h3>Building Exclusive Date Time PDF</h3></a>
+  <h3><a name="exclusive_pdf">Building Exclusive Date Time PDF</a></h3>
   <p><strong>Prerequisite:</strong> bjam must be able to build documentation 
for 'fo' output (necessary aditions must have been added to <font 
class="fname">user-config.jam</font>).</p>
 
   <p>Necessary modifications to build the date time pdf are:
@@ -51,10 +51,10 @@
     <div class="screen">bjam --v2 date_time_doc fo</div></li>
     <li>Build the pdf.<div class="screen">fop 
../../../bin.v2/libs/date_time/.../exclusive_date_time.fo 
date_time.pdf</div></li>
   </ol>
-  </p>
+  <br />
                                        <p><strong>BUILD ERRORS:</strong> 
During the fo->pdf step, an error stating that an id already exists may appear. 
This error appears to be introduced during the xml->fo step. There are two 
possible workarounds for this (depending on where the duplicated id apears). If 
the duplicate id appears in the reference section, find the offending id and 
change it manually (ex: "id2534038" -> "id2534039"). If the id appears in the 
documentation generated from the xml, change one of the anchor names in one of 
the xml files. <strong>Note:</strong> This does not mean there is an error in 
the xml. The anchor and link that is known to have an effect is <font 
class="fname">date_input_facet_intro</font> (change the 'd' to a 'f', or back, 
should do the trick).</p>
   <hr>
-  <a name="doxy_ref"><h3>Generating Date Time Doxygen Reference</h3></a>
+  <h3><a name="doxy_ref">Generating Date Time Doxygen Reference</a></h3>
   <p>Each doxygen reference file must be built, copied, and modified 
seperately. The steps to build all four <font class="fname">*.boostbook</font> 
reference files are:
   <ol>
     <li>Generate the <font class="fname">*.boostbook</font> files.</li>
@@ -68,15 +68,18 @@
           local_time_autodoc
 cp ../../../bin.v2/libs/.../*.boostbook .
 ./ref_tag_fix.pl</pre></div>
-    </p>
+    <br />
     <hr>
-    <a name="xsl_mods"><h3>Making further changes to the 
date_time_fo_stylesheet</h3></a>
+    <h3><a name="xsl_mods">Making further changes to the 
date_time_fo_stylesheet</a></h3>
     <p>The stylesheet currently sets the left, right, and bottom margins. It 
also reduces the font-size for table cells that have the &#060;screen&#062; 
tags in them. The font-size reduction is accomplished by breaking the entire 
string (between the &#060;screen&#062; tags) into segments delimited by '\n'. 
Each of these segment's lengths are checked and the longest segment is used in 
calculating the amount of font-size reduction.</p>
     <p>There are two variables used in adjusting the font-size: <font 
class="fname">char-per-cell</font> &#038; <font 
class="fname">min-reduction</font>. These hold the number of characters that 
can fit into a cell and the minimum percentage of reduction allowed (expressed 
as an integer).</p>
     <p>Determining the number of characters that will fit into a cell is not 
the most gracefull of operations. Simply put, the minimum reduction must be set 
to 100 (no reduction allowed) and the pdf must be built. From there the number 
of characters that will fit must be manually counted.</p>
     <hr>
     <div><p class="copyright">Copyright &#169; 2001-2005 CrystalClear 
Software, Inc</p></div>
     <div class="legalnotice">
-      <p>Subject to the Boost Software License, Version 1.0. <a 
href="http://www.boost.org/LICENSE_1_0.txt"; 
target="_top">http://www.boost.org/LICENSE_1_0.txt</ahref="http://www.boost.org/LICENSE_1_0.txt";></p></div>
+               <p>Distributed under the Boost Software License, Version 1.0.
+       (See accompanying file <a 
href="../../../LICENSE_1_0.txt">LICENSE_1_0.txt</a> or
+        copy at <a 
href="http://www.boost.org/LICENSE_1_0.txt";>www.boost.org/LICENSE_1_0.txt</a>)</p>
+    </div>
   </body>
 </html>



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Boost-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/boost-cvs

Reply via email to