From: Kenichi Handa <handa@m17n.org>
Cc: wilde@sha-bang.de, jyavner@member.fsf.org, emacs-devel@gnu.org,
rms@gnu.org, storm@cua.dk
Subject: Re: Default face problem
Date: Mon, 01 May 2006 13:32:13 +0900 [thread overview]
Message-ID: <E1FaQ4z-0002kz-00@etlken> (raw)
In-Reply-To: <87bquicu9k.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 30 Apr 2006 23:14:16 -0400)
In article <87bquicu9k.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> On this selection, auto-scaled font is refused even if
>> scalable-fonts-allowed is non-nil.
> For what it's worth, "scalable-fonts-allowed" refers to vector-fonts (which
> are inherently scalable). Whereas you're talking about scaling
> a bitmap font.
Here a excerpt from the document of XLFD.
------------------------------------------------------------
PIXEL_SIZE usually incorporates additional vertical spacing
that is considered part of the font design.
(Note, however, that this value is not necessarily equivalent to the height
of the font bounding box.)
Zero is used to indicate a scalable font (see section \n(sS)
...
------------------------------------------------------------
So, for X windows, I think this kind of font is also a kind
of scalabe font.
-xos4-terminus-medium-r-normal--0-0-72-72-c-0-iso8859-1
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-05-01 4:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 22:35 incomplete header-line with 3d boxes and prop fonts Stefan Monnier
2006-04-24 0:25 ` Kim F. Storm
2006-04-24 6:58 ` Stefan Monnier
2006-04-24 11:51 ` Richard Stallman
2006-04-24 12:11 ` Kim F. Storm
2006-04-25 3:16 ` Jonathan Yavner
2006-04-25 22:04 ` Richard Stallman
2006-04-25 12:38 ` Sascha Wilde
2006-04-25 14:47 ` Kim F. Storm
2006-04-25 15:11 ` Sascha Wilde
2006-04-27 22:53 ` Kim F. Storm
2006-04-28 11:34 ` Default face problem [was: Re: incomplete header-line with 3d boxes and prop fonts] Kim F. Storm
2006-05-01 2:41 ` Kenichi Handa
2006-05-01 3:14 ` Default face problem Stefan Monnier
2006-05-01 4:32 ` Kenichi Handa [this message]
2006-05-01 12:34 ` Stefan Monnier
2006-05-01 12:51 ` Kenichi Handa
2006-05-01 13:58 ` Stefan Monnier
2006-05-02 0:42 ` Kenichi Handa
2006-05-01 8:25 ` Kim F. Storm
2006-05-01 12:35 ` Stefan Monnier
2006-05-01 12:49 ` Kim F. Storm
2006-05-08 5:51 ` Kenichi Handa
2006-05-08 8:47 ` Kim F. Storm
2006-05-08 11:50 ` Kenichi Handa
2006-05-08 12:19 ` Kim F. Storm
2006-05-10 4:17 ` Kenichi Handa
2006-05-10 12:21 ` Kim F. Storm
2006-05-10 12:41 ` Kenichi Handa
2006-05-10 17:45 ` Eli Zaretskii
2006-05-11 0:36 ` Kenichi Handa
2006-05-11 3:40 ` Eli Zaretskii
2006-05-11 4:35 ` Kenichi Handa
2006-05-13 13:04 ` Eli Zaretskii
2006-05-15 1:41 ` Kenichi Handa
2006-05-15 3:33 ` Eli Zaretskii
2006-05-15 4:47 ` Kenichi Handa
2006-05-10 17:45 ` Eli Zaretskii
2006-04-24 13:02 ` incomplete header-line with 3d boxes and prop fonts Stefan Monnier
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=E1FaQ4z-0002kz-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=jyavner@member.fsf.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
--cc=wilde@sha-bang.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.
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).