From: Kenichi Handa <handa@etl.go.jp>
Cc: vvv@vvv.vsu.ru, ding@gnus.org, handa@etl.go.jp
Subject: Re: Problems with 8-bit headers
Date: Thu, 27 Apr 2000 08:35:22 +0900 (JST) [thread overview]
Message-ID: <200004262335.IAA15704@etlken.etl.go.jp> (raw)
In-Reply-To: <oqaeigwptn.fsf@titan.progiciels-bpi.ca> (message from =?ISO-8859-1?Q?Fran=E7ois_Pinard?= on 26 Apr 2000 16:49:08 -0400)
=?ISO-8859-1?Q?Fran=E7ois_Pinard?= <pinard@iro.umontreal.ca> writes:
> Vladimir Volovich <vvv@vvv.vsu.ru> writes:
>> However, there is a bug somewhere in core Emacs which makes it misbehave
>> when i receive messages with 8-bit content-transfer-encoding and characters
>> in the range 0x80--0x9f (which often happens when i receive messages
>> in UTF-8).
> I fear that this is a strong limitation of Mule for Latin characters.
> A kind that may be very hard to repair.
Emacs still doesn't support UTF-8 encoding. But, I've just
finished the work for handling 0x80..0x9f bytes in a better
way in the developping code of Emacs 21. With that, those
characters can appear even in a multibyte buffer without
being combined with the following 0xa0..0xff bytes. And,
thus, code conversion is now reversible.
And, although the external package Mule-UCS supports UTF-8
encoding, as you already know, it can handle only such
characters that Emacs supports. But, we have agreed on
adding a new (Emacs internal) charset
`mule-unicode-0100-24ff' which contains Unicode characters
of the range U+0100..U+24FF (thus convers all Cyrillic
characters). On reading UTF-8, Mule-UCS at first tries to
map Cyrillic characters of cyrillic-8859-5, but if
impossible, map to mule-unicode-0100-24ff.
>> I store mails in nnmbox backend, and when i receive such a message,
>> i get ENORMOUS time delays when pressing `g' in a group buffer, and
>> article numbering gets broken (displayed number of articles in a group
>> is overestimated), and such things. I think this is because Emacs uses
>> "intelligent" auto-detection algorithm which wants to interpret a `mbox'
>> buffer as if it were in some charset (mbox is opened in raw mode, but
>> this does not help to switch of this "intelligent" behavior, and certain
>> character combinations choke Emacs). This is a long-standing bug which
>> is there for more than a year, but i don't know how to report it... :-(
Which mail program are you using? Gnus?
---
Ken'ichi HANDA
handa@etl.go.jp
next prev parent reply other threads:[~2000-04-26 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 6:13 Florian Weimer
2000-04-21 9:52 ` Roman Belenov
2000-04-21 11:14 ` Simon Josefsson
2000-04-24 18:20 ` Vladimir Volovich
2000-04-25 21:59 ` Florian Weimer
2000-04-26 6:29 ` Vladimir Volovich
2000-04-26 20:49 ` François Pinard
2000-04-26 23:35 ` Kenichi Handa [this message]
2000-04-30 18:21 ` Florian Weimer
2000-04-26 11:20 Janusz S. Bien
2000-04-30 21:21 Janusz S. Bien
2000-05-01 7:08 ` Florian Weimer
2000-05-01 11:41 ` 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=200004262335.IAA15704@etlken.etl.go.jp \
--to=handa@etl.go.jp \
--cc=ding@gnus.org \
--cc=vvv@vvv.vsu.ru \
/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).