> |I thus find this issue REALLY problematic, and I'd vote for > | - have the default encoding be UTF-8 > > I'll also vote for it, because it is what I wrote in the last mail. > > | - provide a ChannelSftp.setControlEncoding() > > I'm confusing a little bit. Do you think that this method > will resolve some of above problems?
As you mentioned yourself, there are SSH servers (e.g. OpenSSH) which do not recode the arguments of commands from UTF-8 to the locally used encoding -- they simply take the byte stream they read from a command (e.g. stat()) and pass it to the OS. As a result, on a system where no recoding happens and a user can not or does not want to use UTF-8 for file and directory path encoding, the user needs to be able to specify the encoding that Jsch should use when sending file and path names. Only with custom selected encoding can the user produce the right byte stream for file and path names that the remote side needs. That's what I think -- I might be wrong though and I'm happy to dicuss these things. Thanks, Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ JSch-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsch-users
