[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Requirement  and charset tagging
- To: Paul Hoffman / IMC <email@example.com>
- Subject: Re: [idn] Requirement  and charset tagging
- From: "A. Vine" <firstname.lastname@example.org>
- Date: Fri, 16 Jun 2000 16:42:00 -0700
- CC: email@example.com
- Delivery-date: Fri, 16 Jun 2000 16:44:05 -0700
- Envelope-to: firstname.lastname@example.org
Last I checked, RFC 1766 only deals with language tags, and has no provision for
charsets. I haven't read the latest draft, but based on the discussion it
doesn't look like charset tagging has been added.
Andrea Vine, email@example.com, iPlanet i18n architect
"Stew my foot and call me Brenda"
--From "Angry Child" by Aardman Animation
Paul Hoffman / IMC wrote:
> > This document does not recommend any charset for IDN. If more than
> >one charset is used, or might be used in future, in the protocol, then
> >the protocol must specify all the charsets being used and for what
> >purpose. It must also conform to [RFC1766] by tagging the charset. No
> >implicit rules should be allowed for multiple charsets. A CCS(s) chosen
> >must at least cover the range of characters as currently defined (and as
> >being added) by ISO 10646/Unicode.
> The sentence "It must also conform to [RFC1766] by tagging the
> charset." is overkill for a protocol that only allows one charset.
> For example, if the protocol only allows UTF-8, why should every name
> part have to be marked as UTF-8? I propose changing that sentence to
> "If multiple charsets are allowed, each item must be tagged with the
> name of the charset".
> --Paul Hoffman, Director
> --Internet Mail Consortium