From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Unification in Gnus?
Date: Tue, 11 Dec 2001 16:39:45 +0100 [thread overview]
Message-ID: <vafpu5lwyta.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
Since a couple of days ago, the Emacs 21 CVS contains Dave Love's
utilities for unification of iso-8859 charsets. This is Good Stuff.
However, if I compose a message with a Latin-1 ä and a Latin-9 € in
it, then the outgoing message with have charset=macintosh, which
strikes me as a suboptimal value. Suggestions?
[time passes]
Oh, now I see that the Latin-9 character is not Latin-9 after all:
/----
| character: € (01235114, 342604, 0x53a4c)
| charset: mule-unicode-0100-24ff
| (Unicode characters of the range U+0100..U+24FF.)
| code point: 116 76
| syntax: w which means: word
| category:
| buffer code: 0x9C 0xF4 0xF4 0xCC
| file code: not encodable by coding system iso-latin-9
| font: -Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO10646-1
|
| [back]
\----
So it's been converted to mule-unicode. Hm. Hmmmm...
I still don't understand this.
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
reply other threads:[~2001-12-11 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vafpu5lwyta.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).