Re: [xsl] Hidden implementation-defined behaviour

[David Carlisle <davidc@xxxxxxxxx>]

Oh and teh example that Michael added to the spec in relation to the
earlier report is in the final rec section 16.2 as

Example: Splitting an Input File into a Sequence of Lines
...Note that the unparsed-text  function does not normalize line endings....

http://www.w3.org/TR/xslt20/#d5e22249

(I do wish people didn't use generate-id() to generate link anchors:-)


> As far as I can see, both behaviours are legitimate, so it is something to 
> beware of (calling translate(unparsed-text($uri, "
", "")) gives 
> portable behaviour).
No, a file with traditional mac line endings just has a single #13 so
that would make it all one line.

David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________