To save space? Huh?
Windows still standardizes on crlf for text. It may now allow others but the native format is crlf. And yes this is something that only happens on Windows. Neither MacOS nor any Unix based alternative needs CRLF.
This has been happening with Sigil on Windows for over 15 years and no one has complained once.
Quote:
Current Status on WindowsDefault Behavior:
Built-in tools and standard APIs on Windows still output and expect CRLF by default to preserve backward compatibility with legacy software and command-line tools.
Notepad Updates: Windows Notepad natively parses and maintains LF or CR line breaks in existing files rather than corrupting them, but it still defaults to stamping new files with CRLF.
|
Is this your way of asking for a feature request or env variable to prevent them from being added back on Windows? If so, you are going about it in a strange way.
Let's see what if anything other longterm users of Sigil on Windows say about this. If they too want this behaviour to change, I will add that is a future version of Sigil.