From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: emacs-devel@gnu.org
Subject: Re: problems on inline input on Mac
Date: Fri, 28 Jul 2006 14:19:03 +0900 [thread overview]
Message-ID: <wly7uefgs8.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <20060728.125820.34684979.kazu@iij.ad.jp>
>>>>> On Fri, 28 Jul 2006 12:58:20 +0900 (JST), Kazu Yamamoto (山本和彦) <kazu@iij.ad.jp> said:
> Other inline input mechanisms (like "tamago") makes use of buffer
> itself. I guess many people agree that this approach is good.
It would be helpful to think the TSM support (including inline input
support) on Mac corresponds to the XIM support on X11 rather than
Emacs-level input methods such as tamago and leim. Then I think
you'll naturally understand its behavior.
> Unfortunately, the inline input of Mac makes use of overlay instead
> of buffer. This approach causes some problems:
> * Even if the target buffer is read-only, we can input Hiragana and
> Kanji. Read-only errors occur just after we complete strings (ie
> inserting the completed strings from the overlay to the buffer).
The use of overlay strings is intentional and has some reasons.
* Since TSM support corresponds to XIM, it is natural not to change
the buffer contents until the user confirms the text.
* Some keyboard layouts require to show unconfirmed (preedit) text
even when we input some ASCII characters such as "`". There may
be some key binding including "`" that is also allowed to operate
on read-only buffers.
Moreover, you cannot tell in general not only whether the target
buffer is read-only but also which is the target buffer at the stage
of passing input events to TSM using SendEventToEventTarget in
XTread_socket.
> * Since Hiragana and Kanji are hold in an overlay, text properties
> of the buffer is not inherited during input. Of course, after
> completing strings, the properties are inherited by the strings.
They are inherited from those just after the (empty) overlay. You
cannot tell whether the user wants to inherit them from those before
or after it.
> So, I would like to ask to change the implementation of inline input
> on Mac from using overlay to using direct buffer.
I've made some email exchanges with Hashimoto-san (the author of
"inline-patch") on the above issues in Japanese. I will send you some
of them if he agrees.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2006-07-28 5:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 3:58 problems on inline input on Mac Kazu Yamamoto
2006-07-28 5:19 ` YAMAMOTO Mitsuharu [this message]
2006-07-28 5:49 ` Miles Bader
2006-07-28 6:37 ` YAMAMOTO Mitsuharu
2006-07-28 6:50 ` Kazu Yamamoto
2006-07-29 3:32 ` YAMAMOTO Mitsuharu
2006-07-28 6:52 ` YAMAMOTO Mitsuharu
2006-07-28 7:06 ` YAMAMOTO Mitsuharu
2006-07-28 7:23 ` Stefan Monnier
2006-07-29 3:27 ` YAMAMOTO Mitsuharu
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=wly7uefgs8.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@gnu.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 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.