Closed dajare closed 4 years ago
Yes, it's by design, because official spec not exists and nobody knows how it should work (too many collisions possible).
Workaround is to use escaping via backslash: ^up\ up^
Consider sub/sup as "something simplified you can use without guarantees".
Thanks for that helpful (and quick!) reply. So this will be a sensible "won't fix", but good to have the workaround documented.
And that "consideration" makes good sense to me! Thanks again.
You can make PR if you wish. I don't remember details about addons after those landed.
Also, can try to ping sub/sup spec actrivity on commonmark forum (but, to be honest, i don't beleive it helps in reasonable future).
I see from the README that "nested markup is currently not supported" (also on markdown-it-sub). But it did surprise me that "whitespace" breaks the parsing:
^up^
= up^up.up^
= up.upBut with
tab
orspace
, the superscript fails. I see this:^up&tab;up^
= ^up up^^up up^
= ^up up^[That last example with
space
(U+0020) of course. I haven't tested other kinds of "whitespace".]Is this by design? It seems counter-intuitive if
markdown-it-sup
is extending the feature set by adding<sup>...</sup>
equivalence. (And it seems the same is also true ofmarkdown-it-sub
, but I haven't posted this there.)