From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: Re: find-composition still depends on the composition property
Date: Wed, 22 Oct 2008 06:25:49 +0200 [thread overview]
Message-ID: <ubpxdfe7m.fsf@gnu.org> (raw)
In-Reply-To: <E1KsSMH-0005T2-Ek@etlken.m17n.org>
> From: Kenichi Handa <handa@m17n.org>
> Date: Wed, 22 Oct 2008 10:17:57 +0900
> Cc: emacs-devel@gnu.org
>
> Ah, it's not a bug of composition, but a bug of scan_words
> (syntax.c). Currently U+301 is labeled as `latin' script,
> and the surrounding characters there are `cyrillic' script.
> Thus, that funciton thinks that there's a word boundary.
> I'll find a way to solve this problem.
I think we will need a user option to control whether scan_words stops
on script boundaries, see the discussion started by Miles yesterday
about a similar problem.
next prev parent reply other threads:[~2008-10-22 4:25 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 [this message]
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
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=ubpxdfe7m.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).