[mew-int 01220] Re: iso-8859-15 (aka Latin-0 or Latin-9)
Tatsuya Kinoshita
tats at example.com
Thu Dec 12 21:03:02 JST 2002
On December 12, 2002, [mew-int 01219],
Kazu Yamamoto <kazu at example.com> wrote:
> > (2) The translation of other iso-8859 charsets (e.g. iso-8859-2) are
> > not yet supported.
>
> Would you explain the tranlation more concretely?
When I set mew-charset-latin to "iso-8859-15", I reply mail which
has iso-8859-2's A WITH ACUTE (iso-8859-1/15 compatible
character), and I put iso-8859-15's characters, then Mew uses
mew-charset-m17n (utf-8 or iso-2022-jp-2). I hope that Mew uses
iso-8859-15.
When I set mew-charset-latin to "iso-8859-15", I reply mail which
has iso-8859-2's CURRENCY SIGN (incompatible with iso-8859-15),
and I put iso-8859-15's characters, then Mew uses
mew-charset-m17n (utf-8 or iso-2022-jp-2) even if I put
iso-8859-2 compatible characters (e.g. A WITH ACUTE). I hope
that Mew uses iso-8859-2 (or iso-8859-1 if possible and preferred).
> > ucs-tables.el decodes iso-8859 characters into latin-iso8859-1
> > or mule-unicode-0100-24ff when `unify-8859-on-decoding-mode' is
> > enabled.
>
> UnicodeData.txt tells me that EURO SIGN has code point 20AC. I'm quite
> confused why 0100-24ff is chosen. Or, is this encoded with UTF-8?
I don't know well... Anyway, the mule-unicode charset can be
used with the mule-utf-8 coding system in GNU Emacs 21.
--
Tatsuya Kinoshita
More information about the Mew-int
mailing list