Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||vcl: improve selection of fallback font by supplying language hint when none exists|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||ACCEPTED ---||QA Contact:|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
|Issue Depends on:|
Description caolanm 2009-10-10 16:37:21 UTC
Often we have some knowledge of the language that some text is written in when we are forced to use glyph fallback. This helps fontconfig pick a good font to use for that text. In some circumstances, e.g. in the UI itself we don't have any hints to fontconfig basically is forced to pick one at random. What basically pango does in this circumstance is categorize the script that the text is written in and assign it a example language written using that script when asking fontconfig for glyph fallback which gives better results. Patch attached to do that. See https://bugzilla.redhat.com/show_bug.cgi?id=527719 for some screenshots of the problem at the moment that this solves.
Comment 2 email@example.com 2009-10-14 13:57:17 UTC
It may be a better idea to have the change in fontconfig itself: if all the codepoints that fc is requested to resolve are typical for script XXX then fc should prefer a font designed for XXX.
Comment 3 philipp.lohmann 2009-11-05 15:47:52 UTC
@hdu: so go or no go ? meaning integrate or change to enhancment ?
Comment 4 firstname.lastname@example.org 2009-11-06 08:21:51 UTC
We already provide the language to fontconfig if we know the language attribute of the text. If we do not know the language one can only guess based on the missing codepoints. That is just what the patch does. It is a nice idea for libfontconfig where it belongs. Not doing it there works against (or at least around) FC by pretending to know something which we don't know. Now for the UI issue itself: the selected UI language is known and should be provided.