On Fri, Oct 31, 2008 at 8:52 AM, Jiří Kuhn <[EMAIL PROTECTED]> wrote: > the client which doesn't work with UTF-8 is Total Commander > (http://www.ghisler.com/). But what is worst, total commander connected from > different country (with different locale) works with different charset. > Clients from Macintosh don't make it easer. Providing the charset as a > configuration of FtpServer doesn't help (but it would be good - just to > specify the default FtpServer charset), because the charset have to be > changed after user login. FTP protocol does have nothing to specify client > charset (as far as I know), so it have to be per user configuration setting.
Ouch, that's pretty bad by TC. Lets dig deeper, how to other FTP servers handle this? I will test myself but if you already know that would be great. Does TC send any command to indicate what charset it will be using? We support RFC 2640 which stipulates the UTF-8 support (http://www.faqs.org/rfcs/rfc2640.html). I'm not sure I like the idea of doing this on a per user level, that would require hard coding the users choice of client which feels a bit to much (what if the same user has both a Mac and a PC for example). /niklas
