Description of problem:
All of detailed information is available on my post at the fonts list:
binding="same" in this template prevents to apply the rule for the specific language only properly. As a result, fonts is used for non-targetted languages and it may gives different look and feel in some cases.
I'd propose to get rid of binding="same" from this template.
Packages applied this rule is following. all of them needs to be fixed otherwise any of them will be still picked up as long as either of them are installed:
If you can get Behdad to state your analysis is right I see no problem in updating the template
This is the logs what I get from behdad so far:
<##fonts:tagoh> behdad: not sure why we use binding="same" in the patte
rn editing for lang specific thing
<##fonts:behdad> tagoh: if the goal is to alias differing names of equi
valent fonts, we want same binding
<##fonts:behdad> otherwise it doesn't really work
The main purpose of this rule isn't to get the exact alias right, because there are no fonts has certain glyph coverages for everything. and what we are expecting here would be to apply the certain fonts partially for the languages. I see same binding is still useful if one wants to replace AAA font to BBB font say.
Ok, if it doesn t really work, I ll change it when I m back from vacation next week
Do you want commit acces to fontpackages so you can contribute enhancements directly in the future ? I hate being the single point of failure there
(In reply to comment #4)
> Ok, if it doesn t really work, I ll change it when I m back from vacation next
Thanks. to make this clearer more, as a result, this change will puts more gravity to the priority prefix to determine which fonts is better, because strong binding only overrides this list after that and we use that for the case only where AA font could replaces BB font say. and it works expectedly as long as we test the language properly.
> Do you want commit acces to fontpackages so you can contribute enhancements
> directly in the future ? I hate being the single point of failure there
That would be really nice :) I continued the development of the fontconfig audit stuff recently and nearly ready to see if config files contains authorized rules against templates. I'm keen to contribute this audit program, but anyway.
Created attachment 413988 [details]
just attached here because I don't have access to commit it to fontpackages.
* Fri May 14 2010 Akira TAGOH <firstname.lastname@example.org>
— Get rid of binding="same" from l10n-font-template.conf (#578015)
Thanks for approving the request to access on fontpackages.git. just pushed the change the above.
and fixed in fontpackages-1.42-2.fc14.