dleslie 00/12/21 07:36:16
Modified: java/xdocs/sources/xalan readme.xml
Log:
Added note on handling of cr-lf in output.
Revision Changes Path
1.15 +5 -1 xml-xalan/java/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- readme.xml 2000/12/20 17:56:27 1.14
+++ readme.xml 2000/12/21 15:36:15 1.15
@@ -97,7 +97,11 @@
<li>In conformance with the <jump
href="http://www.w3.org/TR/xslt#section-HTML-Output-Method";>XSLT Recommendation
on the HTML
Output Method</jump> and <jump
href="http://www.w3.org/TR/REC-html40/appendix/notes.html#h-B.2.1";>Section
B.2.1 of the HTML 4.0
Recommendation</jump>, &xslt4j2; uses %hh encoding for each byte of the
UTF-8 representation of non-ASCII characters in HTML URI
- attributes.</li>
+ attributes.<br/><br/></li>
+ <li>When your stylesheet asks for an explicit carriage-return character
(&#13;) to be inserted into the output, it is output during
+ the serialization process in escaped form unless escaping has been
disabled. When your stylesheet asks for an explicit line-feed character
+ (&#10;) to be output, the system-default line-break character(s)
is/are output during the serialization process. Also keep in mind that
+ the Parser normalizes line-breaks to line-feeds when it sends character
events to the processor.</li>
</ul>
</s3><anchor name="bugs"/>
<s3 title="Open bugs and bug reporting">
