https://bugzilla.wikimedia.org/show_bug.cgi?id=44394
--- Comment #61 from Steven Walling <[email protected]> --- (In reply to comment #60) > (In reply to comment #59) > > There are plans to expand it further, but I think we have to acknowledge > > that > > we haven't made substantial progress here over the past seven months. We > > can't > > credibly argue that the inconsistencies are temporary / transitional. > > > [...] > > > I think we should start by merging MatmaRex's patch. We've let this drag > > on long enough and we've run out of excuses. By allowing this to fester > > we've both undermined trust in our work and soured relationships that > > could be pleasant and productive. Let's move on, really. > > That is choosing one direction, which is "Don't specify a stack". It's a > good-faith one. It would also make sense if we're (particularly the design > and > UX teams) not willing to put in the work to finalize a global stack. > > > The bits and pieces of design advice that I read tonight were unanimous in > > recommending explicit & specific typography over browser defaults. We > > shouldn't scorn MediaWiki design conventions, but it's 2013, the web has > > changed, and what was reasonable a decade ago is not necessarily reasonable > > today. > > However, as you note here, specifying a stack is the clear trend. Taking > that > general trend (as well as the opinions of the design team here) into account, > specifying a global Vector stack currently seems like the better direction. > > There is a proposal for such a stack at > https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Typography . I > think the body one (essentially the stack in question at this bug) is close > to > being ready for the prime time. Ori presents a fair point (on IRC), that we > should do a final review of the trade-offs, check our work, and make > adjustments to the stack if needed. > > I will email the design list to point to this bug. Matt's comments echo my feelings precisely. Rolling back to the prior default is the easy thing to do. Making consistent change in the font stack is hard and takes time. The current limbo is inconsistent and messy, but personally I don't think the universe has exploded because of it. The design team and others are working on an implementation of a new Vector font stack (described in the page Matt linked to, patch forthcoming). What I want is to support that as an answer to the current inconsistency, but it's not going to happen overnight. In the meantime, if Ori or someone with +2 in core thinks it's not reasonable to request that we wait on that as a way forward, they can feel free to merge Matma's patch over my objections. No hard feelings. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
