From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: Choice of fonts displaying etc/HELLO
Date: Tue, 05 Aug 2008 16:33:06 +0900 [thread overview]
Message-ID: <E1KQH2Y-00024H-6o@etlken.m17n.org> (raw)
In-Reply-To: <uvdykn8rl.fsf@gnu.org> (message from Eli Zaretskii on Fri, 01 Aug 2008 16:51:26 +0300)
In article <uvdykn8rl.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > But is that the right way to categorize them? This character (and others
> > around it) are not Japanese or Korean characters. They just happen to be
> > included in those encodings. The same goes for Cyrillic and Greek
> > characters.
> I agree with Jason. I reported a similar curiosity the moment the
> unicode-2 branch was merged with the trunk.
We don't define the semantics of "category" clearly. We can
think of the category name "Japanese" as "characters
belonging to one of Japanese character set". Then that
character surely have that cateogry. And, in Emacs 22, that
kind of definition was surely useful.
Although, I agree that such kind of definition is not
appropriate now, I have no good idea about how to improve it
without breaking backward compatibility.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-08-05 7:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:49 segmentation fault displaying etc/HELLO on Windows Juanma Barranquero
2008-07-30 6:48 ` Jason Rumney
2008-07-30 11:48 ` Juanma Barranquero
2008-07-30 13:05 ` Jason Rumney
2008-07-30 13:11 ` Jason Rumney
2008-07-30 14:03 ` Juanma Barranquero
2008-07-30 14:19 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Jason Rumney
2008-07-30 15:03 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-07-30 15:26 ` Juanma Barranquero
2008-08-01 12:50 ` Kenichi Handa
2008-08-01 12:56 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Kenichi Handa
2008-08-01 13:17 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-08-01 13:51 ` Eli Zaretskii
2008-08-05 7:33 ` Kenichi Handa [this message]
2008-08-05 18:12 ` Eli Zaretskii
2008-08-06 5:30 ` Kenichi Handa
2008-08-06 6:14 ` Stephen J. Turnbull
2008-08-06 6:29 ` Kenichi Handa
2008-08-06 15:52 ` Stephen J. Turnbull
2008-08-06 17:56 ` Eli Zaretskii
2008-08-07 1:14 ` Kenichi Handa
2008-08-07 3:22 ` Eli Zaretskii
2008-08-07 3:54 ` Kenichi Handa
2008-08-07 4:54 ` Miles Bader
2008-08-07 18:03 ` Eli Zaretskii
2008-08-07 19:30 ` Stephen J. Turnbull
2008-08-11 8:48 ` Miles Bader
2008-08-11 19:03 ` Eli Zaretskii
2008-07-31 1:49 ` segmentation fault displaying etc/HELLO on Windows Kyle M. Lee
2008-07-31 2:03 ` Juanma Barranquero
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=E1KQH2Y-00024H-6o@etlken.m17n.org \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lekktu@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.