I tried running the current unity-2d on Lucid, and see how LTR support is today. I think that almost nothing have changes since I've opened this bug, except perhaps the order of the app indicators and the direction where their menus open, which is fine.
The app-indicators themselves are still aligned to the right, instead of to the left. The entire top panel should be mirrored.
As for the rest of the desktop it remains the same as in the maverick version. The sidebar is on the left instead of on the right, the menubar is aligned to the left, and the menus themselves open to the right, instead of to the left. You can compare it in the screenshot to Firefox, which does it right.
In the next attachment, I have a window maximized, and you can see how the window's close, minimize and maximize buttons are inconsistant between the windowed version and the top panel version.
There is also another unrelated RTL bug here, as the direction of the back and forward arrows in Nautilus aren't mirrored, but I don't think it belongs in this bug :)
Hi,
I tried running the current unity-2d on Lucid, and see how LTR support is today. I think that almost nothing have changes since I've opened this bug, except perhaps the order of the app indicators and the direction where their menus open, which is fine.
The app-indicators themselves are still aligned to the right, instead of to the left. The entire top panel should be mirrored.
As for the rest of the desktop it remains the same as in the maverick version. The sidebar is on the left instead of on the right, the menubar is aligned to the left, and the menus themselves open to the right, instead of to the left. You can compare it in the screenshot to Firefox, which does it right.
In the next attachment, I have a window maximized, and you can see how the window's close, minimize and maximize buttons are inconsistant between the windowed version and the top panel version.
There is also another unrelated RTL bug here, as the direction of the back and forward arrows in Nautilus aren't mirrored, but I don't think it belongs in this bug :)