Check out RFC 2379, just recently upgraded from
IETF proposed standard to IETF draft standard.
No other character encoding has yet got that
high in the IETF standards hierarchy (except
US-ASCII, which is considered more an axiom
than a standard :-).
At 19:57 00/01/24 -0800, Jonathan Coxhead wrote:
> I use Pegasus e-mail <http://www.pegasus.usa.com> under Microsoft
> Windows N T as my e-mail client, and I like it, so I recently wrote
> to the author, David Harris, to ask if he had any plans to include
> Unicode support in his product.
> He replied, in part, "U T F-8 hasn't been standardized as a MIME
> encoding yet as far as I know [...] As soon as I can find an R F C
> that formally describes the way U T F-8 should be handled, I'll
> include such support as I can for it."
> That's good news, so I tried to find an R F C to point him to; but
> all I could see was R F C 1641 (at, e g,
> <ftp://ftp.isi.edu/in-notes/rfc1641.txt>), which seems seriously out
> of date.
> What should I be pointing him at? Pegasus is a Microsoft-only
> product, so the answer might be an R F C, Internet Draft, or a
> Microsoft-specific resource.
> Thanks in advance for any help ...
> /| Jonathan Coxhead Philips Semiconductors
> (_|/ 660 Gail Ave #A3 811 E Arques Ave
> /| Sunnyvale, CA 94086-8160 Sunnyvale, CA 94088
> (_/ tel:+1 408 245 5285 +1 408 991 3725 (voicemail)
> fax: +1 408 991 3300
#-#-# Martin J. Du"rst, World Wide Web Consortium
#-#-# mailto:firstname.lastname@example.org http://www.w3.org
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:58 EDT