הלוואי שהיה קל לדווח על בעיות בכל שפה.
את התמונה שלי צילם עמיתי קרטיק מיסטרי.
Ideally, yes. But ULS is not OOJS :/
- Having more skins on Wikimedia sites is an overhead for Wikimedia staff and volunteer developers, who will have to test everything with more skins. It's not necessarily a blocker, but it's one of the major issues in every discussion about skins. And no, we don't actually test every single thing with Monobook, let alone Modern or Cologne Blue, but compatibility bugs happen often enough for this to be an issue.
Do we currently test against all currently deployed skins?
I like it quite a lot, but:
Not rushing, I'll just mention that this came up a couple of times in the Hebrew Wikipedia as a desired feature.
The full stop change is the direction change. For the most part, the visual order of letters is not supposed to change. The biggest troubles are usually with English words in the middle of RTL paragraphs, with English paragraphs in the middle of RTL articles (and vice versa), with numbers, and with punctuation such as <, >, (, ), ;, ., etc.
It does change the direction, not the alignment. For example, if you do it while editing an English Wikipedia article, you'll notice that the full stops in the end of the sentences jump to the left end of the paragraphs. This is usually not needed in all-English articles, but it is very useful when editing articles that have quotations in Arabic, Hebrew, Persian, Urdu, and other RTL languages, and vice versa—in the Arabic Wikipedia, while editing articles that have English quotations or XML-like markup, such as <ref>, <poem>, etc., so it's almost all articles in RTL wikis.
Tested in en.wikipedia.beta.wmflabs.org.
OK, now, when the portal is in an RTL language, that RTL language appears correctly near the globe, but other LTR languages appear incorrectly. So for example English is shown as "articles +5 357 000", and it's also broken in Japanese, Italian, etc.
A couple of other possibilities:
Is this about updating the files from translatewiki, or about getting the files deployed to production?
Thank you so much for all these quick fixes!
I meant "progress bar". Thanks for the explanations.
Hmm... I need some explanations.
So if anything we should have a cronjob with a dry run, which triggers an alert somewhere when messages get translated locally. It could be one useful signal of an insufficient frequency of localisation updates, due to broken LocalisationUpdate or other reasons. (In general, we already know that the updates must be daily; but contingent data points are still useful.)
VE itself is being integrated into Content Translation, and when this will be a part of that.
At which article does this happen?
Might be related to https://www.mediawiki.org/wiki/Topic:Tlidxysh96y0knx1 , or maybe not.
Would a button or something help to be able to change the portal page's language without leaving the page?