Re: Accumulated fontset definition tweaks for testing

[sand]

Kenichi Handa writes:
> Thank you for them.  I'm going reflect 1 to 3 in fontset.el.
> I think 4 and 5 is not necessary if we implement
> registry-representative-chars as I wrote in the previous
> mail.

I enabled simultaneous X and Xft backends using

  Emacs.FontBackend: xft,x

and some of the non-Unicode characters showed display problems that
didn't appear in an Xft-only configuration.  They were falling back to
other fonts even though my "normal" Neep Alt font had glyphs for them.
I was able to fix the problems with some additional fontset
definitions.

  ;; Needed to keep the non-Unicode Esperanto HELLO text from displaying
  ;; as Palladino.
  (set-fontset-font "fontset-default" 'latin
    (font-spec :registry "iso8859-3" :script 'latin) nil 'prepend)

  ;; Needed to keep the non-Unicode Russian HELLO text from displaying
  ;; as Palladino.
  (set-fontset-font "fontset-default" 'cyrillic
    (font-spec :registry "iso8859-5" :script 'cyrillic) nil 'prepend)

  ;; Needed to keep the non-Unicode Vietnamese HELLO text from displaying
  ;; in the Chinese font Ar Pl Zenkai Uni.
  (set-fontset-font "fontset-default" 'latin
    (font-spec :registry "viscii1.1-1" :script 'latin) nil 'prepend)

  ;; Needed to keep certain non-Unicode Greek HELLO text characters
  ;; from displaying in the Japanese font Sazanami Mincho (and showing
  ;; up blank on the screen).
  (set-fontset-font "fontset-default" 'greek
    (font-spec :registry "iso8859-7" :script 'greek) nil 'prepend)

Does the order in which the drivers are specified in the resource have
any effect on the behavior of Emacs?  I wasn't able to see any
difference between "x,xft" and "xft,x".

Derek

-- 
Derek Upham
address@hidden