Talk:Data Type

I cannot (at least I don't know how) to upload text-file as a binary one. As result, the text files come to server corrupted. Indeed I was forced to reject from FileZilla for this type of uploading and use another tool. The FZ has to resolve this task.

Data Type recognition

It is time to abandon the File Extension as a data type identifier. I would propose that the program examine the data file prior to transmission to see what kind of file it is and what set up is needed to send the file correctly to the destination.

In these cases the file should be converted to a standard format (Text) and transmitted to the destination as a valid Text file. on the destination.

• *NIX text file
• Windows/DOS text file
• Apple text file

IN these cases, the file should be sent in binary form.

• Images, compressed files and other binary data streams.

I deal with a lot of data files on a regular basis. I need to be able to make sure the file arrives as a valid data file on the destination.
Under present conditions, I have a program that I pre-process files with to make sure they are the correct data format.

--Randy Smith aka Randyrls 12:57, 16 March 2010 (UTC)

Unable to transfer Unix text file to Windows with correct line end

I have followed the directions given for setting the Data Type to either Auto, ASCII, or Binary. However, regardless of the setting I use, when downloading a text file from a Linux server to a Windows client, the ASCII conversion is not done. The files all come over with just the (LF) Line Feed character, and not the (CR) Carriage Return, which Windows uses.

I can transfer a text file from the Windows client to the Linux server and it correctly removes the CR when in ASCII data type, but it does not add it back to the file when downloading.

I need to know how to get this to work correctly, or use another file transfer program, as I have a piece of software on Windows that will not read these files without the correct Windows end of line.

Please help