option localenc=[o_m|ansi|utf8]

Let the user change encoding of local paths/files, to let WinScp access any file on local drives in programmatic/scripted mode. Currently the encoding is O_M only.

Sorry, o_m is your black word, but you understand what I mean.

Thanks for your post. This issue is being tracked already.

When the application becomes Unicode, console's input/output encoding will remain O_M, won't it? I mean, when some program pokes characters to console using pipe and reads the output dripping from another pipe, will the encoding of those chars still remain O_M?

This option is to treat those chars as UTF-8 or ANSI.

Mercury wrote:

When the application becomes Unicode, console's input/output encoding will remain O_M, won't it?

I do not know yet.

Hi, winscp is a great problem with a powerful scripting interface. I was wondering if you could clarify how I could set the option in a script to support unicode file names (in this case Chinese).

According to this link: https://winscp.net/eng/docs/sftp
"With FTP protocol this means that UTF-8 will be used when the server announces support for it."

Should I put in this line?
option UTF-8 encoding for filenames on

or this line?
option UTF-8 on

Donny

Please read
https://winscp.net/eng/docs/faq_script_ini