[comp.protocols.tcp-ip.ibmpc] Question for FTP Software...

lance@hermix.UUCP (Lance Ellinghouse) (03/06/91)

I have a question for FTP, Inc. that has yet to be answered by them...

When will they support auto-line termination conversion?

The reason I ask is that there are other companies (not PC based)
that support conversion from UNIX (LF terminated) to Mac (CR terminated)
automaticly.

We have a need for this on the PC!
I know.. they supply UNIX2DOS.EXE and DOS2UNIX.EXE, but these are
NOT practical in a developement environment where code is shared
between UNIX/Mac/PC!

Lance

ljm@FTP.COM (leo j mclaughlin iii) (03/07/91)

>I have a question for FTP, Inc. that has yet to be answered by them...
    
>When will they support auto-line termination conversion?
    
>The reason I ask is that there are other companies (not PC based)
>that support conversion from UNIX (LF terminated) to Mac (CR terminated)
>automaticly.
    
>We have a need for this on the PC!
>I know.. they supply UNIX2DOS.EXE and DOS2UNIX.EXE, but these are
>NOT practical in a developement environment where code is shared
>between UNIX/Mac/PC!

I beg to differ.  Automatic attempts at CRLF conversion are dangerous
for the very reason that UNIX/Mac/PC/VMS/... environments do exist.

By the by, I *have* worked in a sophisticated UNIX/Mac/PC shared development
environment using SCCS, NFS, and RSH which was quite pleasant and always
'did the right thing'.
    
enjoy,
leo j mclaughlin iii
ljm@ftp.com

Disclaimer: The opinions expressed herein reflect the individual biases
which prolonged experience with distributed environments has yielded,
not the biases of my fine employers.

BILLW@MATHOM.CISCO.COM (William Chops Westfield) (03/07/91)

    I have a question for FTP, Inc. that has yet to be answered by them...

    When will they support auto-line termination conversion?

    The reason I ask is that there are other companies (not PC based)
    that support conversion from UNIX (LF terminated) to Mac (CR terminated)
    automaticly.

huh?  TCP's FTP protocol explicitly supports "ascii" mode, where the
sending system is supposed to convert the file to nvt-ascii format (can
involve code conversion, but most often involves end-of-line conversion),
and the receiving FTP converts back to the "local" representation of a
"text" file.  As far as i know, FTP's software has always supported this
(perhaps being aided by the PC disk text format being almost exactly
nvt-ascii...)

BillW
-------