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: Mon, 24 Jul 2006 10:51:16 +0900 Message-ID: References: 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 1153705942 4781 80.91.229.2 (24 Jul 2006 01:52:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Jul 2006 01:52:22 +0000 (UTC) Cc: jdsmith@as.arizona.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 24 03:52:21 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 1G4pcJ-0001PX-QN for ged-emacs-devel@m.gmane.org; Mon, 24 Jul 2006 03:52:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4pcJ-0004jn-9G for ged-emacs-devel@m.gmane.org; Sun, 23 Jul 2006 21:52:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G4pc7-0004ji-V7 for emacs-devel@gnu.org; Sun, 23 Jul 2006 21:52:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G4pc6-0004jW-N3 for emacs-devel@gnu.org; Sun, 23 Jul 2006 21:52:07 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G4pc6-0004jT-FN for emacs-devel@gnu.org; Sun, 23 Jul 2006 21:52:06 -0400 Original-Received: from [150.29.246.133] (helo=mx1.aist.go.jp) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G4pd4-0001DP-J6; Sun, 23 Jul 2006 21:53:07 -0400 Original-Received: from smtp3.aist.go.jp ([150.29.246.12]) by mx1.aist.go.jp with ESMTP id k6O1q2qw028922; Mon, 24 Jul 2006 10:52:02 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id k6O1pwMa001317; Mon, 24 Jul 2006 10:51:58 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1G4pbI-00067V-00; Mon, 24 Jul 2006 10:51:16 +0900 Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Sat, 22 Jul 2006 11:49:45 -0400) 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:57516 Archived-At: In article , Richard Stallman writes: > The argument that we need to preserve the `composition' property doesn't > seem valid: this property can be computed from the sequence of chars. > Handa, is it true that the composition property can always be recomputed > from the sequence of characters? 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). But, it's possible to manually compose some text. For instance please try this: (insert (compose-string "+o" 0 2 '(?+ (tc . bc) ?o))) It inserts "+o" with composition property that can't be recovered automatically once lost. --- Kenichi Handa handa@m17n.org