הלוואי שהיה קל לדווח על בעיות בכל שפה.
את התמונה שלי צילם עמיתי קרטיק מיסטרי.
The current fonts look OK to me.
Any status is OK as long as the intention is to get rid of the gibberish.
Even if this change is easy to make, I prefer to invest time in fixing the issues that caused people to want the Abuse Filter than in perpetuating it.
The bug summary is unclear: I don't know what "a new Language project" is. It's possible that you meant "Make it easier to reach the current requirements for final approval in Wikimedia's language proposal policy" alias "Make it easier to qualify for a new language subdomain at Wikimedia".
In my opinion the biggest problem with adding a language to translatewiki.net/MediaWiki was not listed, and it's the duplication of information to add a language. It should not be necessary to patch both the translatewiki.net repository and ULS, for instance; ULS should automatically use all the local language codes, even if there isn't additional information about them in the CLDR/ULS data. This probably requires T59133 to be fixed.
Perfect timing! I'll be happy to test it at the Hackathon!
This should probably be fixed in https://my.wikipedia.org/wiki/MediaWiki:Common.css itself and not in the Content Translation extension. The local community should be consulted, of course.
(I hope it's the right place to mention this.)
Deployed in train, verified in production. Thanks for the quick review.
With @TerraCodes' patch it looks like this in Chrome:
Oh! Race condition :)
The PLURAL is not too complicated, and it's probably OK technically, but since you're asking, I'll ping @Nikerabbit again: is it correct to assume that if the value is neither 1 nor 2, the last form will be used for all other numbers?
Oh! Right. Yes, it should be four messages. Sorry about the hassle again, but that would be the right thing to do :/
Well, I first added four distinct messages in change 351834, but then I was told to combine them… and now this. Great :D
As far as I know, this is fixed. Please reopen if needed.
Here are good page for testing after deployment: