Markdown support isn't a bad idea, actually, as long as they don't break the most important (IMO) property of Notepad: binary WYSIWYG. I.e. if I type in some plain text and then open the file with anything else (including after moving to another machine/platform, or even viewing raw data stream in transit or on drive), I can trust to see that text, as is, and nothing else. In particular, if I restrict myself to lower 127 bytes, I expect byte-to-byte correspondence.

(Modulo CR/LF, of course.)

▲

tracker1 4 hours ago | parent | next [-]

FWIW, Notepad has had support for BoM detection and wide-characters (UTF-16/UCS-16) for some while. That said, IMO, most simple editors at this point should default to UTF-8 encoding and only LF for line endings.

▲

java-man 7 hours ago | parent | prev [-]

Remember this?

https://en.wikipedia.org/wiki/Bush_hid_the_facts

	▲	Terr_ 5 hours ago \| parent \| next [-]
		I think the Real Bug™ here comes from product-management: Nobody should be taking this kind of stochastic guess process and then just... 100% trusting the outcome with no feedback to the user and no way for the user to correct bad guesses. For example, a prompt when opening the file like: "It's unclear what kind of data this is, here are a few options with a preview, pick which one you'd like me to use." Annoying, but them's the breaks when you're making software and aren't willing to put in hard requirements about what it is expected to (not) operate on.
	▲	TeMPOraL 6 hours ago \| parent \| prev [-]
		Ah, the times when computing used to be full of wonder and discovery.