From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Dyballa Newsgroups: gmane.emacs.help Subject: Re: emacs could not show this symbol. Date: Wed, 27 Feb 2008 13:09:33 +0100 Message-ID: <872989E1-E02D-4265-B629-01CD1B310B74@Web.DE> References: <86ejb08qsv.fsf@freebsd.hasee.cpu> <86y798s6q8.fsf@freebsd.hasee.cpu> <86mypo9e3w.fsf@freebsd.hasee.cpu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1204114211 13025 80.91.229.12 (27 Feb 2008 12:10:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 27 Feb 2008 12:10:11 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: anhnmncb Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Feb 27 13:10:36 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JUL7F-0004Im-1I for geh-help-gnu-emacs@m.gmane.org; Wed, 27 Feb 2008 13:10:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUL6j-0000Sp-3I for geh-help-gnu-emacs@m.gmane.org; Wed, 27 Feb 2008 07:09:57 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUL6R-0000PT-NS for help-gnu-emacs@gnu.org; Wed, 27 Feb 2008 07:09:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUL6P-0000MH-UL for help-gnu-emacs@gnu.org; Wed, 27 Feb 2008 07:09:39 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUL6P-0000M9-RX for help-gnu-emacs@gnu.org; Wed, 27 Feb 2008 07:09:37 -0500 Original-Received: from fmmailgate02.web.de ([217.72.192.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JUL6P-0006WQ-5W for help-gnu-emacs@gnu.org; Wed, 27 Feb 2008 07:09:37 -0500 Original-Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate02.web.de (Postfix) with ESMTP id F0627D25EC51; Wed, 27 Feb 2008 13:09:35 +0100 (CET) Original-Received: from [195.4.206.227] (helo=[192.168.1.2]) by smtp06.web.de with asmtp (TLSv1:AES128-SHA:128) (WEB.DE 4.109 #226) id 1JUL6N-0000aL-00; Wed, 27 Feb 2008 13:09:35 +0100 In-Reply-To: <86mypo9e3w.fsf@freebsd.hasee.cpu> X-Mailer: Apple Mail (2.753) X-Sender: Peter_Dyballa@web.de X-Provags-ID: V01U2FsdGVkX1/gWPL/1Wx1GwE6W+5t5H1b+ZVdDbXDswSz0SGU PobCJ9PD5D+UGOQcEAS42cCclr5gdpTksJN1NDMVB1YMD3Rw08 oqBQTngluc5mAaGt0kBQ== X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:51911 Archived-At: Am 26.02.2008 um 12:00 schrieb anhnmncb: > I don't seem it's font's problem. I think that urxvt's font > selection mechanism is great, if a font doesn't contain a symbol in =20= > that > encoding, it will find another font to display it, don't know whether > emacs could implement this technique? It would not be that easy. A terminal emulation has an easy job: display things in one encoding. =20= GNU Emacs supports some dozens. Less than a handful are sensible, =20 IMO, i.e. Unicode based. Some encodings are 8 bit, left from the =20 child days of some operating systems, other are 16 bit or more, most =20 of them for some restricted national use. Ideally GNU Emacs would need to construct font sets for all these =20 encodings, at least for those in use. It also supports scripts =20 (writing systems) and their languages (language environments). This =20 *can* mean that for different font sizes and font variants (regular, =20 bold, italic, bold italic) 100 MB of fonts would be loaded into =20 memory, at least for 16 bit encodings. The size needed might be =20 reduced when 8 bit encodings could be derived from 16 bit encodings =20 (for example ISO 8859-11 and TIS620 are the same and both could map =20 into Unicode). The idea of font backends eases this situation by delegating font =20 handling to the operating system (what Mac OS X or MS Losedos or ... =20 or X11 are providing in some way, some better, some worse). To make =20 this work the OS has to know what its fonts support/deliver. This =20 information usually is derived from the fonts. Some provide enough =20 information, others tend to hide it. The it becomes difficult. With fc-list you can check what your system provides. The language =20 name used is based on RFC 3066 which in turn references ISO 639. A =20 font with your Thai character could be searched for with: fc-list :lang=3Dth Much more options are possible. To find all monospaced fonts with =20 Thai support: fc-list : file lang spacing | grep spac | egrep 'lang=3D.*th' This is because fc-list tends to report either too much or not enough =20= =96 or I need more practise with fc-list! -- Greetings Pete Got Mole problems? Call Avogadro 6.02 x 10^23