From: anhnmncb <anhnmncb@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs could not show this symbol.
Date: Fri, 29 Feb 2008 08:25:11 +0800 [thread overview]
Message-ID: <86prug7gns.fsf@freebsd.hasee.cpu> (raw)
In-Reply-To: mailman.8038.1204210929.18990.help-gnu-emacs@gnu.org
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> 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.
Vista courier has a symbol even dejavu doesn't contain :``ˏ'' , could
you see it? ;p
>> (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.
I think this setting is meant that when the fontset-dejavu donesn't have
a suitable font to show the character, then emacs will use fontset-default
instead, don't know if I correct, but I find that this setting works
well for me.
>
>> 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
I changed dejavu sans mono to dejavu sans, and m to p, did not work.
--
Regards,
anhnmncb
gpg key: 44A31344
next prev parent reply other threads:[~2008-02-29 0:25 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
[not found] ` <mailman.8038.1204210929.18990.help-gnu-emacs@gnu.org>
2008-02-29 0:25 ` anhnmncb [this message]
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=86prug7gns.fsf@freebsd.hasee.cpu \
--to=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).