>From someone who speaks a native language with several
"extended characters": even non-unix systems (has Windows
earned the "system" status already?) sucks with weird file
names.
>
> That should work.. but, spaces and "extended characters" are so "unclean" in
> the Unix world, it was never de
So it must be an FreeBSD issue, sorry for the noise.
> I ran a few tests, and OpenBSD seems perfectly capable of using those
> extended characters have you tried using doubled quotes?
I tried *everything* (backslash, double quotes, single quotes,...)
BTW my ssh version is OpenSSH_4.5p1 FreeBSD
Marc Rene Arns wrote:
Hi,
I need to transfer files via sftp (ssh ftp) from a Windows machine.
This files may contain Umlauts (vd|) and Spaces.
I made several tests and stuck with the following:
sftp [EMAIL PROTECTED]:'/file-withv|d.txt'
works, but
sftp [EMAIL PROTECTED]:'/file with spaces.tx
I ran a few tests, and OpenBSD seems perfectly capable of using those extended
characters have you tried using doubled quotes?
sftp [EMAIL PROTECTED]:"file with spaces and Umlauts.txt"
That should work.. but, spaces and "extended characters" are so "unclean" in
the Unix world, it was ne
Apparently the Umlauts in my mail got mangled by majordomo, I meant german
latin1 characters, sometimes rewritten as 'ae' 'oe' and 'ue'.
benny
> Hi,
>
> I need to transfer files via sftp (ssh ftp) from a Windows machine.
> This files may contain Umlauts (vd|) and Spaces.
>
> I made several tests a
5 matches
Mail list logo
