From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Harry Putnam <reader@newsguy.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: using emacs with nx
Date: Tue, 30 Jul 2013 17:29:05 +0200 [thread overview]
Message-ID: <19AB2BB8-0AC3-4277-A81D-C64181E578F8@Web.DE> (raw)
In-Reply-To: <87iozshyzp.fsf@newsguy.com>
Am 30.07.2013 um 17:02 schrieb Harry Putnam:
> XLFD?
X Logical Font Description Conventions – when you have X11 installed you should be able to locate xorg-docs-X.Y/specs/XLFD/xlfd.{html,pdf,ps,txt,xml}…
The X11 font names contain a lot of information in a construct like: -misc-fixed-medium-r-normal--0-0-0-0-c-0-iso8859-1.
foundry-font name-weight-slant-width-style-pixel size-point size-resolution X-resolution Y-spacing-average width-charset registry-charset encoding
>
> Just curious:
> Why is better for fonts not to be in XLFD notation?
They are then supplied by libfontconfig which offers to automatically find a(nother) font that can deliver missing characters. Libfontconfig also provides vector fonts (PostScript, TrueType, OpenType) which together with libotf and m17n-lib allow bidi(rectional) typesetting and font shaping, necessary for some Asian scripts.
--
Greetings
Pete
If you don't find it in the index, look very carefully through the entire catalogue.
– Sears, Roebuck, and Co., Consumer's Guide, 1897
prev parent reply other threads:[~2013-07-30 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 7:34 using emacs with nx Andrew Michael Levin
2013-06-10 11:14 ` Peter Dyballa
2013-06-13 11:35 ` Andrew Michael Levin
2013-06-13 12:13 ` Peter Dyballa
2013-07-29 13:35 ` Andrew Michael Levin
2013-07-29 15:11 ` Peter Dyballa
2013-07-29 16:23 ` Eli Zaretskii
2013-07-30 2:28 ` Harry Putnam
2013-07-30 8:24 ` Peter Dyballa
2013-07-30 15:02 ` Harry Putnam
2013-07-30 15:29 ` Peter Dyballa [this message]
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=19AB2BB8-0AC3-4277-A81D-C64181E578F8@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=reader@newsguy.com \
/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).