>> Yes, it also needs to encode other characters as well. >> >> The current version not only chokes on spaces >> but also on german umlauts like (�,�,�) and >> probably more. >> > > Yes - and now it gets even worse. How do the static URIUtil.encodePath > know which encoding should be used? > Even if UTF-8 is the defacto standard we finally need to pass down the > charset attribute too.
Yepp > I will see if I manage to change the WebdavFilenameParser to use use > URIUtil.encodePath with the charset parameter. > This needs to be sorted out before the 1.0 release. Since I need this ASAP I am willing to spend time on that. Any "do it like that" hints? cheers -- Torsten
signature.asc
Description: OpenPGP digital signature
