From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: Ntemacs chooses wrong font. Date: Wed, 11 Jun 2008 15:48:18 +0200 Message-ID: References: <42b562540806060552q622e3dfvb35820ec28dc66d3@mail.gmail.com> <4849AAE4.4080404@gnu.org> <42b562540806061941p2c2d2ebfg734c2d7c4afbbd28@mail.gmail.com> <484F8E81.8050604@gnu.org> <42b562540806110351p699e4ad8l19b5841724eef431@mail.gmail.com> <484FC664.1070403@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1213192140 5280 80.91.229.12 (11 Jun 2008 13:49:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Jun 2008 13:49:00 +0000 (UTC) Cc: emacs-devel@gnu.org, Kevin Yu , Kenichi Handa To: "Jason Rumney" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 11 15:49:43 2008 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 1K6Qhk-0007ru-NF for ged-emacs-devel@m.gmane.org; Wed, 11 Jun 2008 15:49:36 +0200 Original-Received: from localhost ([127.0.0.1]:42006 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6Qgx-0005dR-AN for ged-emacs-devel@m.gmane.org; Wed, 11 Jun 2008 09:48:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6Qgq-0005dM-OW for emacs-devel@gnu.org; Wed, 11 Jun 2008 09:48:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6Qgp-0005d1-8o for emacs-devel@gnu.org; Wed, 11 Jun 2008 09:48:40 -0400 Original-Received: from [199.232.76.173] (port=44850 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6Qgp-0005cd-3d for emacs-devel@gnu.org; Wed, 11 Jun 2008 09:48:39 -0400 Original-Received: from py-out-1112.google.com ([64.233.166.177]:46422) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6Qgo-0003NS-8V for emacs-devel@gnu.org; Wed, 11 Jun 2008 09:48:38 -0400 Original-Received: by py-out-1112.google.com with SMTP id p76so1217841pyb.1 for ; Wed, 11 Jun 2008 06:48:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=lFOpTCx/5YhurJmpztB0ZCMP/JR/zymg50+0EJDDLF0=; b=MM5Y5AJnyPEe4GcgJhIXxt6IlQIfHGa/V7SgC0Lr9ivPMnm2FMFiJ32J3u2QCrF/J1 GoTUgY9JZetS04xSu8s2vUL/XnsdDnuic7Iza8y8o/BFKQBFOEWmgzR0LBzoTJbNMJDr ++T9sfJh1VSISSuY6Bl2E7d3LnUerPsgUEH1M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=scCz71vCYBWOvlEi2BZ5FCUFKrhQEIYRa4deSU1qPKG64NMkADC1ORSy0DvSz+9IjD P/pF3FjQNwi99l77VXX+oiFLny5g/kUGXz2hamfad6D8GpeIRckm5toQTTre7HqGtLMD nUDWEFRZpL+bQaBbqE3UzGAhtcNb51sBxChqc= Original-Received: by 10.114.175.16 with SMTP id x16mr6533789wae.155.1213192098524; Wed, 11 Jun 2008 06:48:18 -0700 (PDT) Original-Received: by 10.114.167.12 with HTTP; Wed, 11 Jun 2008 06:48:18 -0700 (PDT) In-Reply-To: <484FC664.1070403@gnu.org> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: 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:98954 Archived-At: On Wed, Jun 11, 2008 at 14:34, Jason Rumney wrote: > The problem appears to be that the system API used in one of the encode_char > functions on Windows (I don't know whether it is uniscribe or gdi) seems to > return a space glyph for unsupported characters in some fonts, instead of 0 > (which is ".notdef" according to the truetype spec). FWIW, that's what I see: - using gdi (because I've forced Emacs to fail loading usp10.dll or by using Emacs.fontBackend: gdi) => Emacs "finds" U+2200 at glyph #3 of DejaVu Sans Mono. - using uniscribe (by means of Emacs.fontBackend: uniscribe) => Emacs correctly finds U+2200 at #421 of MS Mincho. - leaving it to itself to choose (no Emacs.fontBackend): it "find" the #x3 glyph in DejaVu Sans Mono so it seems gdi-related. > Perhaps C-u C-x = should also report which font backend a font belongs to, > to make tracking these sorts of bugs down easier. BTW, perhaps there should be a (trivial) function to list available backends. Currently the only way I can see is (cdr (assq 'font-backend (frame-parameters))) and that depends on Emacs.fontBackend not being set to limit the list. Juanma