Nicolas Mailhot (nicolas.mailhot(a)laposte.net) 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?
Sure, it's ugly and manual, but it's a limited level of manual work that
shouldn't explode.
Bill