Open MixMe opened 9 years ago
Thanks!
Also for "he-IL" and "fa-IR"
The language table needs an rtl column and probably needs a bom column. I have been working on this at a slow pace because my spare time is limited right now. I recently moved a copy of translatemanager into one of my apps and changed the namespaces in order to support rtl and bom the latest HTML5 way. I added a dir configuration parameter to my config files and will be adding a bom parameter for experimentation reasons. I plan to develop a behavior to dynamically change the parameters based on the current languagepicker choice. The W3C wants us to avoid using CSS to support RTL and move toward using HTML code instead. Theoretically, HTML5 can handle direction change for individual languages for an entire page based on the current dir and bdo settings. I have not reached the point yet where I can say it works. A bom column should handle the special handling required for the individual languages. If you do a W3C search for 'lang bom rtl', it should give you some insight. There is also a discussion about using pre and bom to prevent rtl changes when direction change should not occur. If those columns were added to the language table with a default of NULL, some experimentation is possible without moving the extensions out of vendor.
For "ar-AR" language, textarea must have: direction: rtl;