I wish the indent = code block behavior would get deprecated from the #markdown specs. Triple backtick fences for code blocks and single backticks for inline code seem to have those bases covered, and indents could be freed again for the purposes for which they’ve always been used in prose and verse. (Markdown sucks for #writing#poetry because of the indent prohibition.)
Programmers aren’t the only ones who use markdown.
I've never really been that impressed by them, and maybe I'm in the minority about that, but I also will make the effort to use the proper Unicode for many characters (e.g. … ℃ ㎜ π ‽ ½), so I can understand the impulse. Curly quotes and a few other characters happen to be in a range of Windows-1252 encoding that makes them inherently unreliable after coming in contact with Windows.
I'd argue that these encoding issues are not rare, because of this weakness. It doesn't take long to find examples.
@curlyquotefails@alxlg@edwiebe@obsidianmd Although I’ve seen it before, I haven’t run into that issue much (certainly it doesn’t affect me day-to-day). It seems like a technical problem to be solved rather than a reason to throw in the towel and use straight quotes where they’re not appropriate.
For anyone who cares about typography, straight quotes in prose are a nonstarter. They also create problems in anything that’s heading to a designer for layout.