From: fabien@tzone.org (Fabien Niñoles)
Cc: ding@gnus.org
Subject: Re: locale ISO-8859-15, UTF-8 and mail...
Date: 18 Jul 2002 12:12:56 -0400 [thread overview]
Message-ID: <874rexdng7.fsf@tzone.org> (raw)
In-Reply-To: <vafwurtgt65.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> fabien@tzone.org (Fabien Niñoles) writes:
>> My problem is when I try to read mail encoded in ISO-8859-1.
>> Gnus doesn't seems to recognized them correctly and aren't able
>> to trancode them to my correct display setting (ISO-8859-15 or
>> latin-9 if you prefer). Even "W M c" doesn't wash the mail
>> correctly: the characters (previously printed as ?) are
>> correctly replaced but have a \201 before each occurence
>> (whatever the encoded character is).
Kai> There is a file latin1-disp.el which can sort of do what you
Kai> want, but it uses Latin-1 characters instead of Latin-9
Kai> characters. So you'd have to make a new version which is
Kai> very similar but uses Latin-9 characters. Then you can tell
Kai> Emacs to display many characters using their Latin-9
Kai> equivalents.
Done, I send the file to Dave Love (the original maintainer of latin-1)
but, if it works for mostly anything (like this email: ¾), it doesn't
work when I visiting Latin-1 encoded email; or even in mail-headers.
Something like "élève" will go out has "?l?ve", and, if I "C-u W M c
latin-9", it will be "\201él\201ève". Just watching it with "W M c",
only add \201 before all `?'. I'm looking for adding a command that
simple (gnus-article-decode-charset nil 'latin-9) and remove all \201,
but I will frankly prefer to make it works correctly.
hmmm...
I try to isolate the bug a little number and it seems that it's somewhere
in decode-coding-region and/or decode-coding-string (both built-in).
At least, this
(mm-decode-string "élève" "iso-8859-1")
replace each accentuated character with the sequence "\216?" and
(mm-decode-string "élève" "iso-8859-15")
simply add \216 front to each accentuated character.
So it seems to me that the only bug is the addition of the \216 (or \201
for decode-region) after the translation of a character... BTW, I'm on
powerpc, maybe it's relevant (unsigned char and consor bugs...).
Thanks,
Fabien
--
Fabien Niñoles Debian Maintainer
fabien@debian.org http://www.debian.org
GPG KeyID: C15D FE9E BB35 F596 127F BF7D 8F1F DFC9 BCE0 9436
next prev parent reply other threads:[~2002-07-18 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 18:01 Fabien Niñoles
2002-07-18 11:41 ` Kai Großjohann
2002-07-18 16:12 ` Fabien Niñoles [this message]
[not found] ` <878z49dnk3.fsf@tzone.org>
[not found] ` <vaf4rew25r4.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
2002-07-18 20:44 ` Fabien Niñoles
2002-07-18 20:56 ` Jorgen Schaefer
2002-07-19 7:19 ` Kai Großjohann
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=874rexdng7.fsf@tzone.org \
--to=fabien@tzone.org \
--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).