Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Unknown charset: gbk
Date: Mon, 22 Oct 2007 16:11:17 +0900	[thread overview]
Message-ID: <b4mbqaripyi.fsf@jpl.org> (raw)
In-Reply-To: <87tzomu61s.fsf@jidanni.org>

[-- Attachment #1: Type: text/plain, Size: 717 bytes --]

>>>>> jidanni@jidanni.org wrote:

> OK, here's another GBK message, wrapped super safely with shar(1).

At least for this message, making `gbk' be an alias to `cp936'
in Gnus is a bad idea.  Reiner?  I could reproduce \NNN using
Emacs 22.1 and the current Emacs trunk.  The cp936 coding system
in those versions of Emacsen seems to be incomplete for gbk text.

OTOH, Unicode 2 (i.e. Emacs 23.0.60) and the iconv command (both
support gbk) look good.  Therefore, I tried creating the gbk
coding system for Mule version 5 (i.e. Emacs 21.1-23.0.50) using
iconv.  I use:

$ iconv --version
iconv (GNU libc) 2.6

and Mule-UCS for Emacs 21.x.  If you try this module, you have
to load (or require) it before loading Gnus.


[-- Attachment #2: mule5-gbk.el --]
[-- Type: application/emacs-lisp, Size: 2018 bytes --]

  reply	other threads:[~2007-10-22  7:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 14:17 jidanni
2007-10-08 18:15 ` Reiner Steib
2007-10-10 18:02   ` Reiner Steib
2007-10-18 21:40     ` Reiner Steib
2007-10-19  3:01     ` William Xu
2007-10-19  7:33       ` Katsumi Yamaoka
2007-10-19  8:18         ` William Xu
2007-10-19  9:31           ` Katsumi Yamaoka
2007-10-19 10:26             ` Katsumi Yamaoka
2007-10-19 11:01             ` William Xu
2007-10-19 21:51               ` jidanni
2007-10-22  7:11                 ` Katsumi Yamaoka [this message]
2007-10-22 18:44                   ` Reiner Steib
2007-10-22 22:38                     ` Katsumi Yamaoka

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=b4mbqaripyi.fsf@jpl.org \
    --to=yamaoka@jpl.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).