https://bugzilla.wikimedia.org/show_bug.cgi?id=39381
Dereckson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |upstream See Also| |http://code.google.com/p/ch | |romium/issues/detail?id=144 | |135 --- Comment #15 from Dereckson <[email protected]> --- No, the Chrome bug is still unanswered, and there is no solution offered in IE. To better understand the issue, I would recommend this security review about Graphite: https://wiki.mozilla.org/Security/Reviews/Firefox/Graphite#Introduce_Feature Here the relevant feature summary: "[S]mart font / font shaping technology; similiarity to opentype - key diff: opentype assumption is a piece of code somewhere understands the rules of the script and layout to render properly - this is especially true of asian script type fonts - opentype does not have all that is needed for these script type languages, thus support for font designers is limited - instead of getting additions to the OS to support a font, graphite can support it at an application level to support the font/language" So, to have a good Javanese support, what would be needed: - Chrome implements Graphite engine or adds Javanese script support. - Firefox enables Graphite engine by default. - IE/Windows (I don't know at what level this is precisely done) adds support for Javanese script and layout rules. To enable it by default, it would seem reasonable for me we would need support in two of the three browsers -or- demonstrated evidence the Javanese visitors use at 75%+ one browser. Meanwhile, to enable it, turned off by default, would be acceptable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
