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: Pango-like font fallback (was Re: Russian numero sign) Date: Wed, 08 Mar 2006 10:55:32 +0900 Message-ID: References: <200602191431.36541.pogonyshev@gmx.net> <200603052231.29806.pogonyshev@gmx.net> <200603072239.29811.pogonyshev@gmx.net> 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 1141782976 31236 80.91.229.2 (8 Mar 2006 01:56:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Mar 2006 01:56:16 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 08 02:56:11 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 1FGnuN-00066N-3p for ged-emacs-devel@m.gmane.org; Wed, 08 Mar 2006 02:56:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FGnuM-000409-Bd for ged-emacs-devel@m.gmane.org; Tue, 07 Mar 2006 20:56:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FGnu1-0003ho-PA for emacs-devel@gnu.org; Tue, 07 Mar 2006 20:55:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FGntt-0002vN-LG for emacs-devel@gnu.org; Tue, 07 Mar 2006 20:55:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FGnts-0002v0-U6 for emacs-devel@gnu.org; Tue, 07 Mar 2006 20:55:40 -0500 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FGnwc-0000Ho-0S for emacs-devel@gnu.org; Tue, 07 Mar 2006 20:58:30 -0500 Original-Received: from nfs.m17n.org (nfs.m17n.org [192.47.44.7]) by tsukuba.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id k281tWw2005090; Wed, 8 Mar 2006 10:55:32 +0900 Original-Received: from etlken (etlken.m17n.org [192.47.44.125]) by nfs.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id k281tWkG023756; Wed, 8 Mar 2006 10:55:32 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1FGntk-0000IB-00; Wed, 08 Mar 2006 10:55:32 +0900 Original-To: Paul Pogonyshev In-reply-to: <200603072239.29811.pogonyshev@gmx.net> (message from Paul Pogonyshev on Tue, 7 Mar 2006 22:39:29 +0200) 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:51343 Archived-At: Paul Pogonyshev writes: >> Please note that Pango and the other modern rendering >> engines use TrueType font with a help of freetype/Xft and >> fontconfig libraries. Emacs (and emacs-unicode-2 too) >> currently doesn't use them, but there exists an ongoing >> project for supporting TTF in Emacs. > That is a valid reason why Emacs cannot use Pango (yet), but it > doesn't mean Emacs cannot implement similar substitution heuristic > without Pango and for a different font class. As I understand, you > did that in the `emacs-unicode-2' branch. It is not something simple, > but Emacs is not simple to begin with. I drastically changed the internal structure of fontset in emacs-unicode-2. We can't do such a change for the HEAD (which will be the next release, I hope, soon). >> First of all, do you have any iso10646-1 X core fonts that >> support Cyrillic characters? > No idea, sorry. How do I check? As I wrote above, Emacs does > display Cyrillic characters (newly typed) when `unify-8859-on-decoding' > is off. And already existing characters are displayed no matter if > that mode is active or not. % xlsfonts -fn -*-*-medium-r-normal-*-*-*-*-*-*-*-iso10646-1 gives you a list of iso10646-1 X core fonts usable from Emacs. For instance, if this font is found... -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1 % xfd -fn -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1 shows you the supported glyphs. Please check the block 0x000400. If you see cyrillic glyphs there, that font is what you need. You can do this to use that font. (set-fontset-font "fontset-default" 'mule-unicode-0100-24ff '("FOUNDRY-FAMILY" . "iso10646-1")) Here FOUNDRY-FAMILY is misc-fixed in the above case. If you surely don't have a proper iso10646-1 font, the next method you can try is to customize utf-fragment-on-decoding to t. Even with the default setting of unify-8859-on-decoding/off and unify-8859-on-encoding/on, if utf-fragment-on-decoding is on, when you read an utf-8 cyrillic file, characters and decoded into cyrillic-iso8859-5 charsets, thus you should see glyphs with your iso8859-5 fonts. --- Kenichi Handa handa@m17n.org