GNOME Bugzilla – Bug 682878
Don't include jargon in mount display names and messages
Last modified: 2012-08-30 18:54:42 UTC
We display implementation details of the mount in the user visible names. It would be better not to.
Created attachment 222634 [details] [review] Don't include jargon in mount display names and messages The backend protocol isn't necessary in the display name for a location. And having it there makes it much harder to actually find the user interesting part of the name. Once a mount is connected the user interesting part of the name is "what it is" and not "how it is accessed".
[Note that this would require announcement to gnome-i18n@. Also, string freeze starts on Monday.]
The display name is used for the ~/.gvfs/<subdir> name, changing this will break old filenames, as well as increasing the risk for conflicts there. We probably want to separate these two out and have a special fuse name set by the backend.
Created attachment 222968 [details] [review] Don't use the display name to make the unique mount point
Created attachment 222969 [details] [review] Don't include jargon in mount display names and messages The backend protocol isn't necessary in the display name for a location. And having it there makes it much harder to actually find the user interesting part of the name. Once a mount is connected the user interesting part of the name is "what it is" and not "how it is accessed". This is possible now that we aren't using the display name to make a unique mount point.
looks good to commit
Attachment 222968 [details] pushed as 3ef1deb - Don't use the display name to make the unique mount point Attachment 222969 [details] pushed as a198395 - Don't include jargon in mount display names and messages