From: Kenichi Handa <handa@m17n.org>
Cc: jdsmith@as.arizona.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: xml-parse-file and text properties
Date: Mon, 24 Jul 2006 10:51:16 +0900 [thread overview]
Message-ID: <E1G4pbI-00067V-00@etlken> (raw)
In-Reply-To: <E1G4Jjd-0004fU-D5@fencepost.gnu.org> (message from Richard Stallman on Sat, 22 Jul 2006 11:49:45 -0400)
In article <E1G4Jjd-0004fU-D5@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
> The argument that we need to preserve the `composition' property doesn't
> seem valid: this property can be computed from the sequence of chars.
> Handa, is it true that the composition property can always be recomputed
> from the sequence of characters?
Usually yes, but not always. All normal compositions
(i.e. compositions for displaying a script in the correct
way) are registered in composition-function-table (a
char-table). So, by looking up the table for each
character, we can recover compositions (though very slow).
But, it's possible to manually compose some text. For
instance please try this:
(insert (compose-string "+o" 0 2 '(?+ (tc . bc) ?o)))
It inserts "+o" with composition property that can't be
recovered automatically once lost.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-07-24 1:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 21:35 xml-parse-file and text properties JD Smith
2006-07-20 21:46 ` Richard Stallman
2006-07-20 22:11 ` JD Smith
2006-07-21 4:46 ` Richard Stallman
2006-07-21 6:35 ` Kenichi Handa
2006-07-21 7:24 ` Eli Zaretskii
2006-07-21 8:14 ` Kenichi Handa
2006-07-22 4:39 ` Richard Stallman
2006-07-21 16:13 ` Kevin Rodgers
2006-07-21 23:33 ` Kevin Rodgers
2006-07-20 21:46 ` Richard Stallman
2006-07-20 22:40 ` JD Smith
2006-07-21 12:55 ` Stefan Monnier
2006-07-21 17:34 ` JD Smith
2006-07-21 20:22 ` Stefan Monnier
2006-07-21 21:50 ` JD Smith
2006-07-22 15:49 ` Richard Stallman
2006-07-24 1:51 ` Kenichi Handa [this message]
2006-07-24 3:17 ` Stefan Monnier
2006-07-24 4:36 ` Kenichi Handa
2006-07-24 18:22 ` Richard Stallman
2006-07-24 20:38 ` Stuart D. Herring
2006-07-25 3:09 ` Richard Stallman
2006-07-25 14:00 ` Stefan Monnier
2006-07-25 22:15 ` Richard Stallman
2006-07-24 20:51 ` Stefan Monnier
2006-07-25 3:09 ` Richard Stallman
2006-07-21 20:52 ` Thien-Thi Nguyen
2006-07-21 21:45 ` JD Smith
2006-07-22 9:15 ` Eli Zaretskii
2006-07-24 16:44 ` JD Smith
2006-07-25 16:05 ` JD Smith
2006-07-25 16:27 ` Stefan Monnier
2006-07-25 19:16 ` JD Smith
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=E1G4pbI-00067V-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=jdsmith@as.arizona.edu \
--cc=monnier@iro.umontreal.ca \
/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).