unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org, handa@m17n.org, jasonr@gnu.org
Subject: Re: Choice of fonts displaying etc/HELLO
Date: Mon, 11 Aug 2008 17:48:26 +0900	[thread overview]
Message-ID: <87proglyxx.fsf@catnip.gol.com> (raw)
In-Reply-To: <uhc9wk8he.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 07 Aug 2008 21:03:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:
>> > I meant would it break something if "\\cj" matched only the Katakana
>> > and Hiragana characters instead of what it matches today?
>> 
>> I don't know what it would break, but that doesn't seem like
>> particularly intuitive behavior.
>
> ??? Why not?

Because Japanese as a language uses more than just Katakana and
Hiragana.  You are (apparently) suggesting that \\cj match only
characters that are _uniquely_ japanese, and while that might be an
interesting predicate in some cases, it doesn't seem particularly useful
in general (well to me anyway).

If there's any use at _all_ for the \\c feature, then it should match
how japanese is actually written, rather than "a random subset which
happens to be trivial to implement from the set of data we have
available today".

>> I think emacs' concept of characters belonging to multiple language
>> categories is pretty neat actually.
>
> Maybe I'm missing something, but I don't see how the fact that, say,
> Cyrillic characters are claimed to belong to Japanese category could
> be considered ``neat''.

I didn't say that all the particular results of that functionality were
good -- cyrillic as japanese is one example of where it's silly.

However the _ability_ to have characters belong to multiple categories
is a good thing, and I think it fits the natural way people think of
them.

-Miles

-- 
Idiot, n. A member of a large and powerful tribe whose influence in human
affairs has always been dominant and controlling.




  parent reply	other threads:[~2008-08-11  8:48 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
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 [this message]
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

  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=87proglyxx.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=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 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).