5 Tips To Deal with Right-to-Left Projects
Post from December 11, 2008 (↻ November 11, 2018), filed under Web Development.
This and many other posts are also available as a pretty, well-behaved e-book: On Web Development.
Know what goes into your markup and what goes into your style sheets. It’s actually quite simple: When available, you should always use dedicated bidi markup to describe your content. CSS may not be available, and the specs actually say that conforming user agents may ignore the
unicode-bidiproperties. The only exception is XML which does not offer specific bidi markup, in which case you should use CSS. This is the short version, W3C’s Internationalization Activity provides more detail.
Indicate directionality by the
dirattribute on the
htmlelement. Almost implied by the former point, set
@dirappropriately so that it covers all elements, not just those within the
body. To achieve this, make sure to set directionality on the
Avoid a separate RTL style sheet; better customize styling by means of an ID or class on the
bodyelement. Usually it’s just a small percentage of declarations that differs between a LTR and its RTL sister style sheet. Some small overhead may well be acceptable, meaning that having a few differing and overwriting declarations can be okay. To go for that (manually, in this case, not automatically), make sure you find all declarations that define anything specific to the left or right (typically referring to
text-align, and the like), customize those declarations, and use some hook to apply them—like e.g. setting
bodyelement (well, you really want to use
Please note that the best solution would mean to automatically transform a style sheet into its LTR or RTL counterpart. You should also assume a project to benefit from having all rules in the same style sheet for maintenance and ease-of-use. The arguably presentational ID name in the example is not a problem as the contents are presentationally fundamentally different.
Expect RTL issues with your favorite source editor. Yes. This doesn’t need to mean much yet, however my experience with bidirectional projects does know of a fine mess when it comes to appropriate source editors. My favorite one, IntelliJ, can’t fully handle RTL yet. vi improved support with version 7, as far as I know, but it’s far from being good. Textmate and Coda and stuff have problems with RTL contents. And others do, too, politely skipping at least 20 editors that I either tested myself or learned to screw up in one way or the other, too.
Since I cannot really operate software written in Hebrew or Arabic I usually try to use IntelliJ or vi regardless, or, as a last resort, FCKeditor. If you know a free tool with an English (or German) UI that can deal with both LTR and RTL, please ping me or leave a comment.
Don’t give up; enjoy. Working with international, LTR/RTL projects is a nice challenge that can twist your brain in fascinating ways. It’s also a great topic if you don’t have anything else to talk about. Just kidding. What was that all about.
Update (November 11, 2018)
A late note, work with RTL gets easier with CSS Logical Properties; these remove some former inherent directionality and with that make it possible to write style sheets that work with both LTR and RTL without special modifications.
I’m Jens Oliver Meiert, and I’m a web developer and author. I love trying things, including in the fields of philosophy, art, and adventure. Here on meiert.com I share some of my thoughts and experiences.
If you have any suggestions or questions about what I write, leave a comment or a message.
I tried to find the name editor a friend recommended to me a while ago…I failed badly. However, I remember I got it from the W3C Internationalization Website at http://www.w3.org/International/
Please update the post if you find a better editor than FCK. Thanks & Regards - Jonas
A few month ago my team was developing an arabic version of one of the sites of our customers. I can tell that the third rule (”Try to avoid a separate RTL style sheet”) wouldn’t work on this project because of its huge size. In our case the most comfortable, simple and quick way to make RTL were to make new (not actually new, but kind of exemplair like in OOP) templates and new CSS. Quiete dirty but very quick, stable and effective. It lowers cost a lot.
i think this is the first time i see someone (who is not an israeli or an arab) pointing out the problems with rtl documents and editors.
as a webdeveloper based in israel i get a lot of headaches dealing with support for rtl code and rendering.
the best editor for rtl i use is aptana, though in the osx version there are some problems (none in the windows version).
also notepad++ works quite well too.
notice that some browsers (notably opera) have box-model quirks when working in rtl, especially the padding calculation.
i’m glad i can tip in my 2NIS worth 😊
Hi, it’s not perfect either, but causes us the least problems: GEdit, even when used non-natively under Windows (even though we try to stick to Ubuntu wherever possible). Might want to give it a try.
Have a look at the most popular posts, possibly including:
Perhaps my most relevant book: CSS Optimization Basics (2018). Writing CSS is a craft. As craftspeople we strive to write high quality CSS. In CSS Optimization Basics I lay out the, at least some of the most important aspects of such CSS.
Looking for a way to comment? Comments have been disabled, unfortunately.