You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded curl-7.87.0_1-win64-mingw.zip and the text files have LF instead of CRLF line endings and are not viewable in notepad. Here's a screenshot from a Windows 7 VM. (ignore the chinese text it's for a bug where I needed to switch locale)
The text was updated successfully, but these errors were encountered:
Windows 7 is not supported anymore by MS. Adding these two, I made the decision that it's not worth to identify and convert everything to CRLF for the sake of old Windows systems. So far nobody complained. I think it's also a reasonable workaround to change the default text viewer to an alternative that copes with LF EOLs. Overall, I prefer not altering original/input files, unless absolutely unavoidable.
- Restore CRLF in README.txt, COPYING.txt, etc.
This reverts commit be6bfb2. Notepad in recent systems can properly
process LF-only lines but we're releasing a product that can run on
legacy systems where that may not be true.
Fixescurl#42
Closes #xxxx
I downloaded curl-7.87.0_1-win64-mingw.zip and the text files have LF instead of CRLF line endings and are not viewable in notepad. Here's a screenshot from a Windows 7 VM. (ignore the chinese text it's for a bug where I needed to switch locale)
The text was updated successfully, but these errors were encountered: