From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Adrian Robert Newsgroups: gmane.emacs.devel Subject: Re: fail on osx between 2/4/2009 and 2/5/2009 Date: Tue, 17 Feb 2009 12:15:42 +0200 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 Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1234866564 5588 80.91.229.12 (17 Feb 2009 10:29:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 Feb 2009 10:29:24 +0000 (UTC) Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 17 11:30:39 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 1LZNCp-0007rS-7d for ged-emacs-devel@m.gmane.org; Tue, 17 Feb 2009 11:29:37 +0100 Original-Received: from localhost ([127.0.0.1]:58906 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZNBU-0006Qc-Ri for ged-emacs-devel@m.gmane.org; Tue, 17 Feb 2009 05:28:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LZMz1-0003JS-Ga for emacs-devel@gnu.org; Tue, 17 Feb 2009 05:15:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LZMyy-0003J5-V2 for emacs-devel@gnu.org; Tue, 17 Feb 2009 05:15:18 -0500 Original-Received: from [199.232.76.173] (port=55492 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZMyy-0003J2-Gf for emacs-devel@gnu.org; Tue, 17 Feb 2009 05:15:16 -0500 Original-Received: from fk-out-0910.google.com ([209.85.128.185]:4408) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LZMyy-00061T-1c for emacs-devel@gnu.org; Tue, 17 Feb 2009 05:15:16 -0500 Original-Received: by fk-out-0910.google.com with SMTP id 19so1426654fkr.10 for ; Tue, 17 Feb 2009 02:15:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=v5qUA7g3wXiDbpWy4VXn1nKouPkKDcu4FMRGW5D34CQ=; b=dqj7Svi9T7YmyL8a+bl8N3f/OEIuytnCWW6SoXC0eU73h5wKC2kc0zDFcX26yajcK6 FCedL9W7wa29+hyqHBKePJpJWsAIn3zNfo0nwAIbkgQLO1asjHp+iC1BYT4NbgOihodL 5nI7rLSarKuI9ij1KVNqzr0qNeWtXApvYAsV4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=GAKygBWAbr53Xd/Ackb/uhs0ucHKcHp3mEvyUseiVq5fAGuqMI7oisYvj+im+phO3m FJ8Ptpc6lEK+QSPq+U/bzsixJLFRnj8u+jQMg4oaM9DAqNweNu1IhaJjQS+K9y2Gunx+ isnytvLFMOdBpT6f6jhZGnov5+yH+Gu6zLhVU= Original-Received: by 10.103.224.17 with SMTP id b17mr359130mur.61.1234865713559; Tue, 17 Feb 2009 02:15:13 -0800 (PST) Original-Received: from ?10.20.48.125? (gw1.panoulu.net [212.50.147.101]) by mx.google.com with ESMTPS id t10sm99505muh.28.2009.02.17.02.15.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 17 Feb 2009 02:15:12 -0800 (PST) In-Reply-To: X-Mailer: Apple Mail (2.753.1) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:109121 Archived-At: >> 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. I meant my question more from a user perspective. If they call 'set- frame-font or similar, do ALL of the fonts, on, e.g., the HELLO screen, get switched to be the most similar to the user's selection with the appropriate charset, or does it just change the ASCII font? Experimenting with the non-freetype X build here, just set-frame-font doesn't seem to do it, but selecting something from the shift-left- mouse menu does (but I can't fully trace out what is getting called in this case). >> 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. The full list of properties that can appear bundled under the FONT_EXTRA property that are important for drivers to take into account in match() and list() should be specified somewhere in font.h. In font.c there is font_property_table, which lists everything that is a "first class" property in font.h (explicitly listed in font_property_index), plus the following: 'lang', 'script', and 'otf'. While the font-spec function mentions 'script' and 'name', but not 'lang' or 'otf'. I'm not sure about the criterion for putting something under "EXTRA" or listing it in one place or another in font.c, but if the font driver should respond to it, especially for something as important as core emacs font selection, it should be mentioned in font.h.