Most of these scripts work better if the files have Unix line endings. However, there are some steps of the process that either expect Windows line endings, or change the file to have Windows line endings. Specifically, Solid always writes the file out with Windows line endings, and CC assumes the file has Windows line endings. If CC runs on a file with Unix line endings, you may end up with a file with mixed line endings, and that could lead to data corruption. You could also end up with mixed line endings if you apply certain regular expressions.
It is recommended that:
At the beginning of the process, change the file to use Unix line endings.
At various stages of the process, periodically check whether the file you are working with still has Unix line endings. If not, change it back.
If you have tried running one of these scripts and the output is not what you expect (for instance, there are no changes, or the output is empty, or the script says it can't find any data to run on), check the line endings.
If you are about to run a CC table over the file, first change the file to Windows line endings, then do the CC process, and then change it back to Unix line endings.
Before you do the actual import, double check that the file does not have mixed line endings. (For the import, it doesn't matter if it is Unix or Windows line endings. What matters is that it is uniform.)
There are several ways to change a file with Windows line endings to Unix line endings. Here are a few options (you only need to do one or the other):
Notepad++
Open the file in Notepad++
Use the menu item Edit/EOL Conversion/Unix (LF)
Save file
If you followed the instructions in the Infrastructure section, there should be utilities in your WSL installation called dos2unix and unix2dos. You can apply these commands in your WSL terminal like this (substitute appropriate filenames):
dos2unix < MyDatabase.db > MyDatabase-unix.db
To change it back to Windows line endings:
unix2dos < MyDatabase-unix.db > MyDatabase-windows.db