Last modified: 2005-04-29 08:40:32 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 T2725, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 725 - LTR doesn't work on Hebrew pages
LTR doesn't work on Hebrew pages
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
PC Windows XP
: Normal normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: rtl
  Show dependency treegraph
Reported: 2004-10-16 15:37 UTC by David Shay
Modified: 2005-04-29 08:40 UTC (History)
0 users

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


Description David Shay 2004-10-16 15:37:59 UTC
In hebrew pages of, the text is 
normally aligned to the right. However, English text should 
be aligned to the left. The alignment was done using "DIV 
dir=ltr" HTML tag, but ut stopped working.
Comment 1 Brion Vibber 2005-04-29 07:59:19 UTC
There isn't a significant amount of English text visible there now.
Is this still a problem?
Can you provide a sample page?
Under which browsers and operating systems does the problem appear?
What exactly is the problem, with a comparison between expected and actual output?
Comment 2 Brion Vibber 2005-04-29 08:40:32 UTC
Ganglieri provided a test case at

The problem was this part of skins/monobook/rtl.css:
body * {
    direction: rtl;
/*    unicode-bidi: bidi-override;*/
    unicode-bidi: embed;

By CSS2's rules, the bits under the 'body *' selector actually override an explicit dir="ltr" 
attribute on any element in the body. Letting the value just inherit from body should work fine 
(tested briefly in Safari 1.3, Firefox 1.0.3, and IE 6.0 on XP SP2).

Committed to CVS HEAD and REL1_4 and installed live.

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