all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: mah@everybody.org, jdsmith@as.arizona.edu, emacs-devel@gnu.org
Subject: Re: xml-parse-file and text properties
Date: Fri, 21 Jul 2006 17:14:21 +0900	[thread overview]
Message-ID: <E1G3q9N-0004Eb-00@etlken> (raw)
In-Reply-To: <uu05bh130.fsf@gnu.org> (message from Eli Zaretskii on Fri, 21 Jul 2006 10:24:51 +0300)

In article <uu05bh130.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

>> > 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!
>> 
>> ??? Composition is just a text property.  It doesn't change
>> the character sequence.  It just changes how characters are
>> displayed.

> If the text is displayed differently due to loss of the composition
> property, would it still be readable by those who know the language?

It depends on language/script and the depth of knowledge.

> If not, then removing the composition property _does_ have the effect
> of changing the text _as_i_is_displayed_to_the_user_.

Of course I understand that.  But, in the context of XML
handling, I don't know what is the problem other than the
logical sequence of characters.

---
Kenichi Handa
handa@m17n.org

  reply	other threads:[~2006-07-21  8:14 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 [this message]
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
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=E1G3q9N-0004Eb-00@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=jdsmith@as.arizona.edu \
    --cc=mah@everybody.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.