[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs could not show this symbol.

From: Peter Dyballa
Subject: Re: emacs could not show this symbol.
Date: Fri, 29 Feb 2008 12:15:52 +0100

Am 29.02.2008 um 01:25 schrieb anhnmncb:

For mule-unicode-0100-24ff
encoding I would use a font that has more to offer than Monotype
Courier, Lucida Sans Typewriter or DejaVu Sans Mono or Free Mono.

My sentence can be misunderstood: I was recommending to use Lucida Sans Typewriter or DejaVu Sans Mono or Free Mono instead of Monotype Courier.

Vista courier has a symbol even dejavu doesn't contain :``ˏ'' , could
you see it? ;p

The character you are quoting is MODIFIER LETTER LOW ACUTE ACCENT, U +02CF. It's not in DejaVu, but it's rather insignificant.

I think this setting is meant that when the fontset-dejavu donesn't have a suitable font to show the character, then emacs will use fontset- default
instead, don't know if I correct, but I find that this setting works
well for me.

No. Initially GNU Emacs has two fontsets defined. None of them is meant as the other's fall-back. It's more like two trains starting from the same station: one leaves in this direction giving you the view of this landscape, the other leaves in that direction giving you the view of that landscape. No fall-back possible (but in GNU Emacs you can switch from this to that fontset).

I made experiments with GNU Emacs, launching it with -q and making it load some ELisp code that uses data defined in X resources:

Emacs.Fontset-0: -b&h-lucidatypewriter-medium-r-*-*-10-*-*-*-*-*- fontset-mine,\
chinese-gb2312: -misc-han nom a-medium-r-*-*-0-*-*-*-p-*- gb2312.1980-0,\
                gb18030: -misc-han nom 
thai-tis620: -monotype-arial unicode ms-medium-r-*-*-0-*-*-*-p-*- tis620-2,\ arabic-iso8859-6: -b&h-lucida sans typewriter-medium-r-*-*-0- *-*-*-m-*-iso8859-6.16,\ japanese-jisx0208: -apple-osaka-medium-r-*-*-0-*-*-*-p-*- jisx0208.1983-0,\ katakana-jisx0201: -apple-osaka-medium-r-*-*-0-*-*-*-p-*- jisx0201.1976-0,\ ethiopic-unicode: -misc-ethiopia jiret-medium-r-*-*-0-*-*-*-p- *-iso10646-1,\ mule-unicode-0100-24ff: -b&h-lucidatypewriter-medium-r-*-*-10-*-*-*- m-*-iso10646-1,\ mule-unicode-e000-ffff: -b&h-lucidatypewriter-medium-r-*-*-10-*-*-*- m-*-iso10646-1,\ mule-unicode-2500-33ff: -b&h-lucidatypewriter-medium-r-*-*-10-*-*-*- m-*-iso10646-1

Emacs.Font:             fontset-mine

which allows me to use in the ELisp file:

; (set-fontset-font "fontset-mine" 'bengali-akruti '("Arial Unicode MS" . "unicode-bmp"))
        (set-fontset-font "fontset-mine" (cons (decode-char 'ucs #x10a0)
(decode-char 'ucs #x10ff)) '("dejavu sans mono" . "iso10646-1")) ; Georgian
        (set-fontset-font "fontset-mine" (cons (decode-char 'ucs #x1200)
(decode-char 'ucs #x137f)) '("ethiopia jiret" . "iso10646-1")) ; Ethiopic
        (set-fontset-font "fontset-mine" (cons (decode-char 'ucs #x1380)
(decode-char 'ucs #x139f)) '("code2000" . "iso10646-1")) ; Ethiopic Supplement
        (set-fontset-font "fontset-mine" (cons (decode-char 'ucs #x0980)
(decode-char 'ucs #x09ff)) '("freeserif" . "iso10646-1")) ; Bengali

I.e. there is no error in using the "fontset-mine" symbol, but GNU Emacs does not use that fontset, it uses a bad startup fontset with many empty boxes. When launching GNU Emacs with an additional -- disable-font-backend I can see that my fontset is used (M-x describe- fontset RET RET) and that the HELLO buffer has much less boxes ...

Maybe the fontset for use with any font backend has to be built from fontconfig specification ...

Because you are using monospaced and proportionally spaced fonts in
your fontsets:

I changed dejavu sans mono to dejavu sans, and m to p, did not work.

Actually the width of glyphs taken from more than one monospaced font will most probably vary. So a fontset comprised of more than one (monospaced) font will show variations when it happens that glyphs from more than one font are used to display that text. When you use proportionally spaced fonts, *every* glyph has its own personal width. These fonts are good for menus or pop-up forms.



What is this talk of 'release?' Klingons do not make software 'releases.' Our software 'escapes,' leaving a bloody trail of designers and quality assurance people in its wake.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]