WebDAV and UTF-8 filenames
Hi guys! I've been hacking around a bit with Zope to try to support some non-ascii characters in the id's. Yes, I know it looks ugly in the URL's but when you go via WebDAV, that is not an issue. :) Anyhow, getting your Zope-object to accept non-ascii characters is not that hard, of course. But the problem comes when you try to use OpenOffice, and do a "Save As...". It seems like OpenOffice sends the new name as UTF-8, translating a nice "filé.doc" to "filé.doc". Of course, OpenOffice will translate it back, so it looks good in OpenOffice, but that the id is different from the webclient and OpenOffice is not a good idea. Could somebody help me shed some light on some issues here: 1. Does this happen because Zope missed out on UTF-8 decoding and encoding somewhere? It seems to me that this should be done in the ZPublisher somewhere, but it isn't, right? 2. I have tried understanding the ZPublisher before, but failed. Can somebody point me to where this decoding encoding should be done, maybe? Or are you of the opinion that it's to complicated a bug to fix? 3. Will Zope 2.7 be Python 2.3 only? Because that would probably make UTF-8 support easier. //Lennart
If you set the "management_page_charset" property to "utf-8" in a folder (even the root folder) then Zope will inform the browser that the charset of the management pages of this folder and all subobjects is utf-8 and the IDs in the folder listing page will look right. Cheers, Leo -- Ideas don't stay in some minds very long because they don't like solitary confinement.
Leonardo Rochael Almeida wrote:
If you set the "management_page_charset" property to "utf-8" in a folder (even the root folder) then Zope will inform the browser that the charset of the management pages of this folder and all subobjects is utf-8 and the IDs in the folder listing page will look right.
This does seem to solve the problem (at least with OpenOffice. Cadaver does not like it, but that is probably a Cadaver bug).
On Wed, 2003-10-15 at 12:50, Lennart Regebro wrote:
Leonardo Rochael Almeida wrote:
If you set the "management_page_charset" property to "utf-8" in a folder (even the root folder) then Zope will inform the browser that the charset of the management pages of this folder and all subobjects is utf-8 and the IDs in the folder listing page will look right.
This does seem to solve the problem (at least with OpenOffice. Cadaver does not like it, but that is probably a Cadaver bug).
If the "does not seem to like it" is just a charset display issue, and not an explicit error condition, then this is probably because Cadaver is a command line client, which usually (but not always) means that it's totally obvlivious to charset issues. It'll just spew whatever it receives from the server to your terminal and vice-versa. In this case, it's your terminal's job to interpret utf-8 chars correctly in this case, and to pass accented chars to Cadaver as two byte utf-8 sequences when you type them on the terminal. Cheers, Leo -- Ideas don't stay in some minds very long because they don't like solitary confinement.
participants (3)
-
Lennart Regebro -
Lennart Regebro -
Leonardo Rochael Almeida