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: fail on osx between 2/4/2009 and 2/5/2009 Date: Mon, 16 Feb 2009 09:53:50 +0900 Message-ID: References: <861vubqc79.fsf@blue.stonehenge.com> <10DD5733-4089-4A60-B090-4CB5E32A0E19@42tools.com> <49917BE9.6020903@gnu.org> <15A24001-137F-469F-8B05-DB31D4E8995D@gmail.com> <86BB7F5A-18D1-4D15-A141-FC721BCC7CB4@gmail.com> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1234745643 20656 80.91.229.12 (16 Feb 2009 00:54:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Feb 2009 00:54:03 +0000 (UTC) Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org To: Adrian Robert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 16 01:55:16 2009 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 1LYrlT-0002MX-RU for ged-emacs-devel@m.gmane.org; Mon, 16 Feb 2009 01:55:16 +0100 Original-Received: from localhost ([127.0.0.1]:48553 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LYrkA-0007Sx-0g for ged-emacs-devel@m.gmane.org; Sun, 15 Feb 2009 19:53:54 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LYrk5-0007Sa-LJ for emacs-devel@gnu.org; Sun, 15 Feb 2009 19:53:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LYrk4-0007SO-0Y for emacs-devel@gnu.org; Sun, 15 Feb 2009 19:53:49 -0500 Original-Received: from [199.232.76.173] (port=53293 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LYrk3-0007SL-T4 for emacs-devel@gnu.org; Sun, 15 Feb 2009 19:53:47 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:62645) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LYrk2-00079V-WA for emacs-devel@gnu.org; Sun, 15 Feb 2009 19:53:47 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id n1G0rcCn029744; Mon, 16 Feb 2009 09:53:38 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id n1G0rcQx018215; Mon, 16 Feb 2009 09:53:38 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id n1G0rcHq005975; Mon, 16 Feb 2009 09:53:38 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.69) (envelope-from ) id 1LYrk6-0004M6-7X; Mon, 16 Feb 2009 09:53:50 +0900 In-reply-to: <86BB7F5A-18D1-4D15-A141-FC721BCC7CB4@gmail.com> (message from Adrian Robert on Sun, 15 Feb 2009 18:04:13 +0200) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 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:109096 Archived-At: In article <86BB7F5A-18D1-4D15-A141-FC721BCC7CB4@gmail.com>, Adrian Robert writes: > On Feb 14, 2009, at 3:03 PM, Kenichi Handa wrote: > > > > :script -- script name symbol. script-representative-chars > > can be used as an additional hint to find a font. > > > > :lang -- symbol of iso639 two-letter language code. > > > > :otf -- see the docstring of query-font > > > > and I'm going to add: > > > > :chars -- the same format as the cdr part of each element of > > script-representative-chars. > OK, thanks, I'll work on responding to them in the NS backend (though > I'm unsure about the OTF stuff). Does this new mechanism of > displaying chars in any script (through passing :script to the > backend when asking for fonts) operate with any fontset (e.g., if the > user does set-frame-font or similar), or is it only when the user is > using the so-called "default" fontset? A font-backend doesn't have to case about fontset. In other words, :script property may appean in a font-spec stored in any fontsets. > As far as prioritization, it was said earlier that :chars should > override anything in script-representative-chars. What about > priority between :lang and :script? From the backend impl's > perspective, does :lang really need to be worried about if :script is > present? In `list' method, all properties in a font-spec must be sutisfied. If both :script and :lang are specified, it must return fonts that satify both property. On the other hand, `match' method can return a font that, a font-backend thinks, most fit with the specs. So, it can put any priority to the properties, and can even ignore some of them. > Will there be times when match() or list() receives a spec > with :lang only (and no :script)? Yes. > Also, is there a plan to update the documentation for match() and list > () in font.h? I'm willing to do this (after I've finished and tested > my new implementation) if no one else has time. I don't know what else should be added to the documentations, but if you think the current ones must be improved, please go ahead. --- Kenichi Handa handa@m17n.org