WebDAV enhancements

[brong]

I'm posting this on the blog as well:

I’ve added support for a couple of new features in WebDAV.

1. modified time update support, so clients like NetDrive can now set the modified time of a file to help with synchronisation.
2. lock support so MacOS 10.3.x can now write files (you still can’t use https until 10.4, that’s a client issue)
3. client “quirks”, so quota usage works on macs (you can see how much free space you have!)
4. also, international character support works around a bug in Konqueror.
5. an attempt to correctly handle clients (like NetDrive) that write filenames in the Windows local character set instead of UTF-8 (*grrr*)

On that last topic, I’d love to hear feedback about your experience with non-English characters and your client. I’m trying to come up with a full set of workarounds per client to get the best language support we can.

It will fall back to trying to use your “DefCharSet” value from the the Options screen on the web interface - the same way that the email management screens fall back to that characterset if the encoding of an email is buggy.

Bron.

[hadaso]

Originally posted by brong
It will fall back to trying to use your “DefCharSet” value from the the Options screen on the web interface - the same way that the email management screens fall back to that characterset if the encoding of an email is buggy.

Sometimes I wish it would just fall back to my default encoding (windows-1255). Lately I see a lot of email that in HTML view and in text view are garbled. Encoding is in UTF-8, the message MIME parts seem to state the charset (windows-1255) correctly in a "Content-type" header, but the interface is displayed in UTF-8 with the characters from the message parts (and Subject/from/to headers) mapped to the UTF-8 equivalents of ISO-8859-1 (Latin-1) characters with the same code as the Windows-1255 characters that should be there. In Framed view FastMail seem to give the correct encoding in the HTTP headers (though perhaps this is just using my defaultand not the encoding from the MIME header). I sent some samples to the bug reporting address a while back, but perhaps other people using other encodings (Cyrrilic? Arabic? East Asian?) have enacountered this kind of problem?

This is something that I think started only the past few weeks, and seems to be related to implementing UTF-8. One advantage of the old way was that the browser coulf be used to switch to the correct encoding (even when it was incorrect in the MIME headers).

[robmueller]

I'll check the bug folder, but I didn't think anything had changed with regard to displaying messages recently...

Rob

[hadaso]

The samples I forwarded to the bug reporting address (bug@ME) were forwarded in mid-september. And it took me some time to realize that there's a recurring problem, so the changes, if any, might be a few weeks older than that.

[robmueller]

I've gone through your emails and replied directly.

Rob