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: Fri, 19 Oct 2007 18:31:50 +0900	[thread overview]
Message-ID: <b4mejfrsb5l.fsf@jpl.org> (raw)
In-Reply-To: <m28x5ztt4y.fsf@gmail.com>

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

>>>>> William Xu wrote:

> I created `gbk_test' file(attached) with `iconv -f utf-8 -t gbk'. Now if
> i try to open it inside emacs, i got exactly same results as Reiner's..

Er, utf-8 converts the charset of text.  For instance, the
following line is displayed with all the Japanese letters in
my Emacs (`current-language-environment' is "Japanese"):

>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>| 我建議 也可以去 gcin 的 mailing list 問問看...

(split-char ?我) => (japanese-jisx0208 50 102)
(split-char ?建) => (japanese-jisx0208 55 122)

You get different results?

It suggests that it will probably be meaningless to examine the
Chinese text that was encoded by utf-8 once.  So, I think what
we need is the original message.

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. ;-)
\f

[-- Attachment #2: HELLO --]
[-- Type: text/plain, Size: 16 bytes --]

你好,元气,开发

  reply	other threads:[~2007-10-19  9:31 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 [this message]
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
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=b4mejfrsb5l.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).