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 16:44:11 -0400 [thread overview]
Message-ID: <87bs94vk9w.fsf@tzone.org> (raw)
In-Reply-To: <vaf4rew25r4.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> fabien@tzone.org (Fabien Niñoles) writes:
>> 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.
Kai> I don't understand. What does `W M c' have to do with
Kai> latinX-disp.el?
Nothing. There seems to have two "bugs" here:
1- Gnus seems to defined it's own buffer-display-table instead of
using the standard-display-table. Since latinX-disp.el simply modify
the standard-display-table to be effective, it doesn't seems to work in gnus
(at least v5.9.0 that I used here).
2- I isolate the other bug (the \201 or \216 character add before every high-bit set
character in multibyte environment) to a bug in the coding-system. To test
it just evaluate this:
(decode-coding-string "élève" 'iso-8859-1) => "\216él\216ève" in latin-1 environment.
You can replace the coding system for anything, even no-conversion or
raw-text, it will always add the extra character, whatever your
environment.
Since decode-coding-string are a built-in function, I'm currently rebuilding
emacs to debug this a little more.
Kai> IMHO, it would be better to enable Emacs to just display many
Kai> characters, rather than making changes in Gnus only.
The problem 1) is in Gnus and I don't know if it exists in the CVS. It will
certainly not be easy to fixed since it should appears in the encoding system
of gnus. Maybe someone can help me about this one.
For the other one, it's a problem in my emacs version... I continue to
investigate.
Ciao!
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>
iD8DBQE9NyiIjx/fybzglDYRAiJhAJ4sAOC7/oFtMmGSTGH+qSLSFIvnxwCeJ78n
2abtUFTl8TPntykE0uRvH0g=
=OYfA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-07-18 20:44 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
[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 [this message]
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=87bs94vk9w.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).