Hi! Is someone accessing zope from MS-Office with webdav daily? What are your experiences? Some weeks ago there were several complaints that files were not accessible because they were read-only. My application will have about 30 people using it at one time. The files will be regular office files. The avarage file size will be around 100-300kByte. The network will be a 100MBit Ethernet. Is it possible to use umlauts in file names? thomas
----- Original Message ----- From: "Thomas Guettler" <zopestoller@thomas-guettler.de> To: <zope@zope.org> Sent: Monday, April 22, 2002 07:07 Subject: [Zope] WebDAV access from MS-Office
Hi!
Is someone accessing zope from MS-Office with webdav daily?
What are your experiences?
Some weeks ago there were several complaints that files were not accessible because they were read-only.
This problem should be solved in the latest 2.4/2.5 version.
My application will have about 30 people using it at one time. The files will be regular office files. The avarage file size will be around 100-300kByte. The network will be a 100MBit Ethernet.
Is it possible to use umlauts in file names?
No (at least not without hacking the corresponding check for valid Ids). Andreas
On Mon, Apr 22, 2002 at 09:21:50PM +0200, Dieter Maurer wrote:
Andreas Jung writes:
Is it possible to use umlauts in file names?
No (at least not without hacking the corresponding check for valid Ids). Should we kill this restriction?
I think/hope it is no longer necessary.
We discussed this problem last year and the key question was, what characters should be allowed: utf-8, latin-1, iso-8859-X.. or whatever. I would really love to see the restriction lifted. However lifting the restriction must not break existing code. Andreas
Andreas Jung writes:
On Mon, Apr 22, 2002 at 09:21:50PM +0200, Dieter Maurer wrote:
Andreas Jung writes:
Is it possible to use umlauts in file names?
No (at least not without hacking the corresponding check for valid Ids). Should we kill this restriction?
I think/hope it is no longer necessary.
We discussed this problem last year and the key question was, what characters should be allowed: utf-8, latin-1, iso-8859-X.. Looks like a configuration/startup parameter, similar to "-L". It would control the default encoding of (all) non-Unicode strings inside Zope -- similar to Python's "default_encoding".
or whatever. I would really love to see the restriction lifted. However lifting the restriction must not break existing code. Lifting a restriction is not likely to break existing code. Of course, we must be careful when URLs are constructed. When I looked at it for the last time, it appeared to correctly quote the components. But there may be lots of places...
Dieter
participants (4)
-
Andreas Jung -
Andreas Jung -
Dieter Maurer -
Thomas Guettler