From: John Dlugosz
That is the official IANA name. See
http://www.iana.org/assignments/character-sets . A while back, when
looking for the official name, that's the only one I could find!
Now, I see that windows-1252 is listed also. They don't show date of
listing, but if the MIBenum is incremented each time, it's clearly a
recient addition.
iso-8859-1 is also listed, and it's a subset. Windows started with that
and added glyphs in the C1 control area.
Marc Mutz <mutz(_at_)kde(_dot_)org> on 04-18-2002 12:35:21 PM
To: john(_dot_)dlugosz(_at_)kodak(_dot_)com,
roessler(_at_)does-not-exist(_dot_)org
cc: ietf-openpgp(_at_)imc(_dot_)org
Subject: Re: Clearsigning, MIME, etc.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 18 April 2002 18:31, john(_dot_)dlugosz(_at_)kodak(_dot_)com wrote:
<snip>
Use a header inside the PGP envelope to note the message's character set.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA2
Charset: ISO-8859-1-Windows-3.1-Latin-1
Message starts here...
Now how many people are going to use the correct official name, when it's
such a jawbreaker? Look at the charset declaration in web pages, and
very
few get it right. So, better make that clear.
<snip>
Which charset should this be? The official, preferred mime-name is
"iso-8859-1", and nothing else should be used, though the recveiver should
understand other common names.
Marc
- --
Marc Mutz <mutz(_at_)kde(_dot_)org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8vwPZ3oWD+L2/6DgRAtzUAJ9ldFWxGPh0iM8/CmXShXTpcTGEfACg/jbQ
166yx32jHn7nHrjD5tm82qI=
=G0bO
-----END PGP SIGNATURE-----