** Reply to message from Gaby vanhegan <[EMAIL PROTECTED]> on Sun, 16
Oct 2005 18:34:54 +0100
>On 16 Oct 2005, at 17:13, Dave Anderson wrote:
>
>>> That being said, FTP is well past the time it was designed for.
>>> OpenSSH
>>> is very stable and featurefull. Just make sure it isn't *too*
>>> featureful
>>> for what you're doing.
>>
>> There _is_ one useful-to-me feature of FTP that I can't find in SCP or
>> SFTP: any equivalent to 'ascii mode' (I frequently transfer text files
>> between systems with different end-of-line conventions). Am I just
>> being blind, or is there really no way to do this?
>
>Surely you want the file to appear at the other end in exactly the
>same format that it was on your system?
No, I'd like it to appear in a functionally-equivalent format -- which
requires optional newline conversion.
> This sort of thing is
>normally a client-program issue. I have interarchy on my mac and it
>deals with all of that, plus it has a preference for whether or not
>to convert newlines.
It can't be just a client-side issue, since the software needs to know
the end-of-line conventions for both the source and target systems in
order to determine what, if any, conversion is needed (and whether the
file being transferred is "binary" or "text" needs to be specified and
perhaps passed to the other end of the link).
It's a simple conversion, and the whole thing is certainly not a major
issue, but I'd rather have a one-step process than a two-step process.
[I do realize that the simplistic way FTP handles this really isn't
sufficient in the current enviroment of multiple character sets and
multiple encodings of some character sets.]
Dave
--
Dave Anderson
<[EMAIL PROTECTED]>
