DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6041>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6041

Problems with newline normalization still persist

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2002-01-28 15:04 -------
Humph. Looks like something was out of synch, all right; I just resynchronized 
with CVS (which did bring down a number of files in the xs and parsers directory 
trees), rebuilt, made absolutely certain I was using that build... and can't 
currently reproduce the problem using DocumentTracer from the samples jarfile, 
either invoked from the command line or under my debugger.

I'm still seeing some weird end-of-line behavior in Xalan (instances 
of &amp;#13;), but let's assume that's Xalan's problem for the moment and close 
this.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to