RE: Is this an encoding issue?

Not precisely encoding. What you are seeing is Notepad's 
response to Unix line feeds. Normally on Windows, end of lines
are marked with both a CR (carriage return) and LF (line feed). 
UNIX machines, however, just use LF. 

With Homesite and other 'Unix-aware' editors, they display
the LF just like the CR-LF. But Notepad is very Windows-centric
and won't do this for you (hence the empty box characters and 
bad wrapping). 

It has no affect on how your XML or the output of the transformation
is handled, since browsers also have no problem with this. Saxon
is just following the Unix formal while XT is giving you Windows
line ends.

Sara

> -----Original Message-----
> From: Jason Macki [mailto:jmacki@xxxxxxx]
> Sent: Thursday, June 21, 2001 1:40 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  Is this an encoding issue?
> 
> 
> Hello,
> 
> I've run into a problem that I think might be an encoding issue, and I
> was wondering if anyone could suggest a fix.
> 
> When I use Notepad to open HTML files created with instant 
> Saxon, end of
> line characters are replaced by square blocks, and the lines do not
> break.
> However, when I use other editors such as Visual Studio or HomeSite to
> view the file, the blocks do not appear, and the lines end at the
> correct places.
> 
> When perform the same transformation using XT, this problem does not
> occur.
> 
> Does this ring a bell with anyone?
> 
> Thanks,
> Jason
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list