I keep hearing about ALLL THE BUGS but I've not seen anything on
Bugzilla. This leads me to believe I've not been cc'ed on them or they
haven't been raised (which would be bad). Please can someone raise
these on Bugzilla - if these are being raised on wikis they are not
getting in front of people. If their are still bugs these are being
lost in the noise of this discussion. Maybe if we can clearly see
where the bugs are this can resolved much quicker. It's hard to argue
about the font stack if there are 20 bugs showing
* a screenshot of poor rendering
* the language
* the operating system
* the browser being used.
* plus points if we can identify via inspector the font family being used
Please feel free to raise these and cc me on them.
I've been working on this in my spare time, and I'm hoping to get some
spare time sometime next week to clean this up.
Regardless of the outcome, it would be extremely useful to document
these issues for The Web.
On Fri, Apr 11, 2014 at 4:11 AM, Erwin Dokter <erwin(a)darcoury.nl> wrote:
On 11-04-2014 04:35, Steven Walling wrote:
How are these specific, replicable bugs? DJ is saying things the current
solution is "not working" and we "cannot do better" but there is no
evidence about why this is the case for such a large number of users that
it requires a revert back to plain sans-serif.
People are talking in generalities and about problems related to areas
non-Latin script support, but not referring to bugs filed and which would
be fixed by the suggested patch. Brian's recent comment here is an example
of what we are asking to hear, though I don't think that requires a full
 shows half the world complaining about the typography refresh.
I'm sorry, but this is beginning to be like VE all over again; all I see now
coming out of the foundation is a big, unpenetrable progaganda machine with
a broken record: "There is no problem! This is a good change! There are no
Steven, it has been sufficiently demonstrated that the single, global font
stack is technically flawed and must be reverted. With all due respect to
the design team, they are *not* engineers and may not be aware of the
problems as they have emerged.
I will explain one more time: free/non-free fonts are not the issue,
MediaWiki is now forcing a Latin font stack that does not work in non-Latin
installations. This does not only affect current Mediawiki wikis but will
also affect new non-Latin MW 1.23 installations; they all had/have to fix
this one way or another, usually by resetting the font stack.
We must focus on a system that delivers a font stack on a per-language
basis. But that cannot happen as long as the global font stack is in place.
Unless you can raise issues that cause actual
functional problems that
outweigh the benefits of the new body font stack, I don't think merging
that patch is required to improve things and is worth the churn in user
experience for millions of readers.
*ANY* functional problem outweighs the purported benefits. That is because
actual functional problems should never be weighed; they should be fixed on
Please Steven, and the foundation in general, PLEASE step of the propaganda
wagon and do the responsible thing; remove the font stacks so that we can
focus on a *real* solution that actually *does* benefit the entire world.
I am really, really affraid that refusing to +2 this patch is going to
affect future attempts to fix this on a per-language basis.
Wikitech-l mailing list