From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: xml-parse-file and text properties Date: Fri, 21 Jul 2006 17:14:21 +0900 Message-ID: References: <1153433461.32596.48.camel@turtle.as.arizona.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1153469768 25862 80.91.229.2 (21 Jul 2006 08:16:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 21 Jul 2006 08:16:08 +0000 (UTC) Cc: mah@everybody.org, jdsmith@as.arizona.edu, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 21 10:16:04 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G3qAU-0001g3-Hj for ged-emacs-devel@m.gmane.org; Fri, 21 Jul 2006 10:15:30 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G3qAT-0002yA-QO for ged-emacs-devel@m.gmane.org; Fri, 21 Jul 2006 04:15:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G3qAJ-0002y5-4w for emacs-devel@gnu.org; Fri, 21 Jul 2006 04:15:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G3qAH-0002xt-GW for emacs-devel@gnu.org; Fri, 21 Jul 2006 04:15:18 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G3qAH-0002xq-Cj for emacs-devel@gnu.org; Fri, 21 Jul 2006 04:15:17 -0400 Original-Received: from [150.29.246.133] (helo=mx1.aist.go.jp) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G3qAa-0003aQ-QS; Fri, 21 Jul 2006 04:15:37 -0400 Original-Received: from smtp4.aist.go.jp ([150.29.246.12]) by mx1.aist.go.jp with ESMTP id k6L8F3nn019288; Fri, 21 Jul 2006 17:15:03 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id k6L8F1f1009990; Fri, 21 Jul 2006 17:15:01 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1G3q9N-0004Eb-00; Fri, 21 Jul 2006 17:14:21 +0900 Original-To: Eli Zaretskii In-reply-to: (message from Eli Zaretskii on Fri, 21 Jul 2006 10:24:51 +0300) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:57417 Archived-At: In article , Eli Zaretskii 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