From: Kenichi Handa <handa@m17n.org>
Cc: 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 17:14:26 +0900 [thread overview]
Message-ID: <E1Gm4IM-0006iA-00@etlken> (raw)
In-Reply-To: <20061120041919.GA8024@localdomain> (message from Hongsheng on Mon, 20 Nov 2006 12:19:19 +0800)
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
next prev parent reply other threads:[~2006-11-20 8: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 [this message]
2006-11-20 9:30 ` Hongsheng
2006-11-28 6:36 ` Kenichi Handa
2006-11-20 11:14 ` James Cloos
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=E1Gm4IM-0006iA-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
/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).