You'll stand a better chance of getting your line ends right by using
<xsl:text>
</xsl:text>
with the line end being represented by whatever it is on the system where
the text file containing these two lines resides. (This would be CR+LF on
Windowses, LF on Unices and CR on Mac OSs.)

Explicitly requesting CR or LF or CR+LF means that the result will not
necessarily have the intended line structure on one system or the other,
i.e., wherever you run the XSLT.

-W

On 7 November 2014 18:40, Catherine Wilbur cwilbur@xxxxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> 1) Currently I am using a line feed in my code at the end.  Should it be a
> line feed or carriage return?  Reason I am asking is because when I open my
> CSV file in NotePad or WordPad the data wraps.  But with Notes++ or Excel
> the data does not wrap.  Currently using a line feed at end of my data.
> Assuming it should be a carriage return.  Guessing that the data is
> wrapping when I open the CSV file because it does not recognize the
> carriage return or line feed but Notes++ does recognize these characters.
>
>
> http://stackoverflow.com/questions/7965642/explicitly-specify-linefeed-character-and-not-carriage-return
>
> Should I be using a line feed in my code.  (this is what I am using now)
>          <xsl:text>&#xA;</xsl:text>
>
> Or should I be using a carriage return in my code.
>  <xsl:text>&#xD;</xsl:text>
>
>
> _____________________________________________________________________
> Catherine Wilbur  |  Senior Application Programmer  |  IT Services
> 401 Sunset Avenue, Windsor ON Canada  N9B 3P4
> (T) 519.253.3000 Ext. 2745  |  (F) 519.973.7083  |  (E)
> cwilbur@xxxxxxxxxxx
> www.uwindsor.ca/its
>  XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <-list/528976> (by
> email <>)