Re: How to write file names with cyrill characters?
From: those who know me have no need of my name (not-a-real-address_at_usa.net)
Date: 01/07/04
- Next message: Ted Breen: "Re: days-between"
- Previous message: Chris F.A. Johnson: "Re: days-between"
- In reply to: Matt Benson: "How to write file names with cyrill characters?"
- Next in thread: Bill Marcum: "Re: How to write file names with cyrill characters?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 07 Jan 2004 06:10:34 GMT
in comp.unix.questions i read:
>I want to save a file on my web hosters (unix based) server.
>The file name contains cyrill characters. On my Win2000 system
>it is no problem to rename the file from pure latin char based to a cyrill
>char based file name. But to transfer/rename it on a unix based
>system is a problem. I tried to
>
>- transfer it to the server by FTP (no success)
>- transfer it with original latin based chars and rename it with ftp
>afterwards (no success)
>- transfer it with latin chars and rename it with telnet afterwards (no
>success).
what reason was given for these failures? did the rename fail or were the
results not what you expected? (exact failure messages would be best.)
>Is there way to get it somehow renamed ?
typically unix filesystems are insensitive to most characters, only / and
nul being problems. but the filenames remain a sequence of bytes so the
issue is usually the meaning of each character; i.e., characters in a
filename can either be `raw' where the values can mean anything and might
vary based on application [*], or they can be uniformly encoded (typically
utf-8) which hold their meaning but the application still is involved (it
may need to know that utf-8 is being used).
- make sure that you aren't trying to use characters which use an encoding
that includes a / or nul byte.
- you may need a better or different ftp client (e.g., kermit).
- the provider may need a better, different or reconfigured ftp server, so
that the characters allowed in a filename are not overly restrictive. it
is very common for ftp servers to restrict the characters allowed, due to
past abuses.
since telnet failed too there is a significant chance that neither of the
ftp suggestions will help, but since we don't quite know why you had
failures there is some chance that one may work so is probably worth a
quick investigation. it may even be that kermit would help with the telnet
session, i.e., kermit is also a very fine telnet client.
[*] raw encoding can be quite annoying, e.g., when i look at a filename
with a 0xd2 byte i see a capital o w/grave accent because my application
(terminal) displays using iso-8859-1, but you intended a small ve because
your's displays using iso-8859-5. iso-10646 and unicode attempt to solve
this issue -- in fact they do a quite good job of it, e.g., ms windows 2000
uses utf-16 encoding in the filesystem -- but there is typically nothing in
a unix system that would ensure that what you enter is converted to utf-8,
the tools you use must conspire to reach that outcome (kermit is one such
tool).
-- a signature
- Next message: Ted Breen: "Re: days-between"
- Previous message: Chris F.A. Johnson: "Re: days-between"
- In reply to: Matt Benson: "How to write file names with cyrill characters?"
- Next in thread: Bill Marcum: "Re: How to write file names with cyrill characters?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
