unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: Re: Word boundary (was: find-composition still depends on the	composition property)
Date: Sun, 26 Oct 2008 21:32:09 +0200	[thread overview]
Message-ID: <ubpx7xidi.fsf@gnu.org> (raw)
In-Reply-To: <E1Ku5mn-0001Hd-VE@etlken.m17n.org>

> From: Kenichi Handa <handa@m17n.org>
> CC: juri@jurta.org, emacs-devel@gnu.org
> Date: Sun, 26 Oct 2008 22:36:05 +0900
> 
> In article <uskqka6xq.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Unless I'm missing something important, my reading of th UAX #29
> > (http://www.unicode.org/reports/tr29/tr29-13.html) is that almost all
> > scripts should _not_ have word breaks between letters and digits.  And
> > neither should we define a word break on script boundaries, in most
> > cases.
> 
> Although it says "Do not break between most letters. ALetter
> x ALetter", ALetter doesn't include Han, Katakana, and
> Hiragana.

Yes, that's why I said "in most cases".

> And, it also has this note:
> 
> Normally word breaking does not require breaking between
> different scripts. However, adding that capability may be
> useful in combination with other extensions of word
> segmentation. For example, ...

So maybe we should have a user option to enable that, but I think it
should be off by default.




  reply	other threads:[~2008-10-26 19:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 13:46 find-composition still depends on the composition property Juanma Barranquero
2008-09-05  1:24 ` Kenichi Handa
2008-10-19 23:15   ` Juri Linkov
2008-10-20  6:46     ` Kenichi Handa
2008-10-21 23:46       ` Juri Linkov
2008-10-22  1:17         ` Kenichi Handa
2008-10-22  4:25           ` Eli Zaretskii
2008-10-22  5:43             ` Kenichi Handa
2008-10-22  5:29           ` Kenichi Handa
2008-10-22 19:35             ` Eli Zaretskii
2008-10-23  1:18               ` Kenichi Handa
2008-10-23 23:44                 ` describe-categories (was: find-composition still depends on the composition property) Juri Linkov
2008-10-25  1:37                   ` Kenichi Handa
2008-10-25  8:33                     ` Eli Zaretskii
2008-10-23 23:48                 ` Word boundary " Juri Linkov
2008-10-25 18:03                   ` Eli Zaretskii
2008-10-26 13:36                     ` Kenichi Handa
2008-10-26 19:32                       ` Eli Zaretskii [this message]
2008-10-27  0:17                         ` Word boundary Miles Bader
2008-10-27  0:27                           ` Kenichi Handa
2008-10-27  4:12                             ` Eli Zaretskii
2008-10-27  5:16                             ` Miles Bader
2008-10-31  5:50                               ` Kenichi Handa
2008-10-26  8:15                   ` Word boundary (was: find-composition still depends on the composition property) Kenichi Handa

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=ubpx7xidi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=juri@jurta.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.
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).