Don't break the Windows' EOL.

I still don't see why this was here, but the unit tests are clear : this ```string.replace``` was useless !