From: Kenichi Handa <handa@m17n.org>
Cc: overlord@gmx.li
Subject: Re: Broken charset=utf-16be articles with Gnus and Emacs 21.3
Date: Mon, 31 Mar 2003 10:51:20 +0900 (JST) [thread overview]
Message-ID: <200303310151.KAA14926@etlken.m17n.org> (raw)
In-Reply-To: <v9adfeig1c.fsf@marauder.physik.uni-ulm.de> (message from Reiner Steib on Sat, 29 Mar 2003 12:11:11 +0100)
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
next prev parent reply other threads:[~2003-03-31 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 11:11 Broken charset=utf-16be articles with Gnus and Emacs 21.3 Reiner Steib
2003-03-31 1:51 ` Kenichi Handa [this message]
2003-03-31 4:55 ` Jesper Harder
2003-03-31 13:41 ` Reiner Steib
2003-03-31 16:14 ` Mark Trettin
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=200303310151.KAA14926@etlken.m17n.org \
--to=handa@m17n.org \
--cc=overlord@gmx.li \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.