From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Emacs Development" <emacs-devel@gnu.org>,
"Kenichi Handa" <handa@m17n.org>
Subject: find-composition still depends on the composition property
Date: Fri, 29 Aug 2008 15:46:12 +0200 [thread overview]
Message-ID: <f7ccd24b0808290646r7ce000aet3aa6af5a1315b9d3@mail.gmail.com> (raw)
So, for example, C-u M-x describe-char does not describe composition
of characters now.
character: ಸ (3256, #o6270, #xcb8)
preferred charset: mule-unicode-0100-24ff (Unicode characters of the
range U+0100..U+24FF.)
code point: 0x3F38
syntax: w which means: word
buffer code: #xE0 #xB2 #xB8
file code: ESC #x24 #x2C #x31 #x3F #x38 (encoded by coding
system iso-2022-7bit-dos)
display: by this font (glyph code)
uniscribe:-outline-Tunga-normal-normal-normal-*-13-*-*-*-p-*-iso10646-1
(#x63)
vs. the output before the change:
character: ಸ (3256, #o6270, #xcb8)
preferred charset: mule-unicode-0100-24ff (Unicode characters of the
range U+0100..U+24FF.)
code point: 0x3F38
syntax: w which means: word
buffer code: #xE0 #xB2 #xB8
file code: ESC #x24 #x2C #x31 #x3F #x38 (encoded by coding
system iso-2022-7bit-dos)
display: composed to form "ಸ್ಕಾ" (see below)
Composed with the following character(s) "್ಕಾ" using this font:
uniscribe:-outline-Tunga-normal-normal-normal-*-13-*-*-*-p-*-iso10646-1
by these glyphs:
[#<font-object
"-outline-Tunga-normal-normal-normal-*-13-*-*-*-p-*-iso10646-1"> 18 8
13 13 9]
[0 3 3256 177 7 8 0 13 9 nil]
[0 3 3256 101 8 8 0 13 9 nil]
[0 3 3256 180 3 3 -2 13 9 nil]
Juanma
next reply other threads:[~2008-08-29 13:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 13:46 Juanma Barranquero [this message]
2008-09-05 1:24 ` find-composition still depends on the composition property 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
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=f7ccd24b0808290646r7ce000aet3aa6af5a1315b9d3@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).