Created attachment 64317 [details]
odb database linked to mapped network share, using an ods as source

Problem description: 

If you create a new database using the assistant under windows build.
and use network map letter ( for example N:\blabla\sources\ods\mysources.ods ) as source for the odb (saved at the same place)
you will be unable to edit the database properties 

Inside the odb content.xml a work only one time path is registered like

db:file-based-database xlink:href="file:
///N:/Correspondance/Communes/Géomètre%20conservateur/2013-2017/Décisions/Remerciements/Communes.ods/" db:media-type="application/vnd.oasis.opendocument.spreadsheet"


Steps to reproduce:
(Warning : long story, extract from real life!)

1. Install 3.5.5 Loo windows version under Windows (was 7 64bits here)
2. Connect one or several remote cifs server to letter
3. Create a kind of mailing ods (like name,firstname,birthday,bla informations with data) this will be used as source
And place it to a complex path on a mapped network letter
4. Use Mailing assistant to create a new database, search your source ods call the db whatever
5. Save the odb in the same folder of the ods.
5. You will be able to create a mailing.
6. Now a friend need those odb and ods under his linux, or you send them grouped in a zip file by email. (You can emulate that by simply moving the 2 files in a new location on the network.
7. You want to use the odb, open it, and try to change the location of the ods, menu edit database properties : the field is grayed and you can't change anything. The path is still the old one.

8. This become a hack, your partner extract the content.xml and use ../bla.ods as url for the file. And save it again in the .odb
9. Your partner is able to work with the odb, and best he can move it to new location, and the ods,odb coupling stay working.
10. Your partner send the odb,ods back to you. You place it on the mapped network path, and the best is, now you can also work with, and can even move it inside your infrastructure freely, as you should have been able from the start :-)


Current behavior:
The full network mapped file is registered by windows even if odb and its source are in the same directory. Worst it seems that the url decoder is then unable to treat the second semi-colon in the url, and then the UI doesn't allow the user to change it.


Expected behavior:
if a source is located in the same directory as the odb, apply the same principle on windows than on Linux and use ../mysource.ods scheme.
Benefit : LibreOffice end users will be able to use cross-platform office suite.

Platform (if different from the browser): 
All : an odb has to be able to abstract the way file path work and never use a fixed one. If allowed, also permit UI to allow relative path so a Windows Network share can correspond to a nfs share.
    
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0