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 502756 - translation problems
translation problems
Status: RESOLVED FIXED
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other Linux
: Normal normal
: 1.2.5
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2007-12-10 00:02 UTC by André Klapper
Modified: 2007-12-13 00:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description André Klapper 2007-12-10 00:02:29 UTC
#: ../src/gnome-cmd-advrename-dialog.cc
do all those date and time format strings like "/Date/yyyy", "/Date/yyyy-mm-dd" or "/Time/HH.MM.SS" really need to be marked for translation?
the "Date"/"Time" part must be translated, sure, but i wonder whether it made sense to split the string, translate "Date" and "Time" once and leave the rest untranslated.


#: ../src/gnome-cmd-advrename-dialog.cc:629
"With this:"
translator comment required to translate this properly, like "Translators: this is part of »Replace this:« bla »With this:« bla"


#: ../src/gnome-cmd-advrename-dialog.cc:1123
"Dir"
#: ../src/gnome-cmd-con-dialog.cc:408
"_Remote dir:"
translator comment - in the sense of "Directory"?


#: ../src/gnome-cmd-file-selector.cc:1122
"List failed: %s\n"
translator comment - is "list" a verb here? listing of a directory failed, i assume?


#: ../src/gnome-cmd-user-actions.cc:1359
"You should have received a copy of the GNU General Public License along with 
GNOME Commander; if not, write to the Free Software Foundation, Inc., 59 
Temple Place, Suite 330, Boston, MA  02111-1307  USA"
FSF moved to another place, see http://www.mail-archive.com/debian-policy@lists.debian.org/msg19172.html


#: ../src/libgviewer/search-dlg.cc:343
"_Hex"
hexadecimal? if so, say so :)


lots of stuff in #: ../src/tags/gnome-cmd-tags.cc is *really* techy and needs translator comments. don't expect the translators to be specialists in MPEG encoding, please :)


#: ../src/tags/gnome-cmd-tags-taglib.cc:98
"CCIT J17"
what the...? does this really have to be marked for translation?


in #: ../src/tags/gnome-cmd-tags-doc.cc some language names have a _ prefix, some have a __ prefix. the ones with a __ do not show up in the po file.
Comment 1 epiotr 2007-12-10 19:17:21 UTC
> #: ../src/gnome-cmd-advrename-dialog.cc
> do all those date and time format strings like "/Date/yyyy", "/Date/yyyy-mm-dd"
> or "/Time/HH.MM.SS" really need to be marked for translation?
> the "Date"/"Time" part must be translated, sure, but i wonder whether it made
> sense to split the string, translate "Date" and "Time" once and leave the rest
> untranslated.

Yes, it's done on purpose. The strings define menu entries, and should be localized too. For example: "/Date/yyyy" is translated into Polish as "/Data/rrrr"...


> lots of stuff in #: ../src/tags/gnome-cmd-tags.cc is *really* techy and needs
> translator comments. don't expect the translators to be specialists in MPEG
> encoding, please :)

GNOME Commander is intended to present (and operate on) found metadata tags (see http://epiotr.rootnode.pl/gcmd/trunk/doc/C/figures/gnome-commander_dialog_file_metadata.png for an example). The myriads of MPEG tags and other ones - like Exif, IPTC, ID3, make it very difficult for translation, but their number and technical nature comes from the specifications (sigh)... Many of the translated Exif/IPTC strings can be found here: http://dev.robotbattle.com/~cvsuser/cgi-bin/ns_viewcvs.cgi/exiv2/trunk/po/


The rest of reported problems have been fixed in the latest svn repo, big thanks for spotting them.
Comment 2 André Klapper 2007-12-11 19:15:41 UTC
#: ../src/tags/gnome-cmd-tags-doc.cc:155
"Bahasa"
according to http://en.wikipedia.org/wiki/Bahasa,
"Bahasa is often incorrectly used in English to refer to Indonesian or Malay."

#: ../src/tags/gnome-cmd-tags.cc:392
"Titlesortorder"
#: ../src/tags/gnome-cmd-tags.cc:392
"Title sort order."
first one misses some whitespaces, i guess? same with "Syncedlyrics"?

why are there so many strings that only differ by having a punctuation mark at the end? is this really necessary? stuff like
{TAG_ID3_PUBLISHER, {"ID3.Publisher", TAG_ID3, N_("Publisher"), N_("Publisher.")}},
{TAG_ID3_REVERB, {"ID3.Reverb", TAG_ID3, N_("Reverb"), N_("Reverb.")}},
{TAG_ID3_SUBTITLE, {"ID3.Subtitle", TAG_ID3, N_("Subtitle"), N_("Subtitle.")}},
{TAG_ID3_TIME, {"ID3.Time", TAG_ID3, N_("Time"), N_("Time.")}},

also:
{TAG_EXIF_RELATEDIMAGELENGTH, {"Exif.RelatedImageLength", TAG_EXIF, N_("Related Image Length"), N_("Related Image Length.")}},
{TAG_EXIF_RELATEDIMAGEWIDTH, {"Exif.RelatedImageWidth", TAG_EXIF, N_("Related Image Width"), N_("Related Image Width.")}},

the capitalization is inconsistent. here both strings are totally capitalized, but there are many other strings where this is not the case.
Comment 3 André Klapper 2007-12-11 19:34:14 UTC
#: ../src/tags/gnome-cmd-tags.cc:249
do "IPTC/NAA" need to be marked for translation?

#: ../src/gnome-cmd-options-dialog.cc:211
<locale>
#: ../src/gnome-cmd-advrename-dialog.cc:174
/Time/<locale>
#: ../src/gnome-cmd-advrename-dialog.cc:162
/Date/<locale>
shall these remain untranslated (=use the "locale" setting on a linux system) or shall "locale" be translated?

> Yes, it's done on purpose. The strings define menu entries, and should 
> be localized too. For example: "/Date/yyyy" is translated into Polish 
> as "/Data/rrrr"...
hmm, rok, okay... sounds reasonible that some langs localize this :)
Comment 4 epiotr 2007-12-13 00:13:15 UTC
Fixed:

1. Bahasa -> Indonesian
2. Titlesortorder -> Title Sort Order
3. Syncedlyrics -> Synchronized Lyrics
4. Capitalization
5. IPTC/NAA

"/Date/<locale>"
could be translated as something alike:
"/Datum/Lokales Datumformat"