Help
Add this page to your book
Show book (0 pages)
Suggest pagesTalk:October 2011 Coding Challenge
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Contest and RTL | 5 | 09:58, 21 October 2011 |
(from the saw-it-coming department)
I use Hebrew as my interface language in MediaWiki.org. I clicked on the coding challenge link and it showed the contest description as RTL.
It's not very important to translate this description (although it would be nice), but until it's possible to translate it, can anyone please add class="mw-content-ltr" to it? It seems that i don't have the permission to do it here.
Thank you. --Amir E. Aharoni 08:00, 21 October 2011 (UTC)
Since I don't know which message you were talking about, I have wrapped the following in it:
- MediaWiki:Contest-welcome-rules
- MediaWiki:Contest-submission-new-submission
- MediaWiki:Contest-submission-challenge-description
- MediaWiki:Customusertemplate-contests-welcomecreation
- MediaWiki:Customusertemplate-contests-loginstart
- MediaWiki:Contests-October 2011 Coding Challenge Opportunities
- MediaWiki:Contests-October 2011 Coding Challenge Signup Email
- MediaWiki:Contests-October 2011 Coding Challenge Introduction
- MediaWiki:Contests-October 2011 Coding Challenge Reminder Email
Thank you.
I am mostly talking about Special:ContestWelcome/October_2011_Coding_Challenge. Now most of it is properly LTR, but the message at the top ("The Wikimedia Foundation is pleased to announce the October 2011 Coding Challenge.") and the big blue buttons at the bottom are still RTL.
Unfortunately some of these UI message updates led to the <span> markup being user-visible due to different message-handling in the extension.
We're talking about a remote edge case here (user has a MediaWiki.org account and their UI language set to an RTL language and wants to participate in an English language contest). Given that the Contest UI messages are in heavy duty production use right now, I would ask that they only be modified if absolutely necessary. If I hadn't been awake way too late, we'd probably have broken the experience for a few hundred users.
I strongly suggest that any RTL issues or other i18n issues with the extension or its messages be addressed in the context of the actual extension code, so these changes can be more carefully reviewed and deployed without affecting production.
CN is set to spam the message in 14 different languages, Expecting users not to have the interface in non-english isn't a edge case in my view.
It wouldn't stay broken for long, because i would notice it, if no-one else would before me.
If it's impossible to translate the messages and too complicated to fix the directionality, getting the link in CN to point to an url with ?uselang=en should fix it.
