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 605237 - the "Antialiasing..." message in the progress bar does not show translated
the "Antialiasing..." message in the progress bar does not show translated
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Internationalisation
2.6.7
Other Windows
: Normal normal
: 2.6
Assigned To: GIMP Bugs
GIMP Bugs
: 609470 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-12-22 18:15 UTC by Cristian Secară
Modified: 2015-11-29 15:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cristian Secară 2009-12-22 18:15:03 UTC
On any image, click on Filters -> Enchance -> Antialias. While the action takes place, a progress bar appears at bottom, with a string that says "Antialiasing...". That string remains untranslated.

Tested with French and Romanian. I observed this merely because I am working on GIMP translation for Romanian and I do several operations just in order to check strings translation. In this version for my language there is no untranslated "Antialiasing..." string, in neither of the .po files (and the French translation is almost 100% complete).

Cristi
Comment 1 Sven Neumann 2009-12-23 23:00:10 UTC
That should fix it, applied in both branches:

commit e8ff034ab5d1556d93125ab59eec037691c28b3a
Author: Sven Neumann <sven@gimp.org>
Date:   Wed Dec 23 23:56:45 2009 +0100

    Bug 605237 -  the "Antialiasing..." message in the progress bar does not sho
    
    Add missing call to INIT_I18N().
Comment 2 Sven Neumann 2010-02-09 22:59:27 UTC
*** Bug 609470 has been marked as a duplicate of this bug. ***
Comment 3 Cristian Secară 2010-02-09 23:11:55 UTC
Sorry for duplication, I tried to display in "My Bugs" my own previously reported bugs, but I only found one (605540), probably because this one (and just a few others) was marked as resolved.

Sorry again,
Cristi