Problems with national filenames

FAR works with strings in OEM codepage, but plugin trying to work with them as if they were in ANSI codepage - as a result there is problem with russian filenames for example. WinSCP standalone application works with them correctly.

I'm aware of that. So far, no one has complained :-)

Здравствуйте. И все же, как заставить плагин winscp в фаре перекодировать имена в ANSI, а то русские имена корежатся. Мало того, что они из юникода конвертятся, так еще и тут одна ступень сопротивления.. ;)

-- Edward.

I confirm the problem.

I have a server with UTF8 encoding. If I use winscp with "Server does not use UTF8" off then everything works fine. But in the FAR plugin the names are shown incorrectly.

This is really related to ANSI vs OEM.

This is really related to ANSI vs OEM.

Sure, it is.

martin wrote:

This is really related to ANSI vs OEM.

Sure, it is.

Is there a chance that it will be fixed in the next version? :)

Do you need some more info/testing or something else?

Thanks.

Is there a chance that it will be fixed in the next version? :)

I'll try :-)

martin wrote:

Is there a chance that it will be fixed in the next version? :)

I'll try :-)

And how it goes?

E.G. wrote:

And how it goes?

I've implemented this last week. Give me a few days for release.

martin wrote:

E.G. wrote:

And how it goes?

I've implemented this last week. Give me a few days for release.

oops, no changes in 1.6.1 version :(
we're waiting :)

Народ, при подключении по протоколу SFTP (FTP) никаких проблем нет, а вот по SCP мал мало да. Я пока использую WinSCP с коннектом по SFTP и пометкой коннекта "UTF-8 завсегда".

Ну и не забудьте на хосте, вообще-говоря, сделать
convmv -r -f сКакойКодировкойЗалилиФайлы -е utf-8 *

К примеру я заливал немало FTP-плугином FAR, он лил в cp1251
соотвественно прогнать начиная с корневого надо
convmv -r -f cp1251 -е utf-8 *

Будет круто!
Но при коннекте по SCP это не поможет всё равно. И всё же файлы с русскими именами на хосте лучше хранить в UTF-8, спросите у гуру.

victor wrote:

oops, no changes in 1.6.1 version :(
we're waiting :)

Hm. I believe that this is fixed since 1.6 beta already...

At the moment this feature (use UTF-8 for filenames) is in connection settings, not in general.