From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: anhnmncb <anhnmncb@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs could not show this symbol.
Date: Thu, 28 Feb 2008 16:01:59 +0100 [thread overview]
Message-ID: <B1B716ED-A121-436D-879B-C193A20BCAF8@Web.DE> (raw)
In-Reply-To: <86zltluu1w.fsf@freebsd.hasee.cpu>
Am 28.02.2008 um 13:47 schrieb anhnmncb:
> Now I have resolved the problem though don't know why :)
> I use this configuration in .Xdefaults:
> --------------------------x----------------------------
> x--------------------------------
> Emacs.Fontset-0: \
> -misc-dejavu Sans Mono-medium-r-*-*-12-*-*-*-m-*-fontset-dejavu,\
> chinese-gb2312:-microsoft-Microsoft YaHei-medium-r-*-*-*-*-*-*-p-
> *-iso10646-1,\
> chinese-gbk:-microsoft-Microsoft YaHei-medium-r-*-*-*-*-*-*-p-*-
> iso10646-1,\
> gb18030:-microsoft-Microsoft YaHei-medium-r-*-*-*-*-*-*-*-*-
> iso10646-1,\
> thai-tis620:-misc-fixed-medium-r-*-*-*-*-*-*-*-*-iso10646-1,\
> mule-unicode-0100-24ff:-monotype-courier-medium-r-*-*-*-*-*-*-m-*-
> iso10646-1
I admit that I am not the font or fontset expert, I would have used
here a gb2312.1980-0 encoded for the chinese-gb2312 encoding, a
gb18030.2000-0 encoding for the gb18030 encoding, and a tis620-2
encoded font for the thai-tis620 encoding. For mule-unicode-0100-24ff
encoding I would use a font that has more to offer than Monotype
Courier, Lucida Sans Typewriter or DejaVu Sans Mono or Free Mono.
Well, anyway, I should improve my own settings, too, and learn from
this a bit.
> And this in .emacs:
> --------------------------x----------------------------
> x--------------------------------
> (create-fontset-from-fontset-spec
> (concat
> "-misc-dejavu Sans Mono-medium-r-*-*-12-*-*-*-m-*-fontset-dejavu,"
> "chinese-gb2312:-microsoft-Microsoft YaHei-medium-r-*-*-*-*-*-*-p-
> *-iso10646-1,"
> "chinese-gbk:-microsoft-Microsoft YaHei-medium-r-*-*-*-*-*-*-p-*-
> iso10646-1,"
> "gb18030:-microsoft-Microsoft YaHei-medium-r-*-*-*-*-*-*-*-*-
> iso10646-1,"
> "thai-tis620:-misc-fixed-medium-r-*-*-*-*-*-*-*-*-iso10646-1,"
> "mule-unicode-0100-24ff:-monotype-courier-medium-r-*-*-*-*-*-*-m-
> *-iso10646-1"))
Here above I would also check whether the font encodings match the
GNU Emacs encodings.
> (set-fontset-font "fontset-default"
> 'thai "-misc-fixed-medium-r-*-*-*-*-*-*-*-*-iso10646-1")
> (set-default-font "fontset-dejavu")
> (add-to-list 'default-frame-alist '(font . "fontset-dejavu"))
You were constructing a "fontset-default" and then you're setting a
"fontset-dejavu" to be used as default? I admit, documentation
(particularly examples) of fontsets can be improved.
>
> Another question, maybe emacs.font-backend is enabled by default?
You can check this easily by choosing "Send Bug Report..." from the
Help menu. It will show the configure options used. And ldd (on GNU/
Linux) could tell you which to libraries GNU Emacs is linked. This
can give you a hint of what it's able to use.
> I comment it and find that xft is going on well. Don't know what's the
> most correct way to configure fontset for xft emacs, although I tell
> emacs to use fontset-dejavu, I find that emacs doesn't use this
> fontset
> actually.
See my comment above!
> And many times emacs could not align a line correctly,
Because you are using monospaced and proportionally spaced fonts in
your fontsets:
*-*-p-*-iso10646-1
*-*-m-*-iso10646-1
--
Greetings
Pete
Mac OS X is like a wigwam: no fences, no gates, but an apache inside.
next prev parent reply other threads:[~2008-02-28 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 1:11 emacs could not show this symbol anhnmncb
2008-02-26 4:05 ` anhnmncb
2008-02-26 6:33 ` David Hansen
[not found] ` <mailman.7947.1204007911.18990.help-gnu-emacs@gnu.org>
2008-02-26 11:00 ` anhnmncb
2008-02-27 12:09 ` Peter Dyballa
[not found] ` <mailman.7995.1204114181.18990.help-gnu-emacs@gnu.org>
2008-02-28 0:10 ` anhnmncb
2008-02-28 0:56 ` anhnmncb
2008-02-28 10:12 ` Peter Dyballa
2008-02-28 9:49 ` Peter Dyballa
[not found] ` <mailman.8026.1204192187.18990.help-gnu-emacs@gnu.org>
2008-02-28 12:47 ` anhnmncb
2008-02-28 15:01 ` Peter Dyballa [this message]
[not found] ` <mailman.8038.1204210929.18990.help-gnu-emacs@gnu.org>
2008-02-29 0:25 ` anhnmncb
2008-02-29 11:15 ` Peter Dyballa
2008-02-26 11:35 ` Peter Dyballa
2008-02-26 11:46 ` anhnmncb
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=B1B716ED-A121-436D-879B-C193A20BCAF8@Web.DE \
--to=peter_dyballa@web.de \
--cc=anhnmncb@gmail.com \
--cc=help-gnu-emacs@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.
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).