Arabic "RTL" GUI minor issues

• Oct 2, 2016 - 13:22
Reported version
2.1
Type
Graphical (UI)
Severity
S4 - Minor
Status
closed
Project

Hi
I am on Windows 7 Home Premium.

I am attaching few images showing few issues regarding the Arabic translation.
Please start with the file (Arabic_GUI.pdf), mostly a RTL issue.

For arrows, arrow icons just need to swapped whenever language is either Arabic or Hebrew.

For buttons I think the issue has something to do with the style since even a single Arabic word "eg. message_box.png" (Ignore button) got chopped both sides (4-5 pixels) yet still enough margin exist, perhaps you can solve this all at once by allowing an option (reverting back to Qt native style) i.e. not to use any skin.

For Arabic text, am not quite sure, but am certain Arabic strings aren't too long, I tried making them shorter to no success, "transpose.png" strings are flushed far to the right hitting the embossed frame.

In "inspector.png" strings are chopped at the left end yet there seem extra space available in the spinners they can push.

In "palettes.png" the tooltip string is also chopped at the left end yet tooltips are flexible to room more than 4 word string.
Perhaps something to do with style.

Attachment Size
Arabic_GUI.pdf 65.15 KB
inspector.png 17.26 KB
main_menu.png 9.56 KB
measure_properties.png 16.63 KB
message_box.png 5.15 KB
palettes.png 24.22 KB
plugin_creator.png 11.67 KB
score_properties.png 7.02 KB
start center.png 28.15 KB
style_edit.png 14.53 KB
transpose.png 9.18 KB

Comments

Could someone verify if the new Fusion theme would solve the problem with the strings being chopped?

For the arrow icons, a simple fix would be to test the layout direction of the application when creating the buttons and create them in reverse order for right to left. In this case, Qt will reverse them again, and they would look good. It will be a bit more involved to make this happen dynamically when changing language...

verify if the new Fusion theme would solve the problem means to be using a recent nighly build, which also means that not all translated strings would be working (the majority still do though)

Then RTL (Arabic/Hebrew) should layout fine, perhaps some tweaks will solve the issue.

I would suggest adding some checkbox/comboBox in Preferences to enable current Musescore style otherwise default to Qt Fusion or any other native or future coming styles/skins.

It seems that with the new Fusion style the behavior is better.
Attached two examples with the old Light style on top and the new Light Fusion style at the bottom for the same build ( 185f329 i.e. the "truncated" behavior should be present also in Nightly builds).
But I did not verify all the cases listed in the first post.

Attachment Size
fusion_diff.png 10.98 KB
fusion_diff_editstyle.png 6.57 KB

I would suggest adding some checkbox/comboBox in Preferences to enable current Musescore style otherwise default to Qt Fusion or any other native or future coming styles/skins.

The current plan is to default to Qt Fusion indeed and get rid of the current style. We don't use any native styles because it's a pain to support in the long run. You can read more about it here https://musescore.org/en/node/126606

Here are the equivalent of palettes.png and inspector.png for the Light style (left) and Fusion Light (right). It seems that the bug is already solved also for the Light style, maybe due to the switch to Qt5.6.
[Same built of the previous post, Windows 10]

Attachment Size
diff1.png 19.18 KB
diff2.png 21.92 KB