font for jit chars?

[Aidan Kehoe]

 Ar an t-ocht? l? de m? na Samhain, scr?obh Ilya N. Golubev: 

 > So, now `specifier-matching-instance' MATCHSPEC `car' must be
 > `(get-charset 'jit-ucs-charset-0)', and this does make difference with
 > just `'jit-ucs-charset-0'? 

No. 

 > 1If so, please document. If all of it should not make difference, then my
 > tools, `xfontsel', `xfd', show wrong things, or at least fail to
 > reproduce how xemacs uses this font.

Does specifier-matching-instance give a different result for the font
compared to this: 

(face-font-instance 'default nil 'jit-ucs-charset-0) 

? This assumes it is the default face you are investigating. 

 > And should normally use them to select the font. So in this case will
 > need at least an item in `PROBLEMS' describing how to figure that X tools
 > are broken this way, and what to use instead.
 > 
 > Is `encode-as-utf-8' in font specifier TAG-SET essential?  If so,
 > please document.

It?s essential if you want the font specification to apply to the JIT UCS
character sets. See define-specifier-tag for documentation of the new
specifier tag charset predicates; encode-as-utf-8 is a predefined specifier
tag with the semantics of the following:

(define-specifier-tag 'encode-as-utf-8 nil 
    		      (lambda (charset) 
    		        (charset-property charset 'encode-as-utf-8)))

To apply it to jit-ucs-charset-0 specifically, you could write: 

(define-specifier-tag 'jit-ucs-charset-0 nil
    		      (lambda (charset) 
    		        (eq charset (find-charset 'jit-ucs-charset-0))))

(set-face-font 'default "your desired font xlfd" nil
	'(x jit-ucs-charset-0))

Again, this assumes the default face. 

-- 
Santa Maradona, priez pour moi!