Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
Cc: TSUCHIYA Masatoshi <tsuchiya@pine.kuee.kyoto-u.ac.jp>
Subject: Re: Decoding ISO8859-15 -- offending headers
Date: Mon, 19 Aug 2002 12:14:59 +0900	[thread overview]
Message-ID: <0461972e-ff17-49e4-9344-00dd20b42b14@deisui.org> (raw)
In-Reply-To: <iluptwg2zlg.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sun, 18 Aug 2002 13:08:59 +0200")

>>>>> In <iluptwg2zlg.fsf@latte.josefsson.org> 
>>>>>	Simon Josefsson <jas@extundo.com> wrote:

> I think I found the patch.  I'll boot XEmacs to see what is breaking.
> Masatoshi, do you remember the details?

> 	* gnus-group.el (gnus-group-name-decode): Don't test
> 	multibyte-string, because it breaks XEmacs.

I should comment on this because I suggested him to remove the multibyte
check.  And, for my real intention, I can't read any Japanese newsgroups
whose names are encoded in UTF-8[1] without the patch.

I'll show you why the old group name encoder/decoder went wrong for
both GNU Emacs and XEmacs-MULE.

XEmacs-MULE: Without the patch, all the group names will be decoded
twice because the current implementation of `mm-multibyte-string-p'
for XEmacs is just an alias to `ignore'.  Unfortunately, we can't
implement working multibyte-string-p for XEmacs-MULE because
XEmacs-MULE uses a Latin-1 character so as to represent a byte in the
range from 160 to 255.  See the last paragraph of
"(internals)Character Sets" for details.

GNU Emacs: nntp-server-buffer is marked as multibyte.  A string picked
from the buffer is always regarded as multibyte, unless it doesn't
contain a non-ASCII character.

Footnotes: 
[1]  Section 5.5. in USEFOR draft:
<http://www.ietf.org/internet-drafts/draft-ietf-usefor-article-07.txt>
-- 
Daiki Ueno



  parent reply	other threads:[~2002-08-19  3:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  6:33 Jonas Steverud
2002-07-26 19:39 ` Simon Josefsson
2002-07-27  9:09   ` Jonas Steverud
2002-07-27 14:03     ` Simon Josefsson
2002-07-27 15:17       ` Jonas Steverud
2002-07-27 20:45         ` Simon Josefsson
2002-07-27 21:42           ` Simon Josefsson
2002-07-28  8:46           ` Jonas Steverud
2002-07-28 14:04           ` Reiner Steib
2002-07-29 11:44             ` Simon Josefsson
2002-07-29 14:13               ` Reiner Steib
2002-07-31 15:35                 ` Simon Josefsson
2002-08-01  6:37                   ` Jonas Steverud
2002-08-18  8:42                   ` Jonas Steverud
2002-08-18 10:27                     ` Simon Josefsson
2002-08-18 10:46                       ` Jonas Steverud
2002-08-18 11:08                         ` Simon Josefsson
2002-08-18 11:38                           ` Jonas Steverud
2002-08-19  3:14                           ` Daiki Ueno [this message]
2002-08-19  6:53                             ` Jonas Steverud
2002-08-19  8:54                               ` Kai Großjohann
2002-08-19  9:13                                 ` Simon Josefsson
2002-08-19  9:12                             ` Simon Josefsson
2002-08-19 11:05                               ` Kai Großjohann
2002-08-19 14:28                                 ` Simon Josefsson
2002-08-19 17:02                                   ` Kai Großjohann
2002-08-19 17:13                                     ` Simon Josefsson

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=0461972e-ff17-49e4-9344-00dd20b42b14@deisui.org \
    --to=ueno@unixuser.org \
    --cc=tsuchiya@pine.kuee.kyoto-u.ac.jp \
    /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).