About that, Can I use... Support tables for HTML5, CSS3, etc, but I only care about easiness for now. But to convert back to normal RegExp, running XRegExp in Node.js console would show its true form. (The syntax is a little different, though, like \\p{Katakana}, rather than \\p{sc=Katakana}.)
I have tried that, actually. But in the end, Firefox on Arch Linux aside (which needs lang="ja-JP"), a simple script to change <html lang="en"> to <html lang="ja"> already works just fine.
I think that, if uncommon markdown isn’t used yet, it doesn’t matter. However, to take it seriously, is to change Markdown into AST, and turn back (perhaps with remark, rather than markdown-it, as you want to at least turn it back to simple markup <>[]).
And yeah, since I already used such code block detection for a while, I can survive just fine. (Unless I edit some weird Wiki, which doesn’t happen yet.)
BTW, this is not my fault. Your saved post isn’t as expected. (And I turned off the extension to be sure. What am I supposed to see?)
I have just noticed that <>[] can be prevented from conversion as well, by adding a single space
- < kanji>[kana]. (Actually, anything in \s, and must be in front.)
With zero-width spaces, it appears that preventing conversion in code blocks and alike is cleared. <kanji>[kana]
- \s doesn’t include zero-width spaces, though it works with everything else that has real space. I need to modify the regex a little.
- Even with my mod to prevent
<ruby>collapsing to<>[], putting ZWSP behind<rubyis somehow rendered wrongly. Must be a bug with another regex; so I enable putting ZWSP behind<ruby>(whole tag), for the time being - 振り仮名
