From: Charles Muller <acmuller@gol.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Chinese characters support
Date: Sun, 11 May 2003 02:31:49 +0900 (JST) [thread overview]
Message-ID: <20030511.023149.92589622.acmuller@gol.com> (raw)
In-Reply-To: <84he8292dt.fsf@lucy.is.informatik.uni-duisburg.de>
Kai wrote:
> Really? The HELLO file shows characters from a lot of different
> encodings, and if used as such, then it is quite useful.
>
> > and it is quite often the case that that file will display fine
> > despite the fact that CJK won't work in utf-8
>
> There are known problems with CJK support in UTF-8, but the situation
> has improved greatly in the development version of Emacs.
I know that, and I am not contesting that point. But again, the HELLO file
is not a utf-8 file. It is also not a form of JIS or other East Asian
encoding, so the fact that one can display multilingual scripts by opening
that file does not mean that they will be able to display them in Big5, JIS,
or whatever. If you check the archives for "utf-8+cjk", you will see that we have had a few
threads in the past year that dealt with problems trying to display CJK and
other international scripts, in which the advice was given to look at the
Hello file. As a person who has been working with international scripts and
utf-8 for a number years, I know firsthand the ability to be able to read
this file doesn't usually mean much. People who recommend checking this file
are usually people who don't use double-byte East Asian languages.
> The file is in a relevant encoding: it's the encoding used by Emacs
> internally. (Or rather, an encoding close to the internal encoding.)
Relevant to whom? It's not in utf-8, right? Most of the problems people have
been having with CJK display in Emacs (at least until the appearance of
21.3.5) have to do with problems getting utf-8 to work, and the hello file
will still display even when these problems are not resolved.
No one that I know who works in XML or with East Asian international scripts
works in utf-7, so while that encoding format may be relevant for those who
are programming Emacs internally, it is not relevant for anyone using Emacs
to do multilingual XML or HTML publication, because no one uses it. That's
what I mean when I say "not relevant."
It is not my purpose to badmouth Emacs handling of Unicode. I know that
people have been working very hard to resolve these problems, and from what
I have been hearing, once everyone has copies of 21.3.5 installed with the
right Mule setup, this will be a past issue. Hopefully, somewhere along the
line, the Hello file will also graduate to utf-8.
Regards,
Chuck
---------------------------
Charles Muller <acmuller@gol.com>
Faculty of Humanities, Toyo Gakuen University
Digital Dictionary of Buddhism and CJKV-English Dictionary [http://www.acmuller.net]
H-Buddhism List Editor [http://www2.h-net.msu.edu/~buddhism/]
Mobile Phone: 090-9310-1787
next prev parent reply other threads:[~2003-05-10 17:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5730.1052348993.21513.help-gnu-emacs@gnu.org>
2003-05-10 14:26 ` Chinese characters support Kai Großjohann
2003-05-10 16:17 ` Charles Muller
2003-05-10 16:45 ` Kai Großjohann
2003-05-10 17:31 ` Charles Muller [this message]
2003-05-10 18:43 ` Eli Zaretskii
2003-05-11 2:11 ` Charles Muller
2003-05-11 3:32 ` Eli Zaretskii
2003-05-11 13:59 ` Charles Muller
[not found] ` <mailman.5976.1052661651.21513.help-gnu-emacs@gnu.org>
2003-05-12 19:29 ` Jason Rumney
2003-05-12 19:58 ` Kai Großjohann
2003-05-13 7:40 ` Lee Sau Dan
2003-05-13 9:57 ` acmuller
2003-05-13 10:02 ` Robin Hu
2003-05-15 8:07 ` Lee Sau Dan
2003-05-10 19:24 ` Kai Großjohann
2003-05-11 2:15 ` Charles Muller
2003-05-11 3:34 ` Eli Zaretskii
[not found] ` <mailman.5956.1052619415.21513.help-gnu-emacs@gnu.org>
2003-05-12 19:56 ` Kai Großjohann
2003-05-13 3:36 ` Charles Muller
2003-05-14 3:14 ` Eli Zaretskii
[not found] ` <mailman.6084.1052797097.21513.help-gnu-emacs@gnu.org>
2003-05-13 7:05 ` Kai Großjohann
2003-05-14 6:14 ` Lee Sau Dan
2003-05-14 16:27 ` Kai Großjohann
2003-05-14 21:07 ` Jason Rumney
[not found] ` <mailman.5927.1052587973.21513.help-gnu-emacs@gnu.org>
2003-05-12 19:27 ` Jason Rumney
2003-05-13 7:40 ` Lee Sau Dan
2003-05-13 10:11 ` acmuller
2003-05-13 10:54 ` Charles Muller
[not found] ` <mailman.6097.1052826249.21513.help-gnu-emacs@gnu.org>
2003-05-15 8:07 ` Lee Sau Dan
2003-05-10 17:58 ` Eli Zaretskii
[not found] ` <mailman.5936.1052589798.21513.help-gnu-emacs@gnu.org>
2003-05-13 7:40 ` Lee Sau Dan
2003-05-14 3:15 ` Eli Zaretskii
[not found] ` <mailman.6156.1052882447.21513.help-gnu-emacs@gnu.org>
2003-05-15 8:07 ` Lee Sau Dan
2003-05-16 11:36 ` Eli Zaretskii
2003-05-12 23:05 ` Michael Na Li
2003-05-13 7:02 ` Kai Großjohann
[not found] ` <mailman.5922.1052583563.21513.help-gnu-emacs@gnu.org>
2003-05-13 7:40 ` Lee Sau Dan
2003-05-07 23:08 Gaoyan Xie
2003-05-08 6:27 ` Charles Muller
[not found] ` <mailman.5739.1052375326.21513.help-gnu-emacs@gnu.org>
2003-05-08 7:33 ` Robin Hu
2003-05-10 14:28 ` Kai Großjohann
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=20030511.023149.92589622.acmuller@gol.com \
--to=acmuller@gol.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).