Re: handling of fonts in the langpack plugin

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 02/27/2012 11:41 AM, Bill Nottingham wrote:
> Nicolas Mailhot (nicolas.mailhot@xxxxxxxxxxx) said: 
>> The main problem I see is that current provides are fully automated, and only
>> require looking at the font package being created content. What you ask for is
>> a cross-repo require, so either people would need to fill them in manually
>> (with the reliability and cruft accumulation of cross-processes) or each font
>> package would need to depend on every other font package in the repo at build
>> time to check if it's the priority one for a specific language or not.
> How so? I'm wondering about the feasibility of a hardcoded list. Right now,
> we 'know' which fonts should be the default for non-dejavu languages (at
> least, we set them up that way in comps), so why not add a quick hardcoded
> provide for those 10-20 packages and just change that provide if the
> preferred font infrequently changes?

So, right now we Provide "font(:lang=fa)" from all fonts supporting that
language.  Why can't you create a metapackage default-fonts that provides
"font(default:lang=fa)", etc that would then require the default font for the

Moreover, that metapackage can be made automatically.  It just needs to
install all font packages available in the repository, walk through all
languages, and see what font fontconfig chooses for that language.


> Sure, it's ugly and manual, but it's a limited level of manual work that
> shouldn't explode.
> Bill
> _______________________________________________
> fonts mailing list
> fonts@xxxxxxxxxxxxxxxxxxxxxxx
fonts mailing list

[Index of Archives]     [Fedora Users]     [Font Configuration]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux