ProFTPD handles this using virtual hosting. Each virtual host can have it's own charset. I have found this:
http://home.h01.itscom.net/para/software/misc/proftpd-iconv/index-e.html But it meas that an user has to actively make correction - to use another url. Total commander sends FEAT command but it looks like it ignores UTF8 line... I think, being able to change charset transparently for an user would be great option. At least, I would use it :-) (Or I can imagine a heuristic based on client's IP.) Jiří Kuhn. 2008/10/31 Niklas Gustavsson <[EMAIL PROTECTED]> > 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 >
