unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
Cc: Hongsheng <zhaohscas@yahoo.com.cn>, emacs-devel@gnu.org
Subject: Re: BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend?
Date: Mon, 20 Nov 2006 06:14:52 -0500	[thread overview]
Message-ID: <m3vela9xoc.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <E1Gm4IM-0006iA-00@etlken> (Kenichi Handa's message of "Mon\, 20 Nov 2006 17\:14\:26 +0900")

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

  parent reply	other threads:[~2006-11-20 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20  4:19 BTW, if I want Emacs to support the CJK-EXT B Chinese Characters, must I use the arg --enable-font-backend? Hongsheng
2006-11-20  8:14 ` Kenichi Handa
2006-11-20  9:30   ` Hongsheng
2006-11-28  6:36     ` Kenichi Handa
2006-11-20 11:14   ` James Cloos [this message]
2006-11-20 22:21     ` James Cloos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3vela9xoc.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=emacs-devel@gnu.org \
    --cc=zhaohscas@yahoo.com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).