From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: xml-parse-file and text properties Date: Sat, 22 Jul 2006 00:39:27 -0400 Message-ID: References: <1153433461.32596.48.camel@turtle.as.arizona.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1153543402 2220 80.91.229.2 (22 Jul 2006 04:43:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 22 Jul 2006 04:43:22 +0000 (UTC) Cc: mah@everybody.org, emacs-devel@gnu.org, jdsmith@as.arizona.edu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 22 06:43:19 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 1G49Kg-0007E6-Tl for ged-emacs-devel@m.gmane.org; Sat, 22 Jul 2006 06:43:19 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G49Kg-0000eH-DX for ged-emacs-devel@m.gmane.org; Sat, 22 Jul 2006 00:43:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G49H3-00075Y-8a for emacs-devel@gnu.org; Sat, 22 Jul 2006 00:39:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G49H2-00075C-Mp for emacs-devel@gnu.org; Sat, 22 Jul 2006 00:39:32 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G49H2-000756-HW for emacs-devel@gnu.org; Sat, 22 Jul 2006 00:39:32 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G49Hb-0001pn-4p for emacs-devel@gnu.org; Sat, 22 Jul 2006 00:40:07 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1G49Gx-0005I5-Pp; Sat, 22 Jul 2006 00:39:27 -0400 Original-To: Kenichi Handa In-reply-to: (message from Kenichi Handa on Fri, 21 Jul 2006 15:35:03 +0900) 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:57464 Archived-At: ??? Composition is just a text property. It doesn't change the character sequence. It just changes how characters are displayed. If it replaces two characters with one character, that makes a difference what the text is. You've said that users would perceive them as different characters. Does the composition property affect the sequence of characters that would be written to a file? I have a vague memory that it does. In emacs-unicode-2, loosing of composition property has no problem because I've implemented a code to construct composition automatically in display engine. That definitely seems like an improvement; could you tell me more? However, at present, we need to make the right things happen in Emacs 22. > 1. Distinguish composition properties from others, and make functions > like buffer-substring-no-properties preserve composition properties, > even as they discard all other properties. > Can #1 work? I don't know. If text properties causes a problem in XML, #1 doesn't solve the current problem. If text properties is not a problem, we don't need #1. He said that the text properties in XML cause a serious problem when they are numerous. Keeping all is no good; discarding all text properties would be wrong when there is a composition property. However, keeping just the composition property would be fine, since most of the time there won't be any of them. However, the problem of losing composition properties is not limited to XML.