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 611948 - request fo translator comments, string fixes
request fo translator comments, string fixes
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
unspecified
Other Windows
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-05 22:32 UTC by Ivan Masár
Modified: 2010-10-21 13:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ivan Masár 2010-03-05 22:32:36 UTC
"Unrecognized desktop file Version '%s'"
Where is this string and what does it mean? Why is there capital V?

"Can't pass document URIs to a 'Type=Link' desktop entry"
How do I trigger this string and what does it mean?

" (invalid Unicode)"
please change to
" (invalid Unicode)"

"read", "create/delete", "zápis", "prístup"
add TC: used after "no "

consider using binary prefixes for sizes (ie. KiB, MiB, GiB)
Comment 1 A. Walton 2010-03-05 22:56:33 UTC
> "Unrecognized desktop file Version '%s'"
> Where is this string and what does it mean? Why is there capital V?
> 
> "Can't pass document URIs to a 'Type=Link' desktop entry"
> How do I trigger this string and what does it mean?

These two strings are internal strings to how libegg's 'eggdesktopfile.c' handles Desktop Entry Specification (".desktop") files, and I'm not exactly sure why they are marked for translation. I don't believe we actually ever display those errors anywhere in Nautilus, since we only depend on eggdesktopfile.c to make egg's session management client work. File against libegg?

> " (invalid Unicode)"
> please change to
> " (invalid Unicode)"
These two strings are identical...

> "read", "create/delete", "zápis", "prístup"
> add TC: used after "no "
More context please. "no read?" doesn't really make sense and I can't think of where we'd make that kind of error.
 
> consider using binary prefixes for sizes (ie. KiB, MiB, GiB)
Bug #554172. Most likely not going to happen as Alex (and me, and to be absolutely frank most everyone else in the world at this point) agree this is a bad idea.
Comment 2 Allan Day 2010-06-20 21:33:48 UTC
Changing status to needinfo.
Comment 3 Tobias Mueller 2010-10-21 13:42:28 UTC
Ivan, can you address the issues raised in comment #1 and reopen, please? Thanks in advance.