From: Jason Rumney <jasonr@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: schwab@suse.de, emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: Problem with narrow vs condensed fonts
Date: Tue, 26 Feb 2008 09:45:59 +0000 [thread overview]
Message-ID: <47C3DFD7.4030406@gnu.org> (raw)
In-Reply-To: <jwvir0cgvr1.fsf-monnier+emacs@gnu.org>
Stefan Monnier wrote:
>> Right: the defaulting to "normal" should be done when the value is later
>> used as a preferred spec, but a wildcard should be used instead if the
>> value is later used as an exact spec.
>>
>
> Or rather the defaulting to "normal" should be done elsewhere: when
> choosing the preferred font for a SPEC which doesn't specify any weight.
>
As you can see from the checkin comment, I tried doing this in
font_score, but it didn't have any effect, so I ended up making the
change right at the beginning of the font selection process in
font_parse_fcname. I left the change in font_score even though it didn't
work, because it seemed right to prefer normal fonts there if weight and
slant were unspecified (and presumably adstyle).
next prev parent reply other threads:[~2008-02-26 9:45 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
2008-02-26 4:48 ` Stefan Monnier
2008-02-26 4:58 ` Stefan Monnier
2008-02-26 9:45 ` Jason Rumney [this message]
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=47C3DFD7.4030406@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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.