Euro Sign and Bitstream Vera

Euro Sign and Bitstream Vera

[M G Berberich]

Halle,

I have the problem, that my emacs (23.0.0.1) with
Bitstream-Vera-Sans-Mono-Font shows the Euro-sign ‘€’ as Currency-sign
‘¤’… sometimes. If I start the emacs with the UTF-8-demo-file from
Markus Kuhn the ‘€’ is displayed O.K.

I have set fontsets (shortend by ‘…’) as this:

(create-fontset-from-fontset-spec
 "-bitstream-bitstream vera sans mono-…-*-fontset-vera11,
  latin:-bitstream-bitstream vera sans mono-…-*-iso10646-1,
  mule-unicode-0100-24ff:-bitstream-bitstream vera sans mono-…-iso10646-1,
  mule-unicode-2500-33ff:-bitstream-bitstream vera sans mono-…-iso10646-1,
  mule-unicode-e000-ffff:-bitstream-bitstream vera sans mono-…-iso10646-1,
  symbol:-bitstream-bitstream vera sans mono-…-iso10646-1,
  symbol:-unknown-freemono-…-iso10646-1,
  greek:-unknown-freemono-…-iso10646-1,
  cyrillic:-monotype-andale mono-…-iso10646-1")

BTW: I have defined symbol: two times, does this make sense?

I added the output of ‘C-u C-x =’ below, the “working”-case differns
from the “non-working”-case in the glyph tht is used to display the
(same) char (#xBD / #x102) and in the property ‘fontified’.

Anybody?

	MfG
	bmg

C-u C-x = give this if the Euro-sign is not working
---------------------------------------------------------------------------
        character: ¤ (8364, #o20254, #x20ac)
preferred charset: iso-8859-15 (ISO/IEC 8859/15)
       code point: 0xA4
           syntax: _ 	which means: symbol
         category: c:Chinese h:Korean j:Japanese
      buffer code: #xE2 #x82 #xAC
        file code: #xE2 #x82 #xAC (encoded by coding system utf-8)
          display: by this font (glyph code)
     bitstream vera sans mono:pixelsize=11:foundry=bitstream:…
weight=medium:slant=r:width=normal (#xBD)

Character code properties: customize what to show
  name: EURO SIGN
  general-category: Sc (Symbol, Currency)
  canonical-combining-class: 0 (Spacing, split, enclosing, reordrant,…
and Tibetan subjoined)
  bidi-class: ET (European Number Terminator)
  mirrored: N

There are text properties here:
  auto-composed        t
  fontified            t
---------------------------------------------------------------------------
and this if the Euro-sign is working
---------------------------------------------------------------------------
        character: € (8364, #o20254, #x20ac)
preferred charset: iso-8859-15 (ISO/IEC 8859/15)
       code point: 0xA4
           syntax: _ 	which means: symbol
         category: c:Chinese h:Korean j:Japanese
      buffer code: #xE2 #x82 #xAC
        file code: #xE2 #x82 #xAC (encoded by coding system utf-8-unix)
          display: by this font (glyph code)
     bitstream vera sans mono:pixelsize=11:foundry=bitstream:…
weight=medium:slant=r:width=normal (#x102)

Character code properties: customize what to show
  name: EURO SIGN
  general-category: Sc (Symbol, Currency)
  canonical-combining-class: 0 (Spacing, split, enclosing, reordrant,…
and Tibetan subjoined)
  bidi-class: ET (European Number Terminator)
  mirrored: N

There are text properties here:
  auto-composed        t
---------------------------------------------------------------------------

-- 
„Des is völlig wurscht, was heut beschlos- | M G Berberich
 sen wird: I bin sowieso dagegn!“          | berberic@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg)  | www.fmi.uni-passau.de/~berberic

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 27.01.2007 um 22:13 schrieb M G Berberich:

> I have the problem, that my emacs (23.0.0.1) with
> Bitstream-Vera-Sans-Mono-Font shows the Euro-sign ‘€’ as  
> Currency-sign
> ‘¤’… sometimes.

You need to understand that the € is shown in ISO 8859-15 (ISO  
Latin-9), ISO 8859-16 (ISO Latin-10), and UTF-8 encodings (maybe  
there are also some more obscure). In the first two cases it has hex A 
$, dec 164, oct 244. In UTF-8 it is at U+20AC.

Look into the mode-line! In the right encodings it will start with  
-0:, -r:, or -u:. You can force the right encoding with a first line  
like

	;;; -*- mode: Text; coding: iso-8859-16; -*-

or local variables at the file's end like

	%%% Local Variables:
	%%% mode: latex
	%%% coding: utf-8-unix
	%%% TeX-command-default: "XɘLaTeX"
	%%% TeX-master: t
	%%% End:

Would you like to have some ISO 8859 test files?

--
Mit friedvollen Grüßen

   Pete

Der größte Aberglaube der Gegenwart ist der Glaube an die Vorfahrt.  
(Jacques Tati)

Re: Euro Sign and Bitstream Vera

[M G Berberich]

On Sun, 28 Jan 2007, Peter Dyballa <Peter_Dyballa@Web.DE> wrote:
>
> Am 27.01.2007 um 22:13 schrieb M G Berberich:
>
>> I have the problem, that my emacs (23.0.0.1) with
>> Bitstream-Vera-Sans-Mono-Font shows the Euro-sign ‘€’ as  
>> Currency-sign
>> ‘¤’… sometimes.
>
> You need to understand that the € is shown in ISO 8859-15 (ISO  
> Latin-9), ISO 8859-16 (ISO Latin-10), and UTF-8 encodings (maybe  
> there are also some more obscure). In the first two cases it has hex A 
> $, dec 164, oct 244. In UTF-8 it is at U+20AC.
>
> Look into the mode-line! In the right encodings it will start with  
> -0:, -r:, or -u:. 

It starts with ‘-U’, whitch means: 
utf-8 (UTF-8: Emacs internal multibyte form)

I have ‘(prefer-coding-system 'utf-8)’ in my .emacs -file. Bevor
switching to UTF-8, I had iso-8859-15 coding and no problems with the
Euro-sign ‒ but no german quotation-marks.

	  MfG
	  bmg

-- 
„Des is völlig wurscht, was heut beschlos- | M G Berberich
 sen wird: I bin sowieso dagegn!“          | berberic@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg)  | www.fmi.uni-passau.de/~berberic

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 28.01.2007 um 10:04 schrieb M G Berberich:

>> Look into the mode-line! In the right encodings it will start with
>> -0:, -r:, or -u:.
>
> It starts with ‘-U’, whitch means:
> utf-8 (UTF-8: Emacs internal multibyte form)

This is, IMO, a very strange mark and nowhere documented ...

>
> I have ‘(prefer-coding-system 'utf-8)’ in my .emacs -file. Bevor
> switching to UTF-8, I had iso-8859-15 coding and no problems with the
> Euro-sign ‒ but no german quotation-marks.

Right! It has only French quotation marks. The German ones are at U 
+20xx.

--
Mit friedvollen Grüßen

   Pete     === -Q
              ==<__/% >>
_____________(_)____@_____________________________

Re: Euro Sign and Bitstream Vera

[Ralf Angeli]

* Peter Dyballa (2007-01-28) writes:

> Am 28.01.2007 um 10:04 schrieb M G Berberich:
>
>>> Look into the mode-line! In the right encodings it will start with
>>> -0:, -r:, or -u:.
>>
>> It starts with ‘-U’, whitch means:
>> utf-8 (UTF-8: Emacs internal multibyte form)
>
> This is, IMO, a very strange mark and nowhere documented ...

Of course it is documented:

,----[ (info "(emacs)Coding Systems") ]
|    To display a list of all the supported coding systems, type `M-x
| list-coding-systems'.  The list gives information about each coding
| system, including the letter that stands for it in the mode line (*note
| Mode Line::).
`----

-- 
Ralf

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 28.01.2007 um 12:36 schrieb Ralf Angeli:

>>> It starts with ‘-U’, whitch means:
>>> utf-8 (UTF-8: Emacs internal multibyte form)
>>
>> This is, IMO, a very strange mark and nowhere documented ...
>
> Of course it is documented:

I did not mean it that way (mule-diag explains all markers), I was  
trying to express that I was not seeing the capital U – because it's  
only used in Unicode Emacs 23.0.0 or in Emacs.app, which is based on  
its code.

--
Mit friedvollen Grüßen

   Pete

"There's no place like 127.0.0.1"
                      origin unknown

Re: Euro Sign and Bitstream Vera

[Ralf Angeli]

* Peter Dyballa (2007-01-28) writes:

> Am 28.01.2007 um 12:36 schrieb Ralf Angeli:
>
>>>> It starts with ‘-U’, whitch means:
>>>> utf-8 (UTF-8: Emacs internal multibyte form)
>>>
>>> This is, IMO, a very strange mark and nowhere documented ...
>>
>> Of course it is documented:
>
> I did not mean it that way (mule-diag explains all markers), I was  
> trying to express that I was not seeing the capital U – because it's  
> only used in Unicode Emacs 23.0.0 or in Emacs.app, which is based on  
> its code.

Of course it is used in Emacs trunk as well:

,----[ M-x list-coding-systems RET ]
| [...]
| U -- koi8-u
|   KOI8-U 8-bit encoding for Cyrillic (MIME: KOI8-U)
| [...]
`----

-- 
Ralf

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 27.01.2007 um 22:13 schrieb M G Berberich:

> I have set fontsets (shortend by ‘…’) as this:
>
> (create-fontset-from-fontset-spec
>  "-bitstream-bitstream vera sans mono-…-*-fontset-vera11,
>   latin:-bitstream-bitstream vera sans mono-…-*-iso10646-1,
>  [...]
>   symbol:-bitstream-bitstream vera sans mono-…-iso10646-1,
>   symbol:-unknown-freemono-…-iso10646-1,
>   greek:-unknown-freemono-…-iso10646-1,
>   cyrillic:-monotype-andale mono-…-iso10646-1")
>
> BTW: I have defined symbol: two times, does this make sense?

No, this is non-sense. Which is the right definition? And: what is  
"symbol?" I mean, where in Unicode do you find "symbol?" (at 100.000  
spots maybe)

>
> I added the output of ‘C-u C-x =’ below, the “working”-case differns
> from the “non-working”-case in the glyph tht is used to display the
> (same) char (#xBD / #x102) and in the property ‘fontified’.
>

IMO it cannot work to take glyphs from postions U+00BD or U+0102 from  
Bitstream Vera to print the €. There is probably no font putting € at  
these positions. The problem might come from the fontsets you use.  
Did you notice when this or that glyph is used, is there some  
correlation with the encoding used in the buffer?
This is a new feature in Unicode Emacs 23.0.0 – and maybe it's buggy.  
So you should consider to create a bug report. Then you'll have  
contact with those who make the software!

Where do the fonts come from? Do they come from fontconfig (fc-cache/ 
fc-list) or is standard X11 serving them? Do the Emacs 23.0.0  
fontsets allow ranges like in:

     (create-fontset-from-fontset-spec "-adobe-courier-medium-r-*-*-9- 
*-*-*-*-*-fontset-09pt_adobe_courier" t 'noerror)
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-1  '("adobe-courier" . "iso8859-1"))
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-2  '("adobe-courier" . "iso8859-2"))
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-3  '("adobe-courier" . "iso8859-3"))
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-4  '("adobe-courier" . "iso8859-4"))
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-9  '("adobe-courier" . "iso8859-9"))
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-14 '("adobe-courier" . "iso8859-14"))
	(set-fontset-font "fontset-09pt_adobe_courier"       'latin- 
iso8859-15 '("adobe-courier" . "iso8859-15"))
	(set-fontset-font "fontset-09pt_adobe_courier" 'mule- 
unicode-0100-24ff '("adobe-courier" . "iso10646-1"))
	(set-fontset-font "fontset-09pt_adobe_courier" 'mule- 
unicode-2500-33ff '("adobe-courier" . "iso10646-1"))
	(set-fontset-font "fontset-09pt_adobe_courier" 'mule-unicode-e000- 
ffff '("adobe-courier" . "iso10646-1"))
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0370) (decode-char 'ucs #x03cf)) '("courier new" .  
"iso10646-1"))	; Greek
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x03d0) (decode-char 'ucs #x03ff)) '("lucida sans typewriter" .  
"iso10646-1"))	; Coptic
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0400) (decode-char 'ucs #x04ff)) '("lucida sans typewriter" .  
"iso10646-1"))	; Cyrillic
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0500) (decode-char 'ucs #x052f)) '("lucida sans typewriter" .  
"iso10646-1"))	; Cyrillic Suppl
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0530) (decode-char 'ucs #x058f)) '("aramian unicode" .  
"iso10646-1"))	; Armenian (sylfaen
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0590) (decode-char 'ucs #x05ff)) '("courier new" .  
"iso10646-1"))	; Hebrew
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0600) (decode-char 'ucs #x06ff)) '("lucida sans typewriter" .  
"iso10646-1"))	; Arabic
	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
'ucs #x0700) (decode-char 'ucs #x074f)) '("courier new" .  
"iso10646-1"))	; Syriac

I never found a door to the 23-er fontsets ...


I am using plain fonts and Emacs substitutes the default font (Lucida  
Sans Typewriter from Java) with other fonts when the standard font  
does not contain the glyph needed. It's not perfect, but I can live  
with that ...

--
Mit friedvollen Grüßen

   Pete

There's no place like ~
                           (UNIX Guru)

Re: Euro Sign and Bitstream Vera

[jasonal]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3824 bytes --]

Hi, I find it's weird when i type AltGr+E with German keyboard in emacs23 
under Win32, the output sign is #x80, and it is displayed as \200.
Under Linux, it is #x20AC as expected.

Any ideas?

best regards,

Qichen

"M G Berberich" <berberic@forwiss.uni-passau.de> wrote in message 
news:mtrs84-2dk.ln1@avaloon.forwiss.uni-passau.de...
> Halle,
>
> I have the problem, that my emacs (23.0.0.1) with
> Bitstream-Vera-Sans-Mono-Font shows the Euro-sign ¡®€¡¯ as Currency-sign
> ¡®¡è¡¯¡­ sometimes. If I start the emacs with the UTF-8-demo-file from
> Markus Kuhn the ¡®€¡¯ is displayed O.K.
>
> I have set fontsets (shortend by ¡®¡­¡¯) as this:
>
> (create-fontset-from-fontset-spec
> "-bitstream-bitstream vera sans mono-¡­-*-fontset-vera11,
>  latin:-bitstream-bitstream vera sans mono-¡­-*-iso10646-1,
>  mule-unicode-0100-24ff:-bitstream-bitstream vera sans mono-¡­-iso10646-1,
>  mule-unicode-2500-33ff:-bitstream-bitstream vera sans mono-¡­-iso10646-1,
>  mule-unicode-e000-ffff:-bitstream-bitstream vera sans mono-¡­-iso10646-1,
>  symbol:-bitstream-bitstream vera sans mono-¡­-iso10646-1,
>  symbol:-unknown-freemono-¡­-iso10646-1,
>  greek:-unknown-freemono-¡­-iso10646-1,
>  cyrillic:-monotype-andale mono-¡­-iso10646-1")
>
> BTW: I have defined symbol: two times, does this make sense?
>
> I added the output of ¡®C-u C-x =¡¯ below, the ¡°working¡±-case differns
> from the ¡°non-working¡±-case in the glyph tht is used to display the
> (same) char (#xBD / #x102) and in the property ¡®fontified¡¯.
>
> Anybody?
>
> MfG
> bmg
>
> C-u C-x = give this if the Euro-sign is not working
> ---------------------------------------------------------------------------
>        character: ¡è (8364, #o20254, #x20ac)
> preferred charset: iso-8859-15 (ISO/IEC 8859/15)
>       code point: 0xA4
>           syntax: _ which means: symbol
>         category: c:Chinese h:Korean j:Japanese
>      buffer code: #xE2 #x82 #xAC
>        file code: #xE2 #x82 #xAC (encoded by coding system utf-8)
>          display: by this font (glyph code)
>     bitstream vera sans mono:pixelsize=11:foundry=bitstream:¡­
> weight=medium:slant=r:width=normal (#xBD)
>
> Character code properties: customize what to show
>  name: EURO SIGN
>  general-category: Sc (Symbol, Currency)
>  canonical-combining-class: 0 (Spacing, split, enclosing, reordrant,¡­
> and Tibetan subjoined)
>  bidi-class: ET (European Number Terminator)
>  mirrored: N
>
> There are text properties here:
>  auto-composed        t
>  fontified            t
> ---------------------------------------------------------------------------
> and this if the Euro-sign is working
> ---------------------------------------------------------------------------
>        character: € (8364, #o20254, #x20ac)
> preferred charset: iso-8859-15 (ISO/IEC 8859/15)
>       code point: 0xA4
>           syntax: _ which means: symbol
>         category: c:Chinese h:Korean j:Japanese
>      buffer code: #xE2 #x82 #xAC
>        file code: #xE2 #x82 #xAC (encoded by coding system utf-8-unix)
>          display: by this font (glyph code)
>     bitstream vera sans mono:pixelsize=11:foundry=bitstream:¡­
> weight=medium:slant=r:width=normal (#x102)
>
> Character code properties: customize what to show
>  name: EURO SIGN
>  general-category: Sc (Symbol, Currency)
>  canonical-combining-class: 0 (Spacing, split, enclosing, reordrant,¡­
> and Tibetan subjoined)
>  bidi-class: ET (European Number Terminator)
>  mirrored: N
>
> There are text properties here:
>  auto-composed        t
> ---------------------------------------------------------------------------
>
> -- 
> ?Des is v?llig wurscht, was heut beschlos- | M G Berberich
> sen wird: I bin sowieso dagegn!¡°          | berberic@fmi.uni-passau.de
> (SPD-Stadtrat Kurt Schindler; Regensburg)  | 
> www.fmi.uni-passau.de/~berberic
> 

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 29.01.2007 um 16:45 schrieb jasonal:

> Hi, I find it's weird when i type AltGr+E with German keyboard in  
> emacs23
> under Win32, the output sign is #x80, and it is displayed as \200.

I'd recommend to write a bug report!

\200 signals that you have chosen wrong encodings – on the input  
side! The range of Unicode points from U+0080-U+009F contains 8 bit  
control characters. They are analogous to the 7 bit control  
characters U+0000-U+001F. When this character is inserted, then GNU  
Emacs could not correctly handle the keyboard event.

--
Greetings

   Pete                           <]
              o        __o         |__    o       HPV, the real
     ___o    /I       -\<,         |o \  -\),-%     high speed!
___/\ /\___./ \___...O/ O____.....`-O-'-()--o_________________

Re: Euro Sign and Bitstream Vera

[jasonal]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

OK!
I've reported this and some related issues.

MfG
Qichen

"Peter Dyballa" <Peter_Dyballa@Web.DE> wrote in message 
news:mailman.3761.1170113954.2155.help-gnu-emacs@gnu.org...

Am 29.01.2007 um 16:45 schrieb jasonal:

> Hi, I find it's weird when i type AltGr+E with German keyboard in  emacs23
> under Win32, the output sign is #x80, and it is displayed as \200.

I'd recommend to write a bug report!

\200 signals that you have chosen wrong encodings – on the input
side! The range of Unicode points from U+0080-U+009F contains 8 bit
control characters. They are analogous to the 7 bit control
characters U+0000-U+001F. When this character is inserted, then GNU
Emacs could not correctly handle the keyboard event.

--
Greetings

   Pete                           <]
              o        __o         |__    o       HPV, the real
     ___o    /I       -\<,         |o \  -\),-%     high speed!
___/\ /\___./ \___...O/ O____.....`-O-'-()--o_________________

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 27.01.2007 um 22:13 schrieb M G Berberich:

> C-u C-x = give this if the Euro-sign is not working
> ---------------------------------------------------------------------- 
> -----
>         character: ¤ (8364, #o20254, #x20ac)
> preferred charset: iso-8859-15 (ISO/IEC 8859/15)
> [...]
>      bitstream vera sans mono:pixelsize=11:foundry=bitstream:…
> weight=medium:slant=r:width=normal (#xBD)

I can confirm: when I use GNU Emacs 23.0.0 with enabled font-backend  
and I launch it as 'emacs --enable-font-backend' and I pass as font a  
fontconfig font name at launch time, then I still get and see €, but  
C-u C-x = returns a weird and obviously wrong character position in  
the font – which is reported in the regular XLFD syntax.

(The fontsets used in GNU Emacs 22 and 21 mostly lead to crashes.)

There is a bug to report!

--
Mit friedvollen Grüßen

   Pete

Time is an illusion. Lunchtime, doubly so.

Re: Euro Sign and Bitstream Vera

[James Cloos]

>>>>> "Peter" == Peter Dyballa <Peter_Dyballa@Web.DE> writes:

Peter> I can confirm: when I use GNU Emacs 23.0.0 with enabled font-backend
Peter> and I launch it as 'emacs --enable-font-backend' and I pass as font a
Peter> fontconfig font name at launch time, then I still get and see €, but
Peter> C-u C-x = returns a weird and obviously wrong character position in
Peter> the font – which is reported in the regular XLFD syntax.

When I tried C-u C-x = on the € in your email, I got this:

,----
|         character: € (8364, #o20254, #x20ac)
| preferred charset: unicode (Unicode (ISO10646))
|        code point: 0x20AC
|            syntax: _ 	which means: symbol
|          category: c:Chinese h:Korean j:Japanese
|       buffer code: #xE2 #x82 #xAC
|         file code: #xE2 #x82 #xAC (encoded by coding system raw-text-unix)
|           display: by this font (glyph code)
|      dejavu sans mono:pixelsize=14:foundry=unknown:weight=medium:slant=r:width=normal (#x66A)
|      Unicode data:  
|              Name: EURO SIGN
|          Category: Symbol, Currency
|   Combining class: Sc
|     Bidi category: Sc
| 
| Character code properties: customize what to show
|   name: EURO SIGN
|   general-category: Sc (Symbol, Currency)
|   canonical-combining-class: 0 (Spacing, split, enclosing, reordrant, and Tibetan subjoined)
|   bidi-class: ET (European Number Terminator)
|   mirrored: N
| 
| There are text properties here:
|   auto-composed        t
|   charset              windows-1252
`----

which is almost correct.  (Category seems wrong to me.)

Note that the glyph code for a ttf is the physical position in the
glyf table in the sfnt file, not a character set code point.

I typically start this this command line (by way of an entry in my
icewm menu):

,----
| emacs --enable-font-backend -xrm '*FontBackend: xft' -xrm 'emacs.font: DejaVu Sans Mono:pixelsize=14'
`----

and then run this function:

,----
| (defun jhc-backend-xft-fonts () "" (interactive)
|   (set-fontset-font (frame-parameter nil 'font)
| 		    'han '("SimHei" . "unicode-bmp"))
|   (set-fontset-font (frame-parameter nil 'font)
| 		    'arabic '("Lucida Sans Typewriter" . "unicode-bmp"))
|   (set-fontset-font (frame-parameter nil 'font)
| 		    'yi '("SIL Yi" . "unicode-bmp"))
|   (set-fontset-font (frame-parameter nil 'font)
| 		    'thai '("Lucida Sans Typewriter" . "unicode-bmp"))
| )
`----

That is not perfect; there are still several holes in font coverage
which need to be filled code-point by code-point rather than script-
by-script as above, but it is getting there.....

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

Re: Euro Sign and Bitstream Vera

[M G Berberich]

On Mon, 29 Jan 2007 00:59:06 +0100, Peter Dyballa <Peter_Dyballa@Web.DE> wrote:
>
> Am 27.01.2007 um 22:13 schrieb M G Berberich:
>
>> I have set fontsets (shortend by ‘…’) as this:
>>
>> (create-fontset-from-fontset-spec
>>  "-bitstream-bitstream vera sans mono-…-*-fontset-vera11,
>>   latin:-bitstream-bitstream vera sans mono-…-*-iso10646-1,
>>  [...]
>>   symbol:-bitstream-bitstream vera sans mono-…-iso10646-1,
>>   symbol:-unknown-freemono-…-iso10646-1,
>>   greek:-unknown-freemono-…-iso10646-1,
>>   cyrillic:-monotype-andale mono-…-iso10646-1")
>>
>> BTW: I have defined symbol: two times, does this make sense?
>
> No, this is non-sense. Which is the right definition? And: what is  
> "symbol?" I mean, where in Unicode do you find "symbol?" (at 100.000  
> spots maybe)

A charset like greek, latin,… I suppose. 

>> I added the output of ‘C-u C-x =’ below, the “working”-case differns
>> from the “non-working”-case in the glyph tht is used to display the
>> (same) char (#xBD / #x102) and in the property ‘fontified’.
>
> IMO it cannot work to take glyphs from postions U+00BD or U+0102 from  
> Bitstream Vera to print the €. There is probably no font putting € at  
> these positions. 

But U+0102 gives the right character ‚€‘ (EURO).

> The problem might come from the fontsets you use.  Did you notice
> when this or that glyph is used, is there some correlation with the
> encoding used in the buffer? 

No, it's utf-8 both times.

> This is a new feature in Unicode Emacs 23.0.0 – and maybe it's
> buggy. So you should consider to create a bug report. Then you'll
> have contact with those who make the software!
>
> Where do the fonts come from? Do they come from fontconfig (fc-cache/ 
> fc-list) or is standard X11 serving them? 

I suppose from fontconfig, because they are anti-aliased, how do I
determine this?

> Do the Emacs 23.0.0 fontsets allow ranges like in:

> 	(set-fontset-font "fontset-09pt_adobe_courier" (cons (decode-char  
> 'ucs #x0700) (decode-char 'ucs #x074f)) '("courier new" .  
> "iso10646-1"))	; Syriac

Yes.

  (set-fontset-font "fontset-vera11"
    'mule-unicode-0100-24ff '("dejavu sans mono" . "iso10646-1"))

shows the correct Euro-sign ‚€‘ but

  (set-fontset-font "fontset-vera11"
    'mule-unicode-0100-24ff '("bitstream vera sans mono" . "iso10646-1"))

shows a ‚¤‘. Other applications work fine with Vera, so the problem
depends on emacs /and/ bitstream vera sans mono.

	MfG
	bmg

-- 
„Des is völlig wurscht, was heut beschlos- | M G Berberich
 sen wird: I bin sowieso dagegn!“          | berberic@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg)  | www.fmi.uni-passau.de/~berberic

Re: Euro Sign and Bitstream Vera

[Peter Dyballa]

Am 30.01.2007 um 22:00 schrieb M G Berberich:

> But U+0102 gives the right character ‚€‘ (EURO).

Definitely not! A quite reliable source, from Kermit (utf8.txt), but  
also an application, UnicodeChecker) explain:

	[Ă]  0102  LATIN CAPITAL LETTER A WITH BREVE
	[€]  20AC  EURO SIGN

Have you checked what gucharmap tells?

>
>> This is a new feature in Unicode Emacs 23.0.0 – and maybe it's
>> buggy. So you should consider to create a bug report. Then you'll
>> have contact with those who make the software!
>>
>> Where do the fonts come from? Do they come from fontconfig (fc-cache/
>> fc-list) or is standard X11 serving them?
>
> I suppose from fontconfig, because they are anti-aliased, how do I
> determine this?

Anti-aliasing is not delivered from libfontconfig – you have GTK  
enabled and GNOME in use! And it's actually libfreefont2 that  
provides the calls and means to anti-aliasing, but then it's GTK+2  
that makes use of these capabilities. Libfontconfig exists to  
determine a font by describing its features – and also alternatives/ 
substitutes, it's more of a human approach.

Whether you are using fontconfig or usual X11 you can determine by  
the syntax you use to describe the font. This one is fontconfig:

	Bitstream Vera Sans Mono:style=Roman:weight=100

the next one is usual X11, so-called XFLD syntax:

-bitstream-bitstream vera sans mono-medium-r-normal--0-0-0-0-m-0- 
iso10646-1


--
Mit friedvollen Grüßen

   Pete

"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."