GNOME Bugzilla – Bug 572825
Fails to use translations
Last modified: 2009-02-25 23:32:56 UTC
Please describe the problem: Forwarding the bug reported downstream on Ubuntu -> https://bugs.launchpad.net/ubuntu/+source/conduit/+bug/333178 On the version included in Intrepid (0.3.14), the GUI appears completely untranslated, although translations are present. I have tested both the Catalan (ca) and German (de) locales with the same result, i.e. the UI always appears in English. Both locales have got a binary message catalog: /usr/share/locale/ca/LC_MESSAGES/conduit.mo /usr/share/locale/de/LC_MESSAGES/conduit.mo Steps to reproduce: Simply start conduit through the menu entry Applications -> Accessories -> Conduit Synchronizer Actual results: The UI appears in English Expected results: The UI is translated into the user's locale when the application has got a translation in that language Does this happen every time? Yes Other information:
Can you please install conduit-trunk svn snapshot from out ppa and see if it still occurs. I remember a bug like this being reported ages ago but cannot find the report. I think I remember it being fixed however. https://launchpad.net/~conduit/+archive/ppa
Created attachment 129308 [details] Screenshot of non-translatable messages Installing the conduit-trunk - 0.3.16~svn1896-intrepid1-1 ppa package solved the issue. However, there are still quite a few strings which appear untranslated, although the PO file is up to date. They do not seem to appear in the template, either, so they might have to be marked as translatable in the sources. Please find attached a screenshot which shows these non-translatable strings. * In addition to those, the File -> Examples menu entry and its sub-entries are also non-translatable
Thanks for testing. Trunk is undergoing a rather large change at the moment, however by the end of the week this should be near complete, and I can go ahead an mark many of these new strings for translation. *** This bug has been marked as a duplicate of 568442 ***
Just for the record, I have just found the original bug report, which was http://bugzilla.gnome.org/show_bug.cgi?id=532854 * John, could you please mark this one as a duplicate of 532854 instead of 568442? As the original report does not explicitly mention how this was resolved, I did not quite understand whether this was a bug in conduit or in the conduit packages for Fedora and Ubuntu.
*** This bug has been marked as a duplicate of 532854 ***
Again, just for the record I found the related commit -> http://svn.gnome.org/viewvc/conduit/trunk/configure.ac?r1=1713&r2=1737