Comment 8 for bug 673949
Revision history for this message
| Denis Moyogo Jacquerye (moyogo) wrote Re: [Bug 673949] Re: Technical: Light/Medium/Regular/Bold, investigate /etc/fonts.d/ to map bold to next level up for each | #8 |
[Sorry for duplicates forgot to reply to all]
On Mon, Nov 15, 2010 at 6:19 PM, Mark Shuttleworth <email address hidden> wrote:
> On 15/11/10 15:31, Denis Jacquerye wrote:
>> Applications that can handle preferred family names and weights should
>> use Regular when Light is bolded, and Bold when Regular or Medium are
>> bolded.
>
> Really? We've been testing it the other way entirely: Medium is "Light
> Bold", and that seems to work well.
I meant when a "bold" button or keyboard shortcut is used, or if a
markup property 'font-weight=
In apps using legacy names (ID 1, 2) that should work.
But if using preferred names where they are all in the same big family
it's more problematic.
For example CSS2 specifies that bold should be the larger weight
(beyond 100). So Light (weight=300) will have Regular (weight=400) for
bold. CSS3 has some other scale in the works, but Light still has
Regular for bold.
>> Which is why I think having all apps handling preferred names is the
>> way to go. But I guess it is why one would want to jump through loops
>> with fontconfig.
> We can't fix all the apps in one cycle, and we can't fix proprietary
> apps, and we want the font widely used. So assuming a perfect app
> landscape is not a good starting point for the plan of record :-)
Then you probably don't want Condensed in the same preferred family as
the others.
With DejaVu, DejaVu Sans Condensed is just not available in apps like
the Gimp, but it is in Inkscape and others.
The Gimp just doesn't handle width variants for now, or we have a
problem in DejaVu that Inkscape, Gtk fontselector, etc. seem to
ignore.