Last modified: 2007-03-02 14:38:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9137 - Text alignment should follow interface language, not wiki default/content language
Text alignment should follow interface language, not wiki default/content lan...
Status: RESOLVED DUPLICATE of bug 6100
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-02-28 23:27 UTC by brianna.laugher
Modified: 2007-03-02 14:38 UTC (History)
0 users

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


Description brianna.laugher 2007-02-28 23:27:46 UTC
In a multilingual wiki such as Commons, which has a default language English
(LTR text direction), when using uselang=XX URLs with RTL language codes (for
example ar, he), the text is still left-aligned (suits LTR languages), not right
(suits RTL). The text direction is correct, but the text alignment and
arrangement on the page is unnatural for RTL scripts.

Also form elements such as field labels still appear on the left instead of the
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-03-01 01:41:58 UTC
The content should still follow the directionality of the content language, of
Comment 2 Rotem Liss 2007-03-02 14:38:08 UTC

*** This bug has been marked as a duplicate of 6100 ***

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