[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The charset issue
On Thu, 27 Feb 2003 14:22:32 -0500, Mark Swanson wrote
> On February 27, 2003 02:15 pm, Mark Swanson wrote:
> > Perhaps we need to modify BEGIN:VCALENDAR to:
> > 1. BEGIN:VCALENDAR,CHARSET="UTF-8"
> > 2. allow this line to be in ASCII only
> > 3. bump the VERSION from 2.0 to 2.1.
> OK, after I hit send I realized this isn't exactly a compatible upgrade.
> What about:
> 1. BEGIN:VCALENDAR
> 2. CHARSET:UTF-8
> Where these two lines MUST be ASCII only, and they MUST be the first
> two lines. The CHARSET value must be an IANA registered charset
This could be relaxed a bit without losing anything. As long as the charset
used supports the invariant portion of the ISO 646 charset (as defined in
RFC1345) all of the tokens (keywords, x-names, iana-names and punctuation)
used in 2445 will be intelligible. Obviously, this leaves out EBCDIC charsets
and charsets with more than 8 bits in the default state, but those charsets
don't work with 2445 as it is now either (absent a MIME wrapper).
GPG Key Fingerprint: B375 A4E7 752B DB8C 4359 852E C3CF BF64 379A E9B2
Debian Project (http://www.debian.org)