From: "Johan Kullstam" <kullstam@ne.mediaone.net>
Cc: ding@gnus.org
Subject: Re: charset="Windows-1252"
Date: 02 Nov 1999 08:02:03 -0500 [thread overview]
Message-ID: <m2zowxxd10.fsf@sophia.axel.nom> (raw)
In-Reply-To: Steinar Bang's message of "02 Nov 1999 11:02:21 +0100"
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!
next prev parent reply other threads:[~1999-11-02 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-01 22:02 charset="Windows-1252" Karl Eichwalder
1999-11-02 9:21 ` charset="Windows-1252" Steinar Bang
1999-11-02 9:53 ` charset="Windows-1252" Hrvoje Niksic
1999-11-02 10:02 ` charset="Windows-1252" Steinar Bang
1999-11-02 11:14 ` charset="Windows-1252" Hrvoje Niksic
1999-11-02 12:28 ` charset="Windows-1252" Steinar Bang
1999-11-02 13:17 ` charset="Windows-1252" Florian Weimer
1999-11-02 13:02 ` Johan Kullstam [this message]
1999-11-02 14:53 ` charset="Windows-1252" Toby Speight
1999-11-04 16:42 ` charset="Windows-1252" Robert Bihlmeyer
1999-11-03 8:54 ` charset="Windows-1252" Janne Rinta-Manty
1999-11-04 6:31 ` charset="Windows-1252" Karl Eichwalder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zowxxd10.fsf@sophia.axel.nom \
--to=kullstam@ne.mediaone.net \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).