[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: patch-needswork
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770038
Title:
greeter screen on rtl langs don't show well
--
ubuntu-bugs mailing list
just compare the two screenshots, i read the remarks in the file, but as
i tested it on my machine - the process_labels function makes rtl
languages to be shown partly under the languages list .
** Attachment added: without process_labels
because the browser can't handle xcf pictures.
** Attachment added: proper.png
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/770038/+attachment/2093498/+files/proper.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm afraid I am unable to read right-to-left languages. Can you please
elaborate on the exact problem you're experiencing?
On the point of commenting out the process_labels function, it is
necessary to work around a longstanding issue in GTK+ whereby it cannot
properly wrap text in labels.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770038
Title:
greeter screen on rtl langs don't show well
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: screenshot
https://bugs.launchpad.net/bugs/770038/+attachment/2087129/+files/screen1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770038
Title:
greeter screen on rtl
I found a solution, in file /ubiquity/frontend/gtk_ui.py I commented lines
310-311,
for w in mod.all_widgets:
process_labels(w)
in method Wizard. __init__
probably it was a problem in older versions of some libraries and the solution
for them is now obsolete.
attached patch.
**
