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: [w32] display international HELLO Date: Mon, 19 Nov 2007 11:35:26 +0900 Message-ID: References: <001501c822ab$ccfec5e0$d5101252@JRWXP1> <00d801c82732$0001dfb0$d5101252@JRWXP1> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1195439756 7119 80.91.229.12 (19 Nov 2007 02:35:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 19 Nov 2007 02:35:56 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Richard Wordingham" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 19 03:36:02 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1ItwUT-0006Pb-Bi for ged-emacs-devel@m.gmane.org; Mon, 19 Nov 2007 03:36:01 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ItwUF-0003az-HJ for ged-emacs-devel@m.gmane.org; Sun, 18 Nov 2007 21:35:47 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ItwUB-0003Z4-8J for emacs-devel@gnu.org; Sun, 18 Nov 2007 21:35:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ItwU9-0003XW-Sj for emacs-devel@gnu.org; Sun, 18 Nov 2007 21:35:42 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ItwU9-0003XP-JO for emacs-devel@gnu.org; Sun, 18 Nov 2007 21:35:41 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ItwU8-00032H-Qi for emacs-devel@gnu.org; Sun, 18 Nov 2007 21:35:41 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id lAJ2ZR7I023445; Mon, 19 Nov 2007 11:35:28 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp3.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id lAJ2ZRBw012800; Mon, 19 Nov 2007 11:35:27 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id lAJ2ZQ4w029922; Mon, 19 Nov 2007 11:35:26 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.67) (envelope-from ) id 1ItwTu-0007aR-Jb; Mon, 19 Nov 2007 11:35:26 +0900 In-reply-to: <00d801c82732$0001dfb0$d5101252@JRWXP1> (richard.wordingham@ntlworld.com) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) 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:83604 Archived-At: In article <00d801c82732$0001dfb0$d5101252@JRWXP1>, "Richard Wordingham" writes: >>> 3. Compositions of Lao characters, (i.e. with the 'composition' string >>> property) using the Code2000 font (the only fully working Lao font I >>> have), >>> do not display properly, whether they are in the Lao or >>> mule-unicode-0100-24ff charset. > > I think it's a waste of time to learn composition mechanism > > of Emacs 22. It will be a lot improved in emacs-unicode-2. > Are you talking of future work or the present state of emacs-unicode-2, as > in Emacs 23.0.60.0? I'm talking about the future work, but the latest emacs-unicode-2 code already contains half-done codes. > Are you talking of applying the composition property, > or of the rendering of composed sequences? I'm going to allow each font-backends to generate proper composition information that will vary depending on a font, instead of the current fixed way of composition. So, On Windows, perhaps the font backend can utilize uniscribe. On GNU/Linux, I have not yet decided what to do; using Pango, using m17n-lib, or using a newly written code that directly uses libotf or harfbuzz for OTF handling. I think the last choice will result in the fastest rendering. > With the help of Jason Rumney I > got 23.0.60.0 to build and run on Windows XP, but the Lao compositions are > still displaying unreadably bizarrely. Unfortunately the more thorough > application of composition in emacs-unicode-2 currently makes matters worse! > Before, one could easily if tediously avoid the composition mechanism. For > example, to make a Lao closed syllable consonant-vowel sequence , in > Emacs 22.1 one can type d, space, delete, a. The best I can find in Emacs > 23.0.60.0 is d, space, a, left, delete. However, as soon as one moves the > cursor the characters compose and are then misdisplayed. That is because of the auto-composition mechanism introduced in emacs-unicode-2. The problem is that the current fixed composition is suitable only for a specific font (usually a fixed-width terminal font). Even on Windows, I think there's a way to use BDF fonts distributed as intlfonts. If you use those fonts on Windows, the rendering should be good. --- Kenichi Handa handa@ni.aist.go.jp