Sujet : Re: Simple string conversion from UCS2 to ISO8859-1
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.lang.cDate : 23. Feb 2025, 06:53:59
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vped5n$cp18$3@dont-email.me>
References : 1 2 3 4 5
User-Agent : Pan/0.162 (Pokrosvk)
On Sat, 22 Feb 2025 05:29:14 +0100, Janis Papanagnou wrote:
It looks like they accept not only LF, CR, CR-LF, but also LF-CR.
Is the latter of any practical relevance?
Not to answer the question, but just to add to it; from the XML 1.1 spec
<
https://www.w3.org/TR/2006/REC-xml11-20060816/#sec-xml11>:
In addition, XML 1.0 attempts to adapt to the line-end conventions
of various modern operating systems, but discriminates against the
conventions used on IBM and IBM-compatible mainframes. As a
result, XML documents on mainframes are not plain text files
according to the local conventions. XML 1.0 documents generated on
mainframes must either violate the local line-end conventions, or
employ otherwise unnecessary translation phases before parsing and
after generation. Allowing straightforward interoperability is
particularly important when data stores are shared between
mainframe and non-mainframe systems (as opposed to being copied
from one to the other). Therefore XML 1.1 adds NEL (#x85) to the
list of line-end characters. For completeness, the Unicode line
separator character, #x2028, is also supported.