From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: xml-parse-file and text properties
Date: Fri, 21 Jul 2006 10:13:32 -0600 [thread overview]
Message-ID: <e9qugk$lai$1@sea.gmane.org> (raw)
In-Reply-To: <E1G3muP-0000l5-26@fencepost.gnu.org>
Richard Stallman wrote:
> ;; Note that {buffer-substring,match-string}-no-properties were
> ;; formerly used in several places, but that removes composition info.
>
> but neither of us were clear on the meaning of the statement, or why
> retaining text properties in any XML parsed data would be desirable.
>
> I think I see why. Losing the composition info could mean that the
> composed characters turn into other sequences of characters. It
> literally would change the text!
>
> This is an ugly problem. Many things want to get rid of most text
> properties, but they don't want to forget about composition.
> Logically speaking, composition is really part of the characters in
> the text. Using text properties to encode it is fundamentally
> inconsistent.
>
> We have been lucky so far, in that this inconsistency has not caused a
> lot of problems -- but now our luck is running out.
>
> I can see only two kinds of approaches:
>
> 1. Distinguish composition properties from others, and make functions
> like buffer-substring-no-properties preserve composition properties,
> even as they discard all other properties.
>
> 2. Change the representation of composition so it uses something other
> than text properties.
>
> #2 would be a big maintenance trouble. It would take us a long time
> to get everything working again after such a change. We certainly
> should not install such a change now, and I hope we won't need to do
> it ever.
>
> Can #1 work?
How about extending buffer-substring-no-properties with an optional
KEEP-PROPERTIES argument, a list of text properties to preserve in
the returned string? Then xml-parse-file could call it with the
list of composition properties (whatever they are).
--
Kevin
next prev parent reply other threads:[~2006-07-21 16:13 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 [this message]
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
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='e9qugk$lai$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/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.