2009/3/31 Niklas Gustavsson <[email protected]>
>
> On Tue, Mar 31, 2009 at 9:25 AM, Jens Viebig <[email protected]> wrote:
> > Im not sure 100% but i think this is a client issue. You have to make sure
> > that the client uses UTF-8 control encoding.
>
> Agreed, but we might be able to support some features that might ease
> the pain for those with clients without UTF-8 support. Say for example
> that you got an FTP server where you know most or all of your users
> are from Japan. Having a fallback from UTF8 to Shift JIS might make
> sense, right?

If i remember correctly, someone requested some months ago that
TextLineDecoder wasn't hardcoded to UTF-8 and it seems pretty obvious
from the link in https://issues.apache.org/jira/browse/FTPSERVER-283
that clients not supporting UTF-8 are pretty common, so it is not
unreasonable that we add support for 'charsets' other than UTF-8.

 A fallback would be nice  but with current impl it sounds rather
tricky to send back messages in the client's charset/encoding, right?
I haven't checked it anyway.


>
> /niklas

Reply via email to