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 615639 - L10N: string "Authentication method to host %s is unsupported. (%u)"
L10N: string "Authentication method to host %s is unsupported. (%u)"
Status: RESOLVED FIXED
Product: vinagre
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: vinagre-maint
vinagre-maint
Depends on:
Blocks:
 
 
Reported: 2010-04-13 12:26 UTC by Roman Matyus
Modified: 2010-06-05 14:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Roman Matyus 2010-04-13 12:26:47 UTC 
msgid "Authentication method to host %s is unsupported. (%u)"

Which means "to host"?
Comment 1 André Klapper 2010-04-16 14:28:27 UTC 
Here it's probably http://en.wikipedia.org/wiki/Host_%28network%29
Comment 2 Marcel Telka 2010-04-19 22:02:29 UTC 
I think there is missing something like "for access" between "method" and "to" making the following sentence: "Authentication method for access to host %s is unsupported. (%u)"

Or, there should be simpler: "Authentication method for host %s is unsupported. (%u)"

How can we have an "Authentication method" "to" something? Thanks.
Comment 3 Jonh Wendell 2010-04-28 00:06:12 UTC 
Thanks for the tip, I'm not good at English as I would like :)

Anyway we are in string freeze for 2.30, and this is not so urgent that deserves a break. So, I'll put a comment for now and will fix this in 2.31.
Comment 4 Marcel Telka 2010-04-28 05:47:44 UTC 
John, thanks for working on this (and other L10N bugs too).

While scanning the messages I found that this one maybe needs similar love, but I am not sure...

#: ../vinagre/vinagre-notebook.c:482
#, c-format
msgid "Authentication to host %s has failed"
msgstr ""
Comment 5 Jonh Wendell 2010-06-05 14:55:31 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.