Not sure if this has been discussed before (I dug into the code and issue but couldn't find anything). Is there any desire/objection to convert -- to en-dash and --- to em-dash? Or are we not wanting to get into any typography extensions for flexmark?
Hiya @technosophist! We typically use github rendering as a guide. If it is doing something, we consider it. In some cases we do a better job than github, for example we render adoc more nicely than github does. Does github do something special with -- and ---?
Good question. I noticed that codox does, but didn't check Github
It looks like it GFM uses --- for https://github.github.com/gfm/#thematic-breaks and https://github.github.com/gfm/#setext-headings
Right.... forgot that they can be used as header syntax:
I am a header
-------------I can just insert a literal em-dash, so it's not a huge deal. It just isn't wide enough when looking at a monospaced font (e.g. in code and REPL), but I guess I can just live with that compromise. 🙂
I just looked up adoc, and it seems to understand -- as an emdash (under specific cases)
https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/#text-replacements
Both those GFM cases pretty strictly require a single line of only hyphens, so I suppose it would be possible to support em-dash inline, but I don't see any mention of it.
nah. just did a test and it doesn't
yeah I suppose I could use asciidoc...
I'm a fan of adoc. When given a choice, I use it!
I might actually like making tables then. I hate wrestling markdown over tables and then just being disappointed with the result.
Adoc is actually thoughtfully designed for creating documentation. I like that! Tables can be headache in any markdown... but you have more control in asciidoc.