From: Richard Stallman <rms@gnu.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 14:22:05 -0400 [thread overview]
Message-ID: <E1G5549-0002HO-L6@fencepost.gnu.org> (raw)
In-Reply-To: <E1G4pbI-00067V-00@etlken> (message from Kenichi Handa on Mon, 24 Jul 2006 10:51:16 +0900)
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).
Interesting.
But, it's possible to manually compose some text.
We can consider that improper use of the composition property;
we need not cater to it.
That leaves us in a peculiar in-between situation. If discarding
these properties altered what text would be written in a file, it
would be very bad, and it would be clear we need to preserve these
properties. But that is not the case. Nonetheless, the text will
display wrong if subsequently reinserted in a buffer. All in all, I
think that is enough reason for xml.el to preserve the composition
property.
So the question is how.
One first step would be to write a function that operates on a string
and discards all text properties except composition. More generally,
all except a certain specified list of property names.
I think that should be done at the C level for speed.
next prev parent reply other threads:[~2006-07-24 18:22 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
2006-07-24 3:17 ` Stefan Monnier
2006-07-24 4:36 ` Kenichi Handa
2006-07-24 18:22 ` Richard Stallman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1G5549-0002HO-L6@fencepost.gnu.org \
--to=rms@gnu.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 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.