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 595087 - 4 strings need explanation/translator comments
4 strings need explanation/translator comments
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: general
git master
Other All
: Normal trivial
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-09-13 17:54 UTC by Christian Kirbach
Modified: 2012-08-23 09:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch addressing all translation issues of this bug (2.83 KB, patch)
2012-08-01 18:16 UTC, Felix Möller 		committed Details | Review

Description Christian Kirbach 2009-09-13 17:54:23 UTC 
at least 4 strings need modifications or explanations , i.e. translator comments.
How can a file be started or stopped? :)
What is an etag?


#: ../daemon/gvfsbackendcomputer.c:1252 ../daemon/gvfsbackendcomputer.c:1259
msgid "Can't start file"


#: ../daemon/gvfsbackendcomputer.c:1325 ../daemon/gvfsbackendcomputer.c:1332
msgid "Can't stop file"


#: ../programs/gvfs-save.c:47
msgid "Print new etag at end"


#: ../programs/gvfs-save.c:48
msgid "The etag of the file being overwritten"
Comment 1 Ihar Hrachyshka 2012-02-15 19:24:12 UTC 
Still valid. Any comments/fix?
Comment 2 Felix Möller 2012-07-30 07:39:49 UTC 
(In reply to comment #0)
> at least 4 strings need modifications or explanations , i.e. translator
> comments.
> How can a file be started or stopped? :)
> What is an etag?
> 
> #: ../daemon/gvfsbackendcomputer.c:1252 ../daemon/gvfsbackendcomputer.c:1259
> msgid "Can't start file"
> 
> #: ../daemon/gvfsbackendcomputer.c:1325 ../daemon/gvfsbackendcomputer.c:1332
> msgid "Can't stop file"
Both of them have been introduced with commit 4053577a19585c63e23e6c6e85011e2df9910745 .

For an explanation see bug #531437.

> #: ../programs/gvfs-save.c:47
> msgid "Print new etag at end"
> 
> #: ../programs/gvfs-save.c:48
> msgid "The etag of the file being overwritten"
The ETag seems to come from http://developer.gnome.org/gio/stable/GFileOutputStream.html#g-file-output-stream-get-etag. The long form is entity tag.

More information can be found at:
https://mail.gnome.org/archives/gtk-devel-list/2007-September/msg00054.html

 Etags are
 similar to etags in http, and mtime tags in local files. You pass in 
 one you got when reading or writing the file last time and if the file
 on disk differs from the passed in tag you get an error. 
 (I notice here that the helper API sucks, because you can't get the new
  etag when writing a file, or when reading a file.)

Can somebody create the translators comments now?
Comment 3 Felix Möller 2012-07-31 11:37:39 UTC 
(In reply to comment #2)
> (In reply to comment #0) 
> > #: ../daemon/gvfsbackendcomputer.c:1325 ../daemon/gvfsbackendcomputer.c:1332
> > msgid "Can't stop file"
> Both of them have been introduced with commit
> 4053577a19585c63e23e6c6e85011e2df9910745 .
> 
> For an explanation see bug #531437.

Sorry, I pasted the wrong number. It is bug #585591.
Comment 4 Felix Möller 2012-08-01 18:16:57 UTC 
Created attachment 220088 [details] [review]
patch addressing all translation issues of this bug

Reading bug #531437 file is a way better translation than drive thus changing it. I think no translator comment is needed for that anymore.

Adding translator comments to the etag.

Please review and apply.
Comment 5 Christian Kirbach 2012-08-09 19:11:07 UTC 
Review of attachment 220088 [details] [review]:

Looks good to me