unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: What exactly is chinese-big5?
Date: Fri, 18 Apr 2008 11:16:39 +0300	[thread overview]
Message-ID: <u4p9zr314.fsf@gnu.org> (raw)
In-Reply-To: <E1JmfSZ-0004LZ-U3@etlken.m17n.org>

> From: Kenichi Handa <handa@m17n.org>
> CC: emacs-devel@gnu.org
> Date: Fri, 18 Apr 2008 10:32:15 +0900
> 
> Emacs supports full range of Big5 code space; i.e. 
>    1st byte: 0xA1 .. 0xFE
>    2nd byte: 0x40 .. 0x7E and 0xA1 .. 0xFE

Thank you for the detailed explanations.

> In Emacs 22, you can read the written file by utf-8 and
> search for U+FFFD.

Is U+FFFD the _only_ character that will be produced for any codepoint
that is unassigned in the Big5 code space?  That is, if I search for
U+FFFD, will I find _all_ the places where the original file had
something not belonging to Big5?

Also, assuming that I find one or more invalid characters, is there
some encoding other than chinese-big5 that I should try, which could
explain those problematic characters, besides those I mentioned in my
original message?  This file came from Chinese speaking people, so
there's little doubt it should include only strings that can be read
by Chinese speakers.  Therefore, I wonder how come it does not
translate cleanly into Unicode.  (I cannot ask the people who produced
the file about these issues, since they seem to be pretty ignorant
about that: they claimed the file was in UTF-8...)

Thanks again for you help.




  reply	other threads:[~2008-04-18  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 11:15 What exactly is chinese-big5? Eli Zaretskii
2008-04-18  1:32 ` Kenichi Handa
2008-04-18  8:16   ` Eli Zaretskii [this message]
2008-04-18 11:28     ` Kenichi Handa
2008-04-18 12:47       ` Eli Zaretskii
2008-04-18 13:37         ` Jason Rumney
2008-04-18 15:52           ` Eli Zaretskii
2008-04-18 13:26       ` Jason Rumney

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u4p9zr314.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).