Andreas Jung wrote:
This issue has been discussed several times in the past.
Probably, but infortunately I can't find anything about it.
Toby Dickenson wrote:
> On Monday 20 October 2003 15:01, Lennart Regebro wrote:
>
>>The fact that litmus complains about Zope's inability to accept UTF-8
>>filen
On Monday 20 October 2003 15:01, Lennart Regebro wrote:
> The fact that litmus complains about Zope's inability to accept UTF-8
> filenames is something I view as a bug.
does webdav specify how utf-8-encoded dav filenames correspond to file names
used in URLs?
> Either the already existing, but
This issue has been discussed several times in the past. There was a
consensus
not allow extended characters because of compatibility issues and
conformance of
the HTTP specs (which don't allow extended chars in URLs AFAIk in unencoded
form).
So it is your task to proof that your implementation
Hiya everyone!
I didn't get any response on my last post, so I'm charging ahead full speed.
The fact that litmus complains about Zope's inability to accept UTF-8
filenames is something I view as a bug. It can be fixed simply by
changing the default _checkid() implementation to allow extended
c
