Re: charset="Windows-1252"

[Hrvoje Niksic <hniksic@iskon.hr>]

Steinar Bang <sb@metis.no> writes:

> >>>>> Hrvoje Niksic <hniksic@iskon.hr>:
> 
> > Steinar Bang <sb@metis.no> writes:
> >> That would be the correct solution.  AFAIK "Windows-1252" isn't a
> >> legal charset parameter to text/plain.
> 
> > Why not? 
> 
> Because of this statement from section 4.1.2 (not 4.1.1 as I said
> earlier. Sorry!) of RFC2046. at the bottom of page 9:
> 
> The defined charset values are:
> 
>     (1)   US-ASCII -- as defined in ANSI X3.4-1986 [US-ASCII].
> 
>     (2)   ISO-8859-X -- where "X" is to be replaced, as
>           necessary, for the parts of ISO-8859 [ISO-8859].  Note
>           that the ISO 646 character sets have deliberately been
>           omitted in favor of their 8859 replacements, which are
>           the designated character sets for Internet mail.  As of
>           the publication of this document, the legitimate values
>           for "X" are the digits 1 through 10.

You missed the rest.

   The character sets specified above are the ones that were
   relatively uncontroversial during the drafting of MIME.  This
   document does not endorse the use of any particular character set
   other than US-ASCII, and recognizes that the future evolution of
   world character sets remains unclear.

   Note that the character set used, if anything other than US- ASCII,
   must always be explicitly specified in the Content-Type field.

   No character set name other than those defined above may be used in
   Internet mail without the publication of a formal specification and
   its registration with IANA, or by private agreement, in which case
   the character set name must begin with "X-".

The Windows things are registered.