After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 675601 - GIMP 2.8 dropped translation coverage compared to 2.6
GIMP 2.8 dropped translation coverage compared to 2.6
Status: RESOLVED NOTABUG
Product: GIMP
Classification: Other
Component: Internationalisation
2.8.0
Other All
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 676089 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-05-07 10:53 UTC by lokster
Modified: 2012-09-10 10:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
missing parts of Dutch translation in GIMP 2.8 (25.96 KB, image/png)
2012-05-15 07:54 UTC, Leendert V
Details
semitranslated gimp 2.8 (616.28 KB, image/png)
2012-07-09 09:27 UTC, Tamás
Details

Description lokster 2012-05-07 10:53:59 UTC
When I run GIMP 2.8 with bulgarian locale, most of the menus show in english.
The same strings show OK in bulgarian with previous versions.
I have checked several of the strings in the source, and found that these strings exist in the .po file and are translated.
The problem exist on Linux (Kubuntu 12.04) and Windows (XP).
Comment 1 svetlisashkov 2012-05-08 08:06:40 UTC
I can confirm the same bug.
Comment 2 Leendert V 2012-05-15 07:54:23 UTC
Created attachment 214064 [details]
missing parts of Dutch translation in GIMP 2.8
Comment 3 Leendert V 2012-05-15 07:55:34 UTC
The same bug with the Dutch translation!

Very annoying for the readers of our Dutch GIMP tutorials!
Comment 5 André Klapper 2012-05-15 15:38:44 UTC
*** Bug 676089 has been marked as a duplicate of this bug. ***
Comment 6 Alexandre Prokoudine 2012-05-15 16:43:59 UTC
Here is an example from the po/nl.po:

#: ../app/actions/image-actions.c:57
#, fuzzy
msgctxt "image-action"
msgid "_Transform"
msgstr "_Transformeren"

It's the same in Bulgarian:

#: ../app/actions/image-actions.c:57
#, fuzzy
msgctxt "image-action"
msgid "_Transform"
msgstr "П_реобразуване"

The "fuzzy" bit means that the translatable text changed in the original English version, but noone update the translation to match the change.

Folks, Bulgarian translation was last updated in frigging 2007, and the Ducth one - in 2008! What did you expect? :)

Please just start updating your translations.
Comment 7 Leendert V 2012-05-15 18:24:05 UTC
Thank you Alexandre (also for your help on IRC)!

The problem is clear!
Not a bug in GIMP but outdated translations.
Comment 8 lokster 2012-05-15 21:23:56 UTC
@Alexandre Prokoudine, as far as I know, GIMP is actively translated in Bulgarian on Launchpad.
Comment 9 André Klapper 2012-05-16 10:45:12 UTC
> Not a bug in GIMP but outdated translations.

That is not correct. See comment 4.

@lokster: 
Launchpad has nothing to do with GNOME, but if the Launchpad team upstreamed their translations to the GNOME translation team for review and inclusion in GNOME that would be very welcome. See http://l10n.gnome.org/languages/bg/ for contact info.
Comment 10 Michael Schumacher 2012-05-17 15:37:43 UTC
Not sure what to do with this bug - I don't think that its mere existence will make the translation teams notice that there is a problem, right?
Comment 11 Tamás 2012-07-09 09:27:06 UTC
Created attachment 218320 [details]
semitranslated gimp 2.8
Comment 12 Tamás 2012-07-09 09:28:40 UTC
The bug is present in Mageia 2 and cauldron, in Hungarian language too. Translation file has the right records, so this problem is not with the translation itself.
Comment 13 Alexandre Prokoudine 2012-07-09 09:38:04 UTC
Actually, it IS the problem with the Hungarian translation.

Please have a look yourself:

http://git.gnome.org/browse/gimp/log/po/hu.po?h=gimp-2-8

Unless Mageia 2 somehow has 3 days old translation updates from the 2.8 Git branch, you are dealing with translation that was last updated in 2008.
Comment 14 Claude Paroz 2012-09-10 10:00:26 UTC
Closing, as this is a translation workflow issue, not a Gimp one.