3 ms·
> Markdown qua Markdown, unambiguously supports HTML tags. The section I quoted (and responded to) didn’t say “Markdown supports HTML tags”, it said (emphasis
by latexr 2y ago
> Markdown qua Markdown, unambiguously supports HTML tags.
The section I quoted (and responded to) didn’t say “Markdown supports HTML tags”, it said (emphasis added) “Markdown parsers support (…)”.
So unless you’re arguing that a tool cannot be considered a true Markdown parser¹ unless it parses HTML, the distinction is irrelevant. I wasn’t making a general argument, I was responding to a specific claim.
> You can verify that yourself
Yes, I am quite familiar with that subpar piece of code and specification. I have spent some time implementing a Markdown parser myself (the output wasn’t HTML) and Gruber’s resources were by far the worst. For various reasons he has been an awful steward of Markdown; its ubiquity is despite him, not because of. Forgive me if I don’t find the author to be the authoritative source anymore.
¹ https://en.wikipedia.org/wiki/No_true_Scotsman https://en.wikipedia.org/wiki/No_true_Scotsman
- travisjungroth 2y agoI think you’ve kinda lost the thread. From the top comment: > Markdown was designed… Surely Gruber is an authority on that. And anyway, “ markdown is a lightweight representation of html” is true enough that calling it “decidedly incorrect” is wrong. Certainly it’s not a point that’s supported by going to author intent.
- latexr 2y ago> And anyway, “ markdown is a lightweight representation of html” is true enough that calling it “decidedly incorrect” is wrong. Yes, I completely agree with that. And that wasn’t the point I quoted or responded to. > From the top comment Again, I wasn’t replying to the top comment, I was replying to what I quoted, from the comment I replied to.