GNOME Bugzilla – Bug 273099
Please provide translator comment for Evolution csv plugin message
Last modified: 2009-08-03 15:23:42 UTC
#: plugins/save-calendar/csv-format.c:167 #, c-format msgid "%s%d/%s%d/%s%d %s%d:%s%d:%s%d" Please provide a translator comment for this message, explaining how its used and what kind of values get filled in at the various %s and &d:s. As the message is right now, it is very difficult for a translator to know how to translate this or if he needs to translate it at all.
After looking at the code, this piece of code seems entirely broken from a localization point of view. Why not just use strftime() and a format string of "%x %X" instead?
Please note though that GNOME is currently in string freeze.
Created attachment 44900 [details] [review] patch v1
I'm cc:ing Danilo to see if he thinks this should be translateable or not. To clarify, if you decide to only remove the message from translation, you would not need string freeze approval. Removing is fine from a string freeze point of view.
This all looks very strange. If it should not be translated (I don't know how are generated CSV files used), and if it's not mandated by some specification, I suggest to make the date format YYYY-MM-DD instead (which is universally understood, whereas MM/DD/YYYY will most likely be misunderstood in Europe, at least). Also, why not use "%02d" instead of those hacks there?
Created attachment 44902 [details] [review] What about this one
Created attachment 44903 [details] [review] And without the tiny memoryleak :)
Created attachment 44904 [details] [review] And yet another tiny mistake corrected
*** bug 273098 has been marked as a duplicate of this bug. ***
adding dependency, adding "patch" keyword
Fixed in CVS
FYI: http://cvs.gnome.org/viewcvs/evolution/plugins/save-calendar/csv-format.c?r1=text&tr1=1.3&r2=text&tr2=1.4&diff_format=h
Created attachment 44923 [details] [review] Solves both #73099 and $7398
Hasn't evo already branched for gnome-2-10? I.e. you don't need approval for HEAD, only for gnome-2-10 (and it's not important enough to warrant a string freeze break this late).
Reopening until it gets fixed in at least HEAD.
philip, danilo, can this be closed now according to 2.3.2 release notes it should be in.
Indeed
Comment on attachment 44900 [details] [review] patch v1 Original description was too long for the soon-to-be-upgraded Bugzilla.