Hi,
+-From: "Oberhuber, Martin" <[EMAIL PROTECTED]> --
|_Date: Tue, 25 Sep 2007 15:45:56 +0200 _______________________
|
|* Take a local Windows box with default encoding ("Cp1252")
| and a remote Linux (RHEL4) box with UTF-8 encoding.
|* There are some Unicode characters that lead to bytes
| which cannot be expressed in Cp1252: For instance, the
| character ',Bh(B' includes 0x8d in UTF-8 and byte 0x8d
| is not defined in Cp1252.
|* As a result, when reading the directory with the standard
| encoding, Jsch replaces character ',Bh(B' by a question mark
| '?'
|* But even glob_remote cannot resolve the question mark by
| the original bytes --> as a result, remote files which
| include the ',Bh(B' character cannot be worked on at all!
|no stat(), no ls() etc... no Jsch ChannelSftp command
| at all works on such files.
|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?
Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
+1-415-578-3454
Fax +81-22-224-8773
Skype callto://jcraft/
-------------------------------------------------------------------------
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
