[EMAIL PROTECTED] (Markus Kuhn) wrote on 04.02.01 in
<[EMAIL PROTECTED]>:
> really should have been outside the scope of a character coding standard
> like Unicode to handle language tags and it was a quite ugly politically
> motivated compromise intended to shut up Japanese ISO 2022 fanatics that
> Plane 14 was added in the first place. Fortunately, both W3C and
I thought it was added to placate the IETF, who were asking for language
tagging everywhere (in RFC 2130).
The origin seems to be RFC 2482; the listed contributors are
K. Whistler
G. Adams
Chris Newman
Mark Crispin
Rick McGowan
Joe Becker
John Jenkins
Asmus Freytag
I see no mention of 2022 in there.
> Microsoft have decided not to use them in their formats. HTML, Word.doc,
> and other common text formats have already proper orthogonal font and
> language tagging and won't need any Plane 14 and variant glyph hacks.
And RFC 2482 actually mentions that.
Incidentally, RFC 2130 mentions the 2022 mess (via citing RFC 1554
defining ISO-2022-JP-2) but only speculates if this could solve the
problem; they certainly seem to prefer HTML-like solutions.
Of course, RFC 2482 (Plane 14 tags) actually *is* a HTML-like solution.
MfG Kai
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
