From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: Chinese characters support
Date: Fri, 16 May 2003 14:36:14 +0300 [thread overview]
Message-ID: <7263-Fri16May2003143614+0300-eliz@elta.co.il> (raw)
In-Reply-To: <m365odp6ux.fsf@mika.informatik.uni-freiburg.de> (message from Lee Sau Dan on 15 May 2003 10:07:01 +0200)
> From: Lee Sau Dan <danlee@informatik.uni-freiburg.de>
> Newsgroups: gnu.emacs.help
> Date: 15 May 2003 10:07:01 +0200
>
> >> I don't think so. Unicode will never be able to handle the
> >> "Difference among chinese characters in GB, JIS, KSC, BIG5:"
> >> section in the etc/HELLO file.
>
> Eli> Unicode doesn't, but the Unicode Emacs will. Trust me ;-)
>
> So, you're agreeing that converting HELLO to utf-8 (which only
> represents Unicode) is not a good idea?
I don't know yet. AFAIK, the issue of encoding etc/HELLO in the
Unicode Emacs was not discussed yet, but I expect it to be encoded in
the internal Emacs representation of characters, because that by
definition will support all the characters suppored by Emacs, and do
that unambiguously.
next prev parent reply other threads:[~2003-05-16 11:36 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
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 [this message]
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=7263-Fri16May2003143614+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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).