Last modified: 2014-09-11 19:22:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72718, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70718 - Broken parentheses in Special:Sitematrix when language lacks translation and has opposite direction
Broken parentheses in Special:Sitematrix when language lacks translation and ...
Product: MediaWiki extensions
Classification: Unclassified
SiteMatrix (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Amir E. Aharoni
: i18n
Depends on:
Blocks: rtl
  Show dependency treegraph
Reported: 2014-09-11 14:50 UTC by Jan Ainali
Modified: 2014-09-11 19:22 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Jan Ainali 2014-09-11 14:50:55 UTC
There is something wrong going on in Special:SiteMatrix. When a language lacks translation to the users interface language and it has the opposite direction, the parentheses are broken. 


In the first column the description for the row with arz is broken. It says:

مصرى (مصرى) 

Example for the opposite direction:

The row with Alemannisch is broken. The same is the case for many other languages.
Comment 1 Lokal_Profil 2014-09-11 15:32:55 UTC
When the local translation for a language name is missing the system falls back to using the name of the language in that language itself instead. 

The direction for the text remains that of the local language however, independently on whether a local translation was found.

Expected behaviour:
The direction for the text should be that of the local language only if a translation is found. Otherwise it should be that of the target language.
Comment 2 Andre Klapper 2014-09-11 19:15:16 UTC
similar to

Note You need to log in before you can comment on or make changes to this bug.