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 704295 - Misleading error message in server connect dialogue
Misleading error message in server connect dialogue
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
3.8.x
Other All
: Normal trivial
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-07-15 21:13 UTC by Christian Kirbach
Modified: 2013-07-16 05:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix misleading error message in server connect dialogue (860 bytes, patch)
2013-07-15 21:13 UTC, Christian Kirbach 		committed Details | Review

Description Christian Kirbach 2013-07-15 21:13:10 UTC 
Created attachment 249244 [details] [review]
Fix misleading error message in server connect dialogue

#: ../src/nautilus-connect-server-dialog.c:149
msgid "Don't recognize this file server type."

This message is shown when the scheme (protocol?) is not known. It may be interpreted as a command or an option, but it probably needs to tell
"This file server type is not recognized."
Comment 1 Cosimo Cecchi 2013-07-15 21:47:43 UTC 
Review of attachment 249244 [details] [review]:

Thanks, looks good.
Comment 2 William Jon McCann 2013-07-15 22:28:00 UTC 
As a matter of historical record, that message was intentional. It was supposed to be a bit cute. But maybe it didn't work. The replacement is fine too - just a bit more boring. So, no objections.
Comment 3 Christian Kirbach 2013-07-16 05:50:41 UTC 
Comment on attachment 249244 [details] [review]
Fix misleading error message in server connect dialogue

[master 659a968] Clarify error message in connect server dialogue (Bug 704295)
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 4 Christian Kirbach 2013-07-16 05:52:10 UTC 
The issue is it confused translators, leading to a confusing translation