Last modified: 2013-04-02 11:26:26 UTC
Currently WebFonts are enabled on some wikis only.
But I think that all projects can benefit from WebFonts, i.e. pages like https://en.wikipedia.org/wiki/Akkadian_cuneiform#Syllabary and https://en.wiktionary.org/wiki/%F0%92%80%80
Compare with https://translatewiki.net/wiki/User:Raymond/Akkadian where Cuneiform/Akkadian characters looks very good.
Does this change need global community consensus?
Currently the config has commented out enable entries with "# XXX probably shouldn't be included". Should these wikis be excluded?
I very much want to enable it everywhere, but I also know that in the current state of the extension, there will be at least three languages that won't like it, and maybe more than three. One of them is Hebrew, the font for which is useful for testing, but not so much for reading; I'm working on improving that (a pet project of sorts).
As for the others, either better fonts are needed, or a more clever way to disable experimental fonts.
So it's a bit early for Wikimedia-wide deployment, but we are certainly working toward that.
RESOLVED LATER in that case.
Switching from LATER to the second most relevant resolution for fear of information loss. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65116
(No other resolution is actually correct, but Site requests without shell keyword are meant to be waiting on something.)
See also: bugzilla:43297 (Allow WebFonts to be loaded but disabled by default.)
[Adding bug 43297 to the "See Also" field.]
(In reply to comment #4)
> Switching from LATER to the second most relevant resolution
WebFonts is legacy; this will be done only as part of ULS, from what I understand.
*** This bug has been marked as a duplicate of bug 13097 ***