GNOME Bugzilla – Bug 471701
gdict has an unlocalized license text.
Last modified: 2008-03-21 12:15:22 UTC
gdict has an unlocalized license text due to no gettext. I think it's better to have the localized text since other modules have done. To reproduce: 1. Invoke gdict. 2. Choose [Help] -> [About] and launch the about dialog. 3. Click [License] button and launch [License] dialog. Then the license text is not localized. I'm attaching the patch.
Created attachment 94592 [details] [review] Patch for gnome-dictionary/src/gdict-about.c Attached the patch. Could you review it?
this should be solved at gtk+ level - and there is a bug opened already (see bug 336225). also, licenses are not usually binding when translated, so I don't know whether this should be done or not. marking as duplicate of bug 336225 in the hope that this is solved at the right level of the stack. *** This bug has been marked as a duplicate of 336225 ***
The duplicating bug is dispatched. Is it possible to have the fix in gdict side?
(In reply to comment #3) > Is it possible to have the fix in gdict side? I really don't see the point; the proper fix is to resolve bug 336225. also, comment 37 on that bug (correctly) states that: Translations (of FSF licenses, at least) are always unofficial in any case, if we start translating every single license for every single application we'll get an explosion of size in the .mo files, which will impact on startup time.
The main problem is that gdict only does not provide the translations in GNOME so the problem visibility is high. If you compare other applications and consider the option again, it would be great. Comment 37 is right. Community translations always have the risk of translation qualities. Sun also has the different translations with legal reviews if we start the license translations. This bug introduce unlocalized text in gdict as other application fixes this issue. I agree it's better to fix bug 336225 but how about having the local fix until bug 336225 is fixed? I don't think this fix causes an explosion of size in the .mo files because the word counts are really small. I'm also working the l10n pakcaging and translations and I completely understand the way.