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 273098 - Avoid very long column header message in Evolution csv plugin
Avoid very long column header message in Evolution csv plugin
Status: RESOLVED DUPLICATE of bug 273099
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: JP Rosevear
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-02-27 23:04 UTC by Christian Rose
Modified: 2005-02-28 16:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch that will remove the possibility to translate this (1015 bytes, patch)
2005-02-28 09:46 UTC, Philip Van Hoof
none Details | Review

Description Christian Rose 2005-02-27 23:04:35 UTC
#: plugins/save-calendar/csv-format.c:370
#, c-format
msgid ""
"Uid%sSummary%sDescription List%sCategories List%sComment List%sCompleted%"
"sCreated%sContact List%sStart%sEnd%sDue%sPercent Done%sPriority%sUrl%"
"sAttendees List%sLocation%sModified%s"

Please do not concatenate long messages like this -- it makes it very
difficult to translate and later find changes in the string.
Instead, split the code up so that every single column header is in its own
gettext call.
Comment 1 Christian Rose 2005-02-27 23:14:35 UTC
Pleae note though that GNOME is currently in string freeze.
Comment 2 Philip Van Hoof 2005-02-28 09:46:24 UTC
Created attachment 44901 [details] [review]
Patch that will remove the possibility to translate this
Comment 3 Philip Van Hoof 2005-02-28 09:47:04 UTC
I'm not sure whether or not it should be translatable. Translating
this will have an impact on the file thats being written. It's not a
userinterface-translation.
Comment 4 Christian Rose 2005-02-28 10:45:32 UTC
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.
Comment 5 Danilo Segan 2005-02-28 13:38:21 UTC
The criteria should be: how is the generated CSV file used. If I'm
supposed to import it in eg. Gnumeric, then it should probably be
translated.  Or, if I'm supposed to share it with my friends, it
should probably be translated. Also, if those labels are there to help
human readers, then they should be translated.

OTOH, if it's used in a solely technical matter (eg. exporting from
Evo and importing it back), then it's up to evo designers to decide on
that. 
Comment 6 Philip Van Hoof 2005-02-28 14:04:35 UTC
I can easily imagine myself wanting to create a CSV and sending it to
a friend of mine, who isn't speaking the same language or who hasn't
set his language-preferences tot he same language as I have. 

CSV files are mainly for both reading and using it for
import/exporting purposes.

The Header-line shouldn't be used for importing/exporting by
applications that will use such a file for that purpose. But many such
applications (like openoffice and gnumeric) do have a import-preview
tool that will show what column will be assigned to which
data-structure in the application. I'm guessing its mainly for that
purpose that it's being used (the header-line).

I, personally, would keep it in English only.


Comment 7 Philip Van Hoof 2005-02-28 16:33:20 UTC
This bug will be fixed by the patch of bug 273099. Therefor marking it
as a dup.

*** This bug has been marked as a duplicate of 273099 ***