Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Splinty

Oh yes, i understand it already!
getting PuTTY SSH source for WinSCP You missed Translation features.
Thank You very much for Tracker Bug 325!

Let's kill em!
martin

Actually for the terminal with SFTP session, separate SCP/shell session is opened. That's why the UTF does not work.

Anyway this issue has been added to tracker.
Splinty

Oh, my poor English!!! :?

Yes, You are right. The host i work with has a default file name encoding UTF-8. And WinSCP (and PuTTY with Translation=UTF-8 ) correctly shows it (i mean international symbols of course). But Terminal doesn't. It shows the same incorrect something as WinSCP does via SCP protocol.

As result of it Terminal can't make different shell commands with everything having international symbols, as You understand.
martin

Re: Calling terminal: what's about encoding

You mean the the files in file panel show correctly, while the same files in terminal window do not?
Splinty

Calling terminal: what's about encoding

Hello.
Terminal tool is very suitable one, but it's hard to use it when browsing a UTF-8 encoded file names with international symbols (i use SFTP connection with forced UTF-8 option). So, why not take into account that option (for example) and don't encode the output of terminal window?