From: John Dlugosz
You obviously are not aware of ISO 2022
I'm very aware of ISO 2022! The DICOM (Diagnostic Imaging & Communications
In Medicine) uses it, and I'm actually working on ISO 2022 encoder/decoder
right now.
My opinion is this: way, way too complicated
No kidding.
What kinds of interchange applications (still) use it?
Assuming U+2028 is a "soft" line break that can migrate and U+2029 is the
"hard" line break (the convention of many commercial systems), U+2029 is
the
only choice for line separators when writing code. For plain text, I
personally prefer viewing them as being the same except in GUI
environments
where the spacing provided by U+2029 can be set by the user.
Sorry, I misread. I went back to page 2-14 of the Unicode standard, and
the meaning is that
U+2028 is an unconditional end-of-line, while the contents of a paragraph
(delimited by U+2029) can flow. The "soft" breaks of the current flowing
are not represented by these characters.
The spec is not clear with respect to scope. It makes the point that the
chars are separators, not terminators. So if both U+2028 and U+2029 are
present in the same file, what's the relationship between lines and
paragraphs? Commercial systems, as you say, treat paragraphs as a higher
level than line, even though that's not what the standard says. <sigh>
--John
