The only difference is the
: Unix (LF, \n) vs. Windows (CR LF, \r\n). You can easily convert between them with dos2unix/unix2dos or simply Notepad++.
Unlike
,
srrdb is inconsistent:
Code:
columns: dats nfo | srrdb nfo | dats sfv | srrdb sfv | release
U = Unix EOL
W = Windows EOL
W | U | W | W | Luigis_Mansion_3_NSW-VENOM
W | W | W | W | Luigis_Mansion_3_Update_v1.1.0_NSW-VENOM
W | W | W | W | Luigis_Mansion_3_Update_v1.2.0_NSW-VENOM
W | U | W | W | Luigis_Mansion_3_Multiplayer_Pack_DLC_NSW-VENOM
W | W | W | W | Luigis_Mansion_3_Update_v1.2.1_NSW-VENOM
W | W | W | W | Luigis_Mansion_3_Update_v1.3.0_NSW-VENOM
W | U | W | W | Luigis_Mansion_3_Multiplayer_Pack_1_DLC_READNFO_NSW-VENOM
W | U | W | W | Luigis_Mansion_3_Update_v1.4.0_NSW-VENOM
W | U | W | W | Luigis_Mansion_3_Multiplayer_Pack_2_DLC_READNFO_NSW-VENOM
Considering that srrdb accepts user submissions and seeing as all .sfv files on both sites as well as all .nfo files on dats are in the Windows EOL format, I would say that it is the correct one, which also matches my general experience with scene releases.
This difference was probably caused by someone in the chain between the initial "leaker" and the srrdb uploader using an FTP client not in binary transfer mode, but the default automatic one, which uses ASCII (text) mode for certain file types and unfortunately converts their line endings to the client system's format.