GNOME Bugzilla – Bug 438752
clipped text in about dialogue
Last modified: 2008-07-23 09:58:29 UTC
Testcase attached. Screenshot @ http://www.gnome.org/~chpe/images/wrap-justify-bug.png . Note the clipped text at the right "...foun[d]" and the misaligned centering of the text. glib/pango/gtk+ svn trunk.
Created attachment 88253 [details] testcase
*** Bug 469611 has been marked as a duplicate of this bug. ***
*** Bug 473816 has been marked as a duplicate of this bug. ***
*** Bug 507265 has been marked as a duplicate of this bug. ***
Note that this bug is highly annoying as the code is being distributed now in Fedora, Ubuntu, .... , and this means my applications about box is not fully readable. Please, increase the priority, or we need to look at using a different or custom about box. Also, this obviously should be put on confirmed, just open a gtk about box on eg Ubuntu Gutsy. Word wrapping the comment text with \n is no solution as the translators are not aware of the bug and cannot know why the linebreak is there. Furthermore, line breaks will be ugly once this is solved
Oeps, I just read the tip on meaning of unconfirmed, sorry, I am used to mantis bug tracker
I have the same issue under OpenSuse 10.3 (gtk 2.12) regards,
I think bug 508002 is causing this. Will fix that one tomorrow.
*** Bug 338149 has been marked as a duplicate of this bug. ***
Looking at the source of the about dialog I can see that gtk_label_set_justify() is called first and then gtk_label_set_line_wrap(). From the documentation of gtk_label_set_justify(): "gtk_label_set_justify() has no effect on labels containing only a single line." Could it be that this is caused by calling gtk_label_set_justify() on the single line and then afterwards splitting the line with gtk_label_set_line_wrap()? Perhaps reordering these two calls would fix this? (this is completely speculative...)
meh, disregard last comment. I got around to testing it (had to figure out to use ldconfig) and it does not fix the problem. Obviously. I just reread the code and my above comment is nonsense. Sorry for the spam... One extra comment: I filled the dupe (338149) for 2.8 so the bug was not introduced new in 2.12.
*** Bug 510025 has been marked as a duplicate of this bug. ***
Can someone please test that this is fixed with pango trunk?
I'd like to see what fixed this if any please. Is it #508002 ? This might be related to bug #508192 .
Yes, bug 508002 is what I fixed and I think should fix this. Bug 508192 might be related to this one, but I don't think the other way around.
Still reproducible with pango trunk.
Ah, guess I'm innocent then.
This is fixed on trunk. *** This bug has been marked as a duplicate of 530255 ***