charset="Windows-1252"

charset="Windows-1252"

[Karl Eichwalder]

pgnus seems not to be able to do the right thing with "Windows-1252"
messages (8bit characters are displayed in a back slashish notation):

    MIME-Version: 1.0
    Content-Type: text/plain;
            charset="Windows-1252"
    Content-Transfer-Encoding: 8bit
    X-Mailer: Microsoft Outlook Express 5.00.2615.200
    X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200

Any chance to work around the problem?  Or should I try to convince
people to use ISO charsets?

-- 
work    : ke@suse.de                          |
        : http://www.suse.de/~ke/             |       ------    ,__o
personal: ke@gnu.franken.de                   |      ------   _-\_<,
        : http://www.franken.de/users/gnu/ke/ |     ------   (*)/'(*)

Re: charset="Windows-1252"

[Steinar Bang]

>>>>> Karl Eichwalder <ke@gnu.franken.de>:

> Any chance to work around the problem?  Or should I try to convince
> people to use ISO charsets?

That would be the correct solution.  AFAIK "Windows-1252" isn't a
legal charset parameter to text/plain.  See RFC2046, section 4.1.1
(or http://www.ietf.org/rfc/rfc2046.txt for those who doesn't have
Simon's nifty "RFC button thingy").

Re: charset="Windows-1252"

[Hrvoje Niksic]

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?  Several years ago, people from Microsoft bothered to
register their charsets at ISO.  At least I believe I've found
windows-1250 (aka CP1250, used for Croatian characters) over there.

Re: charset="Windows-1252"

[Steinar Bang]

>>>>> 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.

For easy reference: http://www.ietf.org/rfc/rfc2046.txt

> Several years ago, people from Microsoft bothered to register their
> charsets at ISO.  At least I believe I've found windows-1250 (aka
> CP1250, used for Croatian characters) over there.

And...?

IIRC "Windows-1252" is "extended ISO-8859-1", with additional crud in
both the control character positions, and the range 128-159.

Re: charset="Windows-1252"

[Hrvoje Niksic]

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.

Re: charset="Windows-1252"

[Steinar Bang]

>>>>> Hrvoje Niksic <hniksic@iskon.hr>:

>    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.

With IANA?

You said with ISO, in which case their use is "by private" agreement,
and should be prefixed with "X-".

Re: charset="Windows-1252"

[Johan Kullstam]

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.

10 is a digit?  it looks like two digits to me.

-- 
J o h a n  K u l l s t a m
[kullstam@ne.mediaone.net]
Don't Fear the Penguin!

Re: charset="Windows-1252"

[Florian Weimer]

Hrvoje Niksic <hniksic@iskon.hr> writes:

> The Windows things are registered.

Yes, but not `Windows-1252'. ;)

Re: charset="Windows-1252"

[Toby Speight]

Hrvoje> Hrvoje Niksic <URL:mailto:hniksic@iskon.hr>

0> In article <9t9u2n5b4o7.fsf@mraz.iskon.hr>, Hrvoje wrote:

Hrvoje> Steinar Bang <sb@metis.no> writes:

>> That would be the correct solution.  AFAIK "Windows-1252" isn't a
>> legal charset parameter to text/plain.

Hrvoje> Why not?  Several years ago, people from Microsoft bothered to
Hrvoje> register their charsets at ISO.  At least I believe I've found
Hrvoje> windows-1250 (aka CP1250, used for Croatian characters) over
Hrvoje> there.

But their Windows Latin charset is called "ISO-8859-1-Windows-3.1-Latin-1",
not "Windows-1252" (according to Jukka Korpela[1], who cites the IANA
registry).

[1] <URL:http://www.hut.fi/u/jkorpela/chars.html#win>

Re: charset="Windows-1252"

[Janne Rinta-Manty]

Karl Eichwalder 1999-11-01T22:32:47Z:
KE> pgnus seems not to be able to do the right thing with
KE> "Windows-1252" messages (8bit characters are displayed in a back
KE> slashish notation):
KE> Any chance to work around the problem?  Or should I try to
KE> convince people to use ISO charsets?

I just added windows-1252 to the list gnus-newsgroup-ignored-charsets,
and the messages are now displayed OK. This probably requires that
iso-8859-1 is the default charset.

-- 
Janne Rinta-Mänty

Re: charset="Windows-1252"

[Karl Eichwalder]

Thanks for all your hints and your encouragements!

Janne Rinta-Manty <jrm@iki.fi> writes:

|   I just added windows-1252 to the list
|   gnus-newsgroup-ignored-charsets, and the messages are now displayed
|   OK. This probably requires that iso-8859-1 is the default charset.

Indeed, that's a very good work around -- strange enough, I only figured
out howto set the variable via customize.  And then, gnus stopped
reading the active file.  This setting seems to help for now:

(setq gnus-read-active-file nil)

I tried:

(eval-after-load "gnus-sum"
  (setq gnus-newsgroup-ignored-charsets
        (cons 'windows-1252 gnus-newsgroup-ignored-charsets)))

This leads to an error message; IIRC,
"... gnus-newsgroup-ignored-charsets ... not defined".

-- 
work    : ke@suse.de                          |
        : http://www.suse.de/~ke/             |       ------    ,__o
personal: ke@gnu.franken.de                   |      ------   _-\_<,
        : http://www.franken.de/users/gnu/ke/ |     ------   (*)/'(*)

Re: charset="Windows-1252"

[Robert Bihlmeyer]

Hi,

>>>>> On 02 Nov 1999 10:53:28 +0100
>>>>> Hrvoje Niksic <hniksic@iskon.hr> said:

 Hrvoje> Why not? Several years ago, people from Microsoft bothered to
 Hrvoje> register their charsets at ISO. At least I believe I've found
 Hrvoje> windows-1250 (aka CP1250, used for Croatian characters) over
 Hrvoje> there.

1250 is registered but 1252 is not. See
<URL:http://www.isi.edu/in-notes/iana/assignments/character-sets>.
(Referenced from <URL:http://www.iana.org/numbers.html>).

	Robbe

-- 
Robert Bihlmeyer	reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>	<http://stud2.tuwien.ac.at/~e9426626/sig.html>