Hi forum!!!

I need help in converting Linux Text File to Windows/Notepad Text File.

Before I transfer the file, I vi the file and the format is OK then I transfer via FTP. When I transfer a text files in Linux, I use ASCII not Binary.

Now, the file is now in windows (without an extension of course). I able to view the file in dos by doing "c:\edit file2008" and the dos editor normally display it correctly like in vi but when I view it in Notepad, it got wrapped.

I tried doing....unix2dos but I got some error.

[younguns@younguns Ledgers]$ unix2dos file2008 -c ASCII newfile2008
unix2dos: converting file file2008 to DOS format ...
unix2dos: converting file newfile2008 to DOS format ...
unix2dos: problems converting file newfile2008
[younguns@younguns Ledgers]$

Any help about doing this is much appreciated.

Thank you in advance.

What does it look like in wordpad rather than notepad?

You should try:

Without -n unix2dos will assume all files have to be converted. With -n will assume the first file is the input and the second file is the output.

Hi...

Well..when I open it in wordpad its not wrapped it has spaces in between e.g. same with edit (dos) & vi. But in notepad it got wrapped.

I use notepad to test whether it will be correctly displayed. If this is correctly displayed in notepad, the file then can now be uploaded with a gov't agency use of their database record (probably they use VB...don't know).

The only work around I know, other than the other guys suggested about unix2dos is use "edit" to open in dos then save it then when I open this in notepad it is not wrapped anymore.

What I wonder about is that 2 months ago before we migrated from SCO to RHEL is that the SCO txt files are OK meaning when I transferred it to Windows & open it notepad, its not wrapped or it displayed as it should.

Thanks.

I do not get what you ask exactly, but I can try to explain what happens.

The problem is the convention used to identify a newline in a text file. Usually UNIX/Linux has a different 'convention' from Windows (no idea about what SCO uses).

Now, you usually use text editors to work with these files. Some know about both 'conventions' (like wordpad) and display the text properly, some know just their 'convention' (like notepad) and you need to take care of the transformation yourself (dos2unix/unix2dos).