Fallback to Unity 2D for RTL locales
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
Invalid
|
Undecided
|
Unassigned | ||
| Nux |
Won't Fix
|
Undecided
|
Unassigned | ||
| Ubuntu Translations |
Won't Fix
|
Medium
|
Unassigned | ||
| Unity |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Dear Friends,
Since Unity and Nux don't yet support RTL (Bug #654988) then until that support is released, Unity should fall back to Unity 2D, which does support RTL.
A branch for Nux, was written for this purpose and a merge was proposed. Please make freeze exception.
The rationale is that RTL users will get mighty confused because their shell is LTR while the rest of their apps are RTL.
It would be better to have a "boring", no bling shell than to have an LTR shell in a RTL language.
Test packages are available in the following PPA:
https:/
In order to test:
1. See that when user's language is one of the RTL languages (Hebrew, Arabic, Farsi, etc.) that a Unity session is replaced by a Unity 2D session.
2. See that this can be circumvented by setting the UNITY_ALLOW_RTL variable (I do it in .profile).
3. See that LTR locales sessions are not affected by this.
Thanks and Blessings,
Shahar
Related branches
| tags: | added: precise rtl |
| summary: |
- Fall back to Unity 2D for RTL locales + Fallback to Unity 2D for RTL locales |
| Changed in ubuntu-translations: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in nux: | |
| status: | New → Incomplete |
| Changed in unity: | |
| status: | New → Incomplete |
| Changed in nux: | |
| status: | Incomplete → New |
| Changed in unity: | |
| status: | Incomplete → New |
| Bilal Akhtar (bilalakhtar) wrote | #1 |
| Changed in unity: | |
| status: | New → Incomplete |
| Changed in nux: | |
| status: | New → Incomplete |
| Shahar Or (mightyiam) wrote | #2 |
| description: | updated |
| Changed in nux: | |
| status: | Incomplete → New |
| Changed in unity: | |
| status: | Incomplete → Invalid |
| status: | Invalid → New |
| Changed in ubuntu-translations: | |
| status: | Triaged → New |
| Martin Pitt (pitti) wrote | #3 |
| Changed in unity: | |
| status: | New → Confirmed |
| Haggai Eran (haggai-eran) wrote | #4 |
| Changed in ubuntu-translations: | |
| status: | New → Triaged |
| Shahar Or (mightyiam) wrote | #5 |
| Omer Akram (om26er) wrote | #6 |
| Changed in unity: | |
| status: | Confirmed → Won't Fix |
| Changed in nux: | |
| status: | New → Won't Fix |
| Changed in ubuntu-translations: | |
| status: | Triaged → Won't Fix |
| Changed in ayatana-design: | |
| status: | New → Invalid |
So, is this meant to be a freeze exception bug? Then for that, could you follow the steps here: https:/
If that's the case, then this shouldn't be assigned to Ayatana Design either.