httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-site/xdocs/docs-project docsformat.xml
Date Fri, 02 Apr 2004 21:29:24 GMT
slive       2004/04/02 13:29:23

  Modified:    docs/docs-project docsformat.html
               xdocs/docs-project docsformat.xml
  Log:
  Add a note about character escaping.
  
  Revision  Changes    Path
  1.29      +9 -1      httpd-site/docs/docs-project/docsformat.html
  
  Index: docsformat.html
  ===================================================================
  RCS file: /home/cvs/httpd-site/docs/docs-project/docsformat.html,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -d -b -u -r1.28 -r1.29
  --- docsformat.html	2 Apr 2004 20:54:17 -0000	1.28
  +++ docsformat.html	2 Apr 2004 21:29:22 -0000	1.29
  @@ -186,7 +186,7 @@
   complex stuff (like spanning rows or columns) will not work.</p>
   <p>In addition, <code>pdflatex</code> does not know how to incorporate
   GIF files.  So any graphics must be available in PNG format.</p>
  -<p>Finally, there are various other restrictive assumptions embedded
  +<p>There are various other restrictive assumptions embedded
   in the XSLT that work for the current docs, but may need to be
   modified in the future.  For example, the code that transforms
   HTML-style links to LaTeX cross-references will work only with the
  @@ -194,6 +194,14 @@
   <code>&lt;pre&gt;</code> sections are very likely not to work well
   in LaTeX because of differences in escaping and formatting rules
   in <code>verbatim</code> sections.</p>
  +<p>Finally, there are various differences in escaping rules between
  +XML/HTML and LaTeX.  Some characters need to be backslash-escaped in
  +LaTeX, and all XML entitites (&amp;whatever;) must be converted to
  +LaTeX equivalents.  This is currently handled for a limitted set of
  +characters using a big ugly search-replace in the XSLT.  But this may
  +need to be modified in the future, especially to handle translations.
  +Perhaps pre-processing with a perl script and a substitution table
  +would be better.</p>
     </blockquote>
    </td></tr>
   </table>
  
  
  
  1.17      +11 -1     httpd-site/xdocs/docs-project/docsformat.xml
  
  Index: docsformat.xml
  ===================================================================
  RCS file: /home/cvs/httpd-site/xdocs/docs-project/docsformat.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -d -b -u -r1.16 -r1.17
  --- docsformat.xml	2 Apr 2004 20:54:19 -0000	1.16
  +++ docsformat.xml	2 Apr 2004 21:29:23 -0000	1.17
  @@ -124,7 +124,7 @@
   <p>In addition, <code>pdflatex</code> does not know how to incorporate
   GIF files.  So any graphics must be available in PNG format.</p>
   
  -<p>Finally, there are various other restrictive assumptions embedded
  +<p>There are various other restrictive assumptions embedded
   in the XSLT that work for the current docs, but may need to be
   modified in the future.  For example, the code that transforms
   HTML-style links to LaTeX cross-references will work only with the
  @@ -132,6 +132,16 @@
   <code>&lt;pre&gt;</code> sections are very likely not to work well
   in LaTeX because of differences in escaping and formatting rules
   in <code>verbatim</code> sections.</p>
  +
  +<p>Finally, there are various differences in escaping rules between
  +XML/HTML and LaTeX.  Some characters need to be backslash-escaped in
  +LaTeX, and all XML entitites (&amp;whatever;) must be converted to
  +LaTeX equivalents.  This is currently handled for a limitted set of
  +characters using a big ugly search-replace in the XSLT.  But this may
  +need to be modified in the future, especially to handle translations.
  +Perhaps pre-processing with a perl script and a substitution table
  +would be better.</p>
  +
   </section>
   
   </body>
  
  
  

Mime
View raw message