[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Broken charset=utf-16be articles with Gnus and Emacs 21.3
|
From: |
Kenichi Handa |
|
Subject: |
Re: Broken charset=utf-16be articles with Gnus and Emacs 21.3 |
|
Date: |
Mon, 31 Mar 2003 10:51:20 +0900 (JST) |
|
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.2.92 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
In article <v9adfeig1c.fsf@marauder.physik.uni-ulm.de>, Reiner Steib
<4.uce.03.r.s@nurfuerspam.de> writes:
> Actions to reproduce the bug:
> - Start Gnus `M-x gnus RET' and compose an article `a'.
> - Switch to TeX input method: `M-x set-input-method RET TeX RET'
> - Enter some characters:
> \sigma ä (a with diaeresis) \omega
> (Note: \sigma and \omega (without ä) is not sufficient.)
> .. *or* ...
> \sigma \omega \alpha \o \int
> - Preview `M-m P' (or `C-u M-m P') or send the message.
> The preview (and the outgoing message) will be encoded with
> "Content-Type: text/plain; charset=utf-16be" and it will not be
> readable with Gnus and most other MUAs or newsreaders.
> I've been told (-> Simon Krahnke) that the result isn't even correct
> UTF-16.
Oops, I've just found that Emacs' coding systems utf-16-le
and utf-16-be produce BOM (Byte Order Mark) which is a bug
according to their specifications. I've just installed a
fix.
> Expected behavior:
> - The article should be encoded with
> "Content-Type: text/plain; charset=utf-8".
I don't know why GNUS prefers utf-16-X to utf-8. At least,
sort-coding-systems prefers utf-8.
---
Ken'ichi HANDA
handa@m17n.org