[Bug 1632] [PATCH] UTF-8 hint sftp-server extension

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=1632

--- Comment #10 from Marton Balint <cus at fazekas.hu> 2010-01-08 10:52:55 EST ---
Yes, charset problems may also arise between UNIX systems. The ultimate
solution would be the filename-charset extension, but as far as I know
that would require SFTP protocol version 6, which is not going to
happen in openSSH in the near future.

There is a really good comparison of protocol versions here:
http://www.greenend.org.uk/rjk/2007/sftpversions.html

I didn't want to solve everybody's problem, I tried to came up with an
as simple as possible patch to solve one of the most common charset
problems with a Windows client and a UTF-8 UNIX server. And it's
important to mention that this problem will not go away in time unless
WinSCP change the default charset to UTF-8. On the other hand, the
standard charset of UNIX systems will be UTF-8, so the different
charset problem between UNIX systems will hopefully be less and less
common.

Of course, if that's more acceptable I may recreate my patch, to give
hint not just for utf-8 encoding, but for the encoding of your choice.
But implementing the filename-charset extension seems too complicated
to me, because that would require protocol version 6, in-server charset
conversion, etc...

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.