From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Thu Mar 13 2003 - 05:14:31 CST
In <3E6F5C1D.8020005@Sonietta.blilly.com> Bruce Lilly <blilly@erols.com> writes:
>Charles Lindsey wrote:
>> In <3E6CC144.60904@Sonietta.blilly.com> Bruce Lilly <blilly@erols.com> writes:
>>>We're discussing text message header fields, not HTML. ...
>>
>>
>> If it is legitimate for the standards which define HTML to permit the RFC
>> 3066 language tags to be expressed in UTF-16, then it must be legitimate
>> for the Netnews standard to express those same tags in the Unicode
>> plane 14 characters expressly designed for that very purpose.
>Your argument seems to be "if milk must be pasteurized, then coffee must
>be decaffienated". HTML language tags in fact use the 3066/IANA/ISO codes
>directly, not via some mapping. E.g.:
No, it was reported that in HTML those 3066 language codes (composed of
letters. digits and hyphens) could legitimately be conveued in, for
example, UTF-16. Thus establishing that your claim that RFC 3066 required
them to be expressed in US-ASCII was false.
>> And in fact undoing that mapping consists simply of masking the characters
>> with 0x7F.
>The problem is that if the charset is unsupported by the recipient, one
>cannot even *get to* the mapping to undo it.
If a recipient does nor support the particular charset, then it is
unlikely to care very much what language to asssume when [not] displaying
that charset.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl Email: chl@clw.cs.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5