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 520064 - L10N: error on POT string '% Complete'
L10N: error on POT string '% Complete'
Status: RESOLVED FIXED
Product: planner
Classification: Other
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2008-03-03 10:04 UTC by dooteo
Modified: 2008-03-04 02:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Adds descriptive comment and sets string to no-c-format (626 bytes, patch)
2008-03-03 18:55 UTC, Maurice van der Pot 		none Details | Review

Description dooteo 2008-03-03 10:04:33 UTC 
Please describe the problem:
Hi,

I think next message should _not_ be c-format
#: ../src/planner-task-view.c:344
#, c-format
msgid "% Complete"
msgstr "% amaituta"

Because running msgfmt gives me next error:

eu.po:2035: format specifications in 'msgid' and 'msgstr' for argument 1 are not the same

It is expecting a 'C' character after '% ', so in languages a Spanish does not give errors, '% Completado', but gives errors on other languages.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 dooteo 2008-03-03 10:05:44 UTC 
So can you change string type to no-c-format?

Thanks
Comment 2 André Klapper 2008-03-03 10:28:04 UTC 
this is a broken string from my POV. it's should be "%d%% complete".
Comment 3 Maurice van der Pot 2008-03-03 18:55:39 UTC 
Created attachment 106503 [details] [review]
Adds descriptive comment and sets string to no-c-format

How about this one?

Kurt, will you commit this if it's acceptable?
Comment 4 Kurt Maute 2008-03-04 02:40:40 UTC 
ok, I committed this, and I'm marking it as fixed.

If there's still a problem with L10N, please reopen this bug and we'll work on it some more.

tnx!