Unix newlines to windows newlines (on Windows)

Question

Does anyone know of a way (say Powershell, or a tool) in Windows that can recurse over a directory and convert any unix files to windows files.

I'd be perfectly happy with a way in Powershell to at least detect a unix file.

It's easy do this for one single file, but I'm after something a bit more scalable (hence leaning towards a Powershellish solution).

Answer 1

There is dos2unix and unix2dos in Cygwin.

Answer 2

If Cygwin isn't for you, there are numerous standalone executables for unix2dos under Windows if you Google around, or you could write one yourself, see my similar (opposite direction for conversion) question here.

Answer 3

download vim, open your file and issue

:se fileformat=dos|up

Batch for multiple files (all *.txt files in C:\tmp - recursive):

:args C:\tmp\**\*.txt
:argdo se fileformat=dos|up

Answer 4

You can use Visual Studio. File -> Advanced Save Options...

Answer 5

Here is the pure PowerShell way if you are interested.

Finding files with atleast one UNIX line ending (PowerShell v1):

dir * -inc *.txt | %{ if (gc $_.FullName -delim "`0" | Select-String "[^`r]`n") {$_} }

Here is how you find and covert UNIX line endings to Windows line endings. One important thing to note is that an extra line ending (\r\n) will be added to the end of the file if there isn't already a line ending at the end. If you really don't want that, I'll post an example of how you can avoid it (it is a bit more complex).

Get-ChildItem * -Include *.txt | ForEach-Object {
    ## If contains UNIX line endings, replace with Windows line endings
    if (Get-Content $_.FullName -Delimiter "`0" | Select-String "[^`r]`n")
    {
     $content = Get-Content $_.FullName
     $content | Set-Content $_.FullName
    }
}

The above works because PowerShell will automatically split the contents on \n (dropping \r if they exist) and then add \r\n when it writes each thing (in this case a line) to the file. That is why you always end up with a line ending at the end of the file.

Also, I wrote the above code so that it only modifies files that it needs to. If you don't care about that you can remove the if statement. Oh, make sure that only files get to the ForEach-Object. Other than that you can do whatever filtering you want at the start of that pipeline.