The multilingual/translation support is integrated with the WYSIWYG feature in a way that if you are working in an English interface, the text direction in CKEditor remains LTR even when the page being edited is defined as being in Hebrew, which is RTL. I expect that this applies to any other RTL language.
Similarly, it seems to me (though I haven't tested it thoroughly) that a user working in a Hebrew interface would get RTL behaviour in CKEditor even when editing an English page.
I can only assume that use of the English-language interface for editing Arabic pages and Arabic-language interface for English pages is common, as such combinations are certainly common where Hebrew is involved. The forcing of direction according to interface language rather than page language is likely to be a significant annoyance in all such cases.
The ideal solution would be to make the editor direction dependent on the page language's direction, and only according to the user's language if there is no page language set (there is a CKEditor option which does that - see http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html#.contentsLangDirection)
A simplistic hack was added to force the direction to 'ltr' for 'en' page language and 'rtl' for 'he' page language and only if neither of these is matched, to go by the standard logic.
contentsLangDirection: "' . ($prefs['feature_bidi'] === 'y' ? 'rtl' : 'ltr') . '"
'. ( !empty($smarty->_tpl_vars['lang']) ? 'contentsLanguage: "' . $smarty->_tpl_vars['lang'] . '",' : '') . ' contentsLangDirection: "' . ( $smarty->_tpl_vars['lang'] === 'he' ? 'rtl' : ( $smarty->_tpl_vars['lang'] === 'en' ? 'ltr' : ($prefs['feature_bidi'] === 'y' ? 'rtl' : 'ltr') ) ) . '"
For general use it would make more sense to have a "RTL" flag in the language list and refer to that when setting contentsLangDirection, falling back on the "ui" setting for direction when no page language is defined.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
Unable to connect to show.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |