From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: schwab@suse.de, emacs-devel@gnu.org
Subject: Re: Problem with narrow vs condensed fonts
Date: Tue, 26 Feb 2008 12:10:13 +0900 [thread overview]
Message-ID: <E1JTqCr-0002K5-6f@etlken.m17n.org> (raw)
In-Reply-To: <jwvprukihh9.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 25 Feb 2008 21:23:57 -0500)
In article <jwvprukihh9.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > But, as you changed the numeric value of of `normal' weight
> > from 100 to 101, ftfont_list doesn't include regular weight
> > font (most of ttf has regular weight).
> Why does it only accept an exact-match?
Because that's the spec I desided for that API of (struct
font_driver *)->list. I wanted to distinguish required
(i.e. mandatory) font-spec and preferred font-spec. `list'
returns fonts matching with a required spec, and
font-selection routine find a font besting matching with
preferred spec from them.
So, we should not give FONT-SPEC containing just preferred
specs to `list'.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-02-26 3:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 22:21 Problem with narrow vs condensed fonts Stefan Monnier
2008-02-18 23:05 ` Lennart Borgman (gmail)
2008-02-24 21:32 ` Andreas Schwab
2008-02-25 2:09 ` Stefan Monnier
2008-02-25 6:23 ` Kenichi Handa
2008-02-25 8:27 ` Jason Rumney
2008-02-25 11:24 ` Kenichi Handa
2008-02-25 11:35 ` Jason Rumney
2008-02-25 10:25 ` Andreas Schwab
2008-02-25 15:45 ` Stefan Monnier
2008-02-26 1:54 ` Kenichi Handa
2008-02-26 2:23 ` Stefan Monnier
2008-02-26 3:10 ` Kenichi Handa [this message]
2008-02-26 4:48 ` Stefan Monnier
2008-02-26 4:58 ` Stefan Monnier
2008-02-26 9:45 ` Jason Rumney
2008-02-26 11:18 ` Kenichi Handa
2008-02-26 12:00 ` Jason Rumney
2008-02-28 11:17 ` Jason Rumney
2008-02-28 12:05 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2008-02-25 9:16 Angelo Graziosi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JTqCr-0002K5-6f@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@suse.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.