From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Unknown charset: gbk
Date: Fri, 19 Oct 2007 19:26:50 +0900 [thread overview]
Message-ID: <b4mk5pj8knp.fsf@jpl.org> (raw)
In-Reply-To: <b4mejfrsb5l.fsf@jpl.org>
>>>>> Katsumi Yamaoka wrote:
> The gbk text that I made using Emacs Unicode-2 is in the next
> page. It looks fine in Unicode-2, but is displayed with all
> boxes in Emacs 23.0.50. ;-)
The gbk text was displayed correctly if Emacs 23.0.50 did not
load the mule-gbk package. So, maybe it's better to use Emacs's
cp936 than mule-gbk, and Reiner's solution was right.
(I'll be inactive until Monday. Sorry.)
next prev parent reply other threads:[~2007-10-19 10:26 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 [this message]
2007-10-19 11:01 ` William Xu
2007-10-19 21:51 ` jidanni
2007-10-22 7:11 ` Katsumi Yamaoka
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=b4mk5pj8knp.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).