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 524278 - CIFS location translation
CIFS location translation
Status: RESOLVED DUPLICATE of bug 498195
Product: evolution
Classification: Applications
Component: Mailer
2.12.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-03-25 11:19 UTC by matip
Modified: 2012-01-20 10:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description matip 2008-03-25 11:19:07 UTC 
CIFS location translation.

Very often people send links to documents on windows shares like :
\\server\share\folder\folder2\file.ext

It would be great it Evolution would translate that to something like 
smb://server/share/folder/folder2/file.ext and open that in a nautilus window. 


It would be good that if we could have a simple link translator as a module or as an option.




Distribution: openSUSE 10.3 (i586)
Gnome Release: 2.20.0 2007-09-22 (SUSE)
BugBuddy Version: 2.20.1
Comment 1 André Klapper 2008-03-25 12:20:35 UTC 
probably a gio integration issue
Comment 2 Oded Arbel 2008-09-28 10:12:52 UTC 
Currently evo "translates" links in the form \\server\share\document to file://\\server\share\document which is not the best.

We can get gio to understand "standard" windows shares links, and that would also mean getting evo to stop the above translation, but I think it would be much easier to get evo to simply translate the links to the smb:// form by simply appending "smb:" to the start of the link and change all back-slashes to forward slashes
Comment 3 Joel Goguen 2009-03-18 16:39:35 UTC 
Is this maybe a duplicate of bug 498195?
Comment 4 Oded Arbel 2009-03-18 18:24:27 UTC 
looks like it
Comment 5 André Klapper 2012-01-20 10:08:35 UTC 

*** This bug has been marked as a duplicate of bug 498195 ***