Hi!

I am not sure this is a good idea. At least in its current state. The path which you get currently from WebDavFile can be used again as input in ls for example. However, if you add decoding on the way out you will have to add encoding on the way in. Otherwise you can not simply reuse the path that you get from the library to query the next sub folder. And it feels strange if the library handles decoding for you but you have to handle encoding yourself.

Also tests are missing and this would be a major bump in the version since it is breaking apps which handle en-/decoding already.

But maybe @jld3103 has another view on this. :)

@vauvenal5 I agree with your points