Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=531105
Behdad Esfahbod besfahbo@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |richard@hughsie.com, | |smparrish@gmail.com Component|fontconfig |PackageKit AssignedTo|besfahbo@redhat.com |richard@hughsie.com
--- Comment #1 from Behdad Esfahbod besfahbo@redhat.com 2009-10-26 18:17:15 EDT --- (In reply to comment #0)
The font stack triggers the PK font auto-installer for stuff like N'ko or Ancient Persian for which fontconfig has no orthography
Therefore, those calls will never succeed and the user is bothered for no good reason
This is surely a bug. And easy to fix, in at least two ways on the PK side:
1) Only show a dialog if there's any font supporting that language. This was supposed to be the default. Not sure why it wasn't implemented this way.
2) In the GTK+ module, use FcLangGetCharset() to check whether fc knows about the language.
IMO both of them should be done.
fc-query/cache should also generate PK metadata for unicode blocks, so that when the font stack needs a glyph which is not part of an orthography, PK can search for fonts that cover the corresponding unicode block (stuff like symbols will probably never make it in an orth)
Not a huge fan of this. Lets add orth's where missing.