Bug 5781 - [RTL problems] Hebrew characters
Status: NEW
Alias: None
Product: Openbox
Classification: Unclassified
Component: general
Version: 3.4.11.2
Hardware: All Linux
: P3 critical
Assignee: Dana Jansens
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2012-10-19 03:19 EDT by khazarian
Modified: 2015-03-06 18:39:05 EST
4 users (show)

See Also:


Attachments
Several RTL problems (100.00 KB, application/x-gzip)
2012-10-19 03:19 EDT, khazarian

Description khazarian 2012-10-19 03:19:04 EDT
Created attachment 3287 [details]
Several RTL problems

I am testing a Hebrew translation for Openbox and I have found the following issues:

1) Truncated messages.
   See directory: truncate_text

2) Keystrokes look bad and are unusable.
   See directory: menu_alignment_underline

3) The default alignment (not justification) in menus and titles is LTR
   (Left-to-right) which sometimes cause to mixed Semitic (Arabic,
   Farsi, Hebrew) and Latin text to be in a messed order.
   See directory: title_alignment

   Due to a Unicode character RLE (U+202B), I assume, there is a
   difference between the window titles of Ekiga and Linphone.
   See text: ob_rtl_ekiga_vs_linphone_text.txt

   This character does not matter since Openbox should align everything
   from the right to the left automatically and if this would be done,
   the text will be in a correct order and there would not be a
   difference between the two window titles above.

I also tried: "*justify: right" in a themerc file without success.
See image: ob_rtl_bad_menu_aligenment+underline.png
Comment 1 khazarian 2012-10-25 15:23:03 EDT
I have added Mr. Karim Oulad Chalha and Mr. Khaled Hosny (Arabic translators) to this discussion.

Honorable Sirs,

Please add the word Arabic to title, in case you are experiencing a similar problem, and do participate in this bug report, if you may.

Thank you.
Comment 2 Paul G 2015-03-06 18:39:05 EST
Patch against mikachu-master to enable utf8 support for menu accelerators is in https://bugzilla.icculus.org/show_bug.cgi?id=6364 This may or may not solve the underline issue you reported, or may indeed introduce new ones. Could you test and update please, since I don't know an RTL language.

The latter is pertinent to the other issues you've reported. It's a bit difficult (for me at least) to discern what is wrong and what is right. I realize this is a bit tricky, but could you please try specifying expected behaviour vs current behaviour for these cases as best you can.