From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: lekktu@gmail.com, jasonr@gnu.org, emacs-devel@gnu.org
Subject: Re: Choice of fonts displaying etc/HELLO
Date: Wed, 06 Aug 2008 20:56:34 +0300 [thread overview]
Message-ID: <usktijact.fsf@gnu.org> (raw)
In-Reply-To: <E1KQbbD-0005D0-LW@etlken.m17n.org>
> From: Kenichi Handa <handa@m17n.org>
> CC: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org
> Date: Wed, 06 Aug 2008 14:30:15 +0900
>
> In article <uzlnrjpp5.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>
> > I think the only meaningful categories are those defined by Unicode.
> > That is, a block of Cyrillic characters should have the cyrillic
> > category, the block of Japanese characters should have japanese
> > category, etc.
>
> Unfortunately, there's no such block as "Japanese" in
> Unicode.
Sorry, I meant Katakana and Hiragana.
> > What kind of backward compatibility problems could we cause? Who or
> > what code depends on these categories?
>
> (re-search-forward "\\cj") can effectively search for
> characters belonging to Japanese charset. It is used, for
> instance, in japanese-hankaku-region (in japan-util.el), and
> "\\cc" is used in encode-hz-region (in china-util.el).
Well, would it still work if "\\cj" matches Katakana and Hiragana
characters?
next prev parent reply other threads:[~2008-08-06 17:56 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
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 [this message]
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=usktijact.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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.