home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Feature Requests
Adding support for Right-to-left languages (Hebrew, Arabic...)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="velis" data-source="post: 1105849" data-attributes="member: 96429"><p>I have a bit of experience with farsi in my Android app:</p><p>Generally, RTL users *prefer* everything to be mirrored, but they are used to western layouts and don't complain about them too much. My farsi translator told me multiple times that I needn't bother that much, but was still quite happy that I went so far as to mirror the entire app.</p><p></p><p>In my experience, straight mirror will usually do it (also relatively easy to support in rendering engine), but there may be cases where that's not a good solution. I have no idea what such cases might be, but Google specifically mentions that they don't want to do the straight mirror because it might break something. My guess is that if there was something to break, it would be the developer's LTR assumption and manual layout of components in LTR order. Mirroring certain component combinations might then prove to be a bad idea, but not much worse than not mirroring at all.</p><p></p><p>As for string reversing: don't do it!!! Even in RTL languages, there are expressions / acronyms / formulas / whatever that are written in a western-like script. The default Windows API should normally take care of proper string rendering, as long as you use a font that has the required language characters.</p><p></p><p>Personally, I think there needs to be one more item observed: current layout engine only supports fixed coordinates. The problem is that some languages require more space to say the same thing than others. So in my translation of MP, I have noticed repeatedly that my translation would be cut off because there simply was no translation short enough. In other places though, there was too much space left because slovene translation was much shorter than english original. This is perhaps unrelated, but essentially it has the same roots as RTL support.</p><p></p><p>Oh, and BTW: some languages have different glyphs for numerals (0 - 9). They are also in different unicode code ranges. Just a heads-up for all those %d sprintfs <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>About FreeType rendering issues: <a href="http://stackoverflow.com/questions/6431624/freetype-support-for-right-to-left-languages" target="_blank">http://stackoverflow.com/questions/6431624/freetype-support-for-right-to-left-languages</a> (there's a layout lib mentioned there)</p></blockquote><p></p>
[QUOTE="velis, post: 1105849, member: 96429"] I have a bit of experience with farsi in my Android app: Generally, RTL users *prefer* everything to be mirrored, but they are used to western layouts and don't complain about them too much. My farsi translator told me multiple times that I needn't bother that much, but was still quite happy that I went so far as to mirror the entire app. In my experience, straight mirror will usually do it (also relatively easy to support in rendering engine), but there may be cases where that's not a good solution. I have no idea what such cases might be, but Google specifically mentions that they don't want to do the straight mirror because it might break something. My guess is that if there was something to break, it would be the developer's LTR assumption and manual layout of components in LTR order. Mirroring certain component combinations might then prove to be a bad idea, but not much worse than not mirroring at all. As for string reversing: don't do it!!! Even in RTL languages, there are expressions / acronyms / formulas / whatever that are written in a western-like script. The default Windows API should normally take care of proper string rendering, as long as you use a font that has the required language characters. Personally, I think there needs to be one more item observed: current layout engine only supports fixed coordinates. The problem is that some languages require more space to say the same thing than others. So in my translation of MP, I have noticed repeatedly that my translation would be cut off because there simply was no translation short enough. In other places though, there was too much space left because slovene translation was much shorter than english original. This is perhaps unrelated, but essentially it has the same roots as RTL support. Oh, and BTW: some languages have different glyphs for numerals (0 - 9). They are also in different unicode code ranges. Just a heads-up for all those %d sprintfs :) About FreeType rendering issues: [url]http://stackoverflow.com/questions/6431624/freetype-support-for-right-to-left-languages[/url] (there's a layout lib mentioned there) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Feature Requests
Adding support for Right-to-left languages (Hebrew, Arabic...)
Contact us
RSS
Top
Bottom
