BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

[Hongsheng]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 366 bytes --]

Dear Kenichi,

If I want the Emacs to support CJK-EXT B Chinese characters, must I run the
Emacs with the argument: --enable-font-backend?

I want to know whether it's possible to display the full unicode characters
with XLFD other than XFT?

Best,
Hongsheng.
__________________________________________________
¸Ï¿ì×¢²áÑÅ»¢³¬´óÈÝÁ¿Ãâ·ÑÓÊÏä?
http://cn.mail.yahoo.com

Re: BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

[Kenichi Handa]

In article <20061120041919.GA8024@localdomain>, Hongsheng <zhaohscas@yahoo.com.cn> writes:

> Dear Kenichi,
> If I want the Emacs to support CJK-EXT B Chinese characters, must I run the
> Emacs with the argument: --enable-font-backend?

Not necessarily.

> I want to know whether it's possible to display the full unicode characters
> with XLFD other than XFT?

Technically it's possible but there's no standard way.
First of all, I don't know if there's an agreement about
what registry-encoding to use for an X font for Unicode SIP
area.  So here I assume that you somehow manage to get an X
font whose registry-encoding part name is "iso10646-2".  I
can't tell how to make your TTF recognized by X server as
such a font.

Anyway, once you confirm that your font is working on X by,
for instance, xfd as below:

% xfd -fn .....-iso10646-2

what you have to do is this:

(push '("iso10646-2$" . unicode-sip) font-encoding-alist)
(set-fontset-font
 "fontset-default" 'han '(nil . "iso10646-2") 'append)

---
Kenichi Handa
handa@m17n.org

Re: BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

[Hongsheng]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1039 bytes --]

> > I want to know whether it's possible to display the full unicode characters
> > with XLFD other than XFT?
> 
> Technically it's possible but there's no standard way.
> First of all, I don't know if there's an agreement about
> what registry-encoding to use for an X font for Unicode SIP
> area.  So here I assume that you somehow manage to get an X
> font whose registry-encoding part name is "iso10646-2".  I
> can't tell how to make your TTF recognized by X server as
> such a font.
> 
> Anyway, once you confirm that your font is working on X by,
> for instance, xfd as below:
> 
> % xfd -fn .....-iso10646-2
> 
> what you have to do is this:
> 
> (push '("iso10646-2$" . unicode-sip) font-encoding-alist)
> (set-fontset-font
>  "fontset-default" 'han '(nil . "iso10646-2") 'append)

When I put this into my .emacs, the Emacs will return the wrong message as
this:

Wrong type argument: frame-live-p, append

Best,
Hongsheng.
__________________________________________________
¸Ï¿ì×¢²áÑÅ»¢³¬´óÈÝÁ¿Ãâ·ÑÓÊÏä?
http://cn.mail.yahoo.com

Re: BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

[Kenichi Handa]

Sorry for the late response.

In article <20061120093036.GA21045@localdomain>, Hongsheng <zhaohscas@yahoo.com.cn> writes:

> > (set-fontset-font
> >  "fontset-default" 'han '(nil . "iso10646-2") 'append)

> When I put this into my .emacs, the Emacs will return the wrong message as
> this:

> Wrong type argument: frame-live-p, append

Oops, that line should be:

(set-fontset-font
 "fontset-default" 'han '(nil . "iso10646-2") nil 'append)

---
Kenichi Handa
handa@m17n.org

Re: BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

[James Cloos]

>>>>> "Kenichi" == Kenichi Handa <handa@m17n.org> writes:

Kenichi> Technically it's possible but there's no standard way.
Kenichi> First of all, I don't know if there's an agreement about
Kenichi> what registry-encoding to use for an X font for Unicode SIP
Kenichi> area.

There is no agreement on the registry-encoding.  The use of iso646-2
was explicitly rejected some years back.  (This was around the point
where Keith started public work on libXft, fontconfig and the render
extension and library, and may have been part of the motication.)

About a year ago George added support for non-BMP fonts to fontforge
for the display of reference glyphs (it uses XLFD fonts for its UI).

Fontforge uses UnicodePlane-{1,2,3,...,16} for the non-BMP planes.

Note that the only way to get the X server to use such fonts -- w/o
patching the server, of course -- is to use BDF or PCF fonts.  The
X server's and font-server's support for scalable fonts will not do
the right thing with random, user-specified encodings.

The general consensus on the X lists has been to depricate server-
side fonts in favour of fontconfig-discovered client-side fonts, so
it is unlikely that any specification of registry-encoding for non-
BMP will ever be standardized.  And as far as I am aware, nothing
but fontforge and emacs are even trying to support them.  (Besides,
of course, the glyphs in the non-unicode Chinese encoding(s) which
map to SIP code points in Unicode, as already supported by Emacs.)

As for fonts supporting Unicode-Plane-n, I am not aware of any.
I've been hacking a bit, on but more often off, on one for the
math block, but even when finished that will have glyphs sized
for fontforge's grid display; I expect they'd be too small for
anyone's editing usage.  No one else has announced any work or
plans on the fontforge lists for any other UnicodePlane-x font.

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

Re: BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?

[James Cloos]

|> The use of iso646-2

Grr.  Obviously I meant iso10646-2....

[SIGH]

-JimC