Return-Path:
In addition, pdflatex
does not know how to incorporate
GIF files. So any graphics must be available in PNG format.
Finally, there are various other restrictive assumptions embedded +
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 @@
<pre>
sections are very likely not to work well
in LaTeX because of differences in escaping and formatting rules
in verbatim
sections.
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 (&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.
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 @@In addition, pdflatex
does not know how to incorporate
GIF files. So any graphics must be available in PNG format.
Finally, there are various other restrictive assumptions embedded +
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 @@
<pre>
sections are very likely not to work well
in LaTeX because of differences in escaping and formatting rules
in verbatim
sections.
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 (&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.
+