login about faq

Dear all,

I am attempting to transfer files which contain Unicode characters in the filename. The host is running Tectia server 6.4.1, the client is running Tectia client 6.4.1. Both machines are running Windows Server 2008 R2.

The test file I am attempting to transfer is "Ω-reactor.txt" (if you can't read that, the first character is Unicode character 03A9, "GREEK CAPITAL LETTER OMEGA"). When I view the folder on my client containing this file in Tectia secure file transfer, it displays as "O-reactor.txt" (that appears to be a standard ASCII uppercase letter O), and when I attempt to transfer it to the server, I receive the error message "6: fcr_parse_raw: O-reactor.txt (src): no such file" - presumably because there really is no file called O-reactor.txt.

I've been able to connect to the server using other sftp programs, including FileZilla, which display the filename correctly, and can transfer it. The problem is that when it arrives on the server, the name has changed to Ω-reactor.txt.

Does anyone have any suggestions for how I can transfer files with unicode names?

asked Apr 26 '13 at 16:40

Thomas_Just's gravatar image

Thomas_Just
6112


Hi,

I will start with some positive news: if you would be transferring your file between 2 Unix/Linux machines that are both set to use UTF-8 as character set encoding then most of the things would work fine and your file would transfer without problems.

However, I see that you are trying to use Tectia SSH Client and Server to achieve that on Windows platforms. I am afraid you are out of luck. It is because Tectia SSH Client and Server use so called legacy API functions to access files in most cases. That API only supports code pages that use only 256 characters at the same time.

That means that you could probably transfer your file “Ω-reactor.txt” between those machines using Tectia, but you would have to set both of them to use Greek as “Language for non-Unicode programs” (code page Windows 1253). That requires reboot.

It is a shame that some programs are still ignoring Unicode. It is about 20 years since Microsoft introduced Unicode into their system (or more?).

As a workaround you could use some archiving program that supports Unicode to pack all your files into one archive; transfer that; and unpack. From my experience WinRAR was the only one I found that supports Unicode on Windows properly. But I wasn’t looking too much. All versions of ZIP archives usually failed similar way as Tectia. But that was some years ago. Nowadays the native Windows folder compression may support it? I should test that...

I am afraid I didn't help much...

Regards,

Martin

PS: some competing SSH implementations do support Unicode in filenames, but you would have to have both client and server supporting it and it would have to support SFTP protocol version 6 (some earlier SFTP version implementation may also work, but certainly not SFTP v3 which Tectia uses).

See also this question:How to use SSH with UTF-8 encoding.

link

answered Apr 26 '13 at 22:49

Martin%20Dobsik's gravatar image

Martin Dobsik
599126

edited Apr 26 '13 at 22:54

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×55
×2

Asked: Apr 26 '13 at 16:40

Seen: 4,711 times

Last updated: Apr 26 '13 at 22:54

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.