GNOME Bugzilla – Bug 388689
when xchat-gnome opens query on me, there is a lot of garbage from .po file on the top
Last modified: 2008-09-05 21:47:58 UTC
Please describe the problem: Whenever somebody sends me a query (when I open new query, it's OK), new window opens (so far so good), which has in the top a lot of information which looks like a top of .po file of my current locale (cs_CZ). Steps to reproduce: 1. let somebody send you a query 2. 3. Actual results: There is a lot of non-sensical stuff in the top of newly opened window. Expected results: Window should open clean. Does this happen every time? yes Other information:
Created attachment 78802 [details] illustration of described behavior
I can confirm this bug with fr_FR.UTF-8
This indicates that the return value of gettext("") is inserted.
This bug is since 0.14 (not in the 0.13)
I suspect this bug to come from a sync with xchat but, as i don't remember how to cleanly sync with last version, i can't test and see if a new sync would fix it. (BTW maybe we should write somewhere (wiki or in a file) how to sync)
Ubuntu bug https://beta.launchpad.net/ubuntu/+source/xchat-gnome/+bug/92564 the bug is due to src/common/text.c pevent_load_defaults () "pntevts_text[i] = strdup (_(te[i].def));" When a query is open there is a te[i].def = ""
Created attachment 84729 [details] [review] don't use gettext when not required
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Created attachment 85547 [details] [review] corrected patch The last patch is incorrect, as it causes no messages to be translated at all. The attached patch should fix this.
the changes have been reverted in svn with a sync on xchat, reopening
Created attachment 95957 [details] [review] new patch version
Very much present in xchat-gnome 0.18 on Fedora 8.
0.18 != development version. This *IS* fixed in svn.
*** Bug 478959 has been marked as a duplicate of this bug. ***
*** Bug 513400 has been marked as a duplicate of this bug. ***