Using the copy command is it possible to generate Unix on Windows and vice-versa?
On Unix a Line Feed character (LF, ASCII 10) is used to mark the end of a line. On Windows an LF plus a Carriage Return (CR, ASCII 13). Although the copy command allows you to specify many different delimiters, the ‘nl’ (New Line) one will generate LF or LFCR depending on the platform it is running on. Fortunately there are a couple of ways to achieve this result. Using Ingres Net you can run the copy command on Windows with the database on Unix (or vice-versa) and it will generate LFCR EOLs. If you generate the file on Unix and transfer via ftp to Windows (or vice-versa) you can specify ASC (ASCII format) and it will translate the file. There are some utilities for Windows and Unix which can be used to translate the files – e.g. on Unix sed ‘s/$/^M/g’ orig.dat > windows.
Related Questions
- Is it possible to call an operating system command from within isql on an OpenVMS machine (equivalent to the !! command in UNIX)?
- Database 1: Is it possible to transfer a Windows EndNote library to EndNote on a Macintosh (and vice-versa)?
- Using the copy command is it possible to generate Unix on Windows and vice-versa?