From: Peter Dyballa <Peter_Dyballa@Web.DE>
Subject: Re: font display
Date: Sat, 22 Oct 2005 12:07:34 +0200 [thread overview]
Message-ID: <28f7b4f2c521bbec2789405f42f1dcbb@Web.DE> (raw)
In-Reply-To: <87ach2m9bj.fsf@nospam.nomore>
Am 22.10.2005 um 07:04 schrieb John:
> emacs -bg black -fg white -bw 0 -fn
> -*-lucida-medium-r-*-sans-14-140-*-75-p-81-iso8859-1 &
>
A short answer: mathematical characters (glyphs) are outside the ISO
8859-1 range. You could have more success with an iso10646-1 encoded
font.
Beside this GNU Emacs is able to get the missing (mathematical) glyphs
(outside ISO 8859-1) from other fonts of your system, or using
etl-fixed. By creating fontsets you have the chance to direct GNU Emacs
to use the specified fonts in the Unicode ranges of interest.
--
Greetings
Pete
Build a man a fire and he'll be warm for a night, but set a man on fire
and he'll be warm for the rest of his life.
next prev parent reply other threads:[~2005-10-22 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 5:04 font display John
2005-10-22 10:07 ` Peter Dyballa [this message]
[not found] ` <mailman.12216.1129975662.20277.help-gnu-emacs@gnu.org>
2005-10-22 15:47 ` John
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=28f7b4f2c521bbec2789405f42f1dcbb@Web.DE \
--to=peter_dyballa@web.de \
/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).