From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: anhnmncb <anhnmncb@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs could not show this symbol.
Date: Wed, 27 Feb 2008 13:09:33 +0100 [thread overview]
Message-ID: <872989E1-E02D-4265-B629-01CD1B310B74@Web.DE> (raw)
In-Reply-To: <86mypo9e3w.fsf@freebsd.hasee.cpu>
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
> 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.
GNU Emacs supports some dozens. Less than a handful are sensible,
IMO, i.e. Unicode based. Some encodings are 8 bit, left from the
child days of some operating systems, other are 16 bit or more, most
of them for some restricted national use.
Ideally GNU Emacs would need to construct font sets for all these
encodings, at least for those in use. It also supports scripts
(writing systems) and their languages (language environments). This
*can* mean that for different font sizes and font variants (regular,
bold, italic, bold italic) 100 MB of fonts would be loaded into
memory, at least for 16 bit encodings. The size needed might be
reduced when 8 bit encodings could be derived from 16 bit encodings
(for example ISO 8859-11 and TIS620 are the same and both could map
into Unicode).
The idea of font backends eases this situation by delegating font
handling to the operating system (what Mac OS X or MS Losedos or ...
or X11 are providing in some way, some better, some worse). To make
this work the OS has to know what its fonts support/deliver. This
information usually is derived from the fonts. Some provide enough
information, others tend to hide it. The it becomes difficult.
With fc-list you can check what your system provides. The language
name used is based on RFC 3066 which in turn references ISO 639. A
font with your Thai character could be searched for with:
fc-list :lang=th
Much more options are possible. To find all monospaced fonts with
Thai support:
fc-list : file lang spacing | grep spac | egrep 'lang=.*th'
This is because fc-list tends to report either too much or not enough
– or I need more practise with fc-list!
--
Greetings
Pete
Got Mole problems?
Call Avogadro 6.02 x 10^23
next prev parent reply other threads:[~2008-02-27 12:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 1:11 emacs could not show this symbol anhnmncb
2008-02-26 4:05 ` anhnmncb
2008-02-26 6:33 ` David Hansen
[not found] ` <mailman.7947.1204007911.18990.help-gnu-emacs@gnu.org>
2008-02-26 11:00 ` anhnmncb
2008-02-27 12:09 ` Peter Dyballa [this message]
[not found] ` <mailman.7995.1204114181.18990.help-gnu-emacs@gnu.org>
2008-02-28 0:10 ` anhnmncb
2008-02-28 0:56 ` anhnmncb
2008-02-28 10:12 ` Peter Dyballa
2008-02-28 9:49 ` Peter Dyballa
[not found] ` <mailman.8026.1204192187.18990.help-gnu-emacs@gnu.org>
2008-02-28 12:47 ` anhnmncb
2008-02-28 15:01 ` Peter Dyballa
[not found] ` <mailman.8038.1204210929.18990.help-gnu-emacs@gnu.org>
2008-02-29 0:25 ` anhnmncb
2008-02-29 11:15 ` Peter Dyballa
2008-02-26 11:35 ` Peter Dyballa
2008-02-26 11:46 ` anhnmncb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=872989E1-E02D-4265-B629-01CD1B310B74@Web.DE \
--to=peter_dyballa@web.de \
--cc=anhnmncb@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).