|Posted by Vladimir Panteleev|
in reply to ag0aep6g
Posted in reply to ag0aep6g
On Friday, 2 April 2021 at 10:12:25 UTC, ag0aep6g wrote:
> On 02.04.21 09:56, Vladimir Panteleev wrote:
>> On Thursday, 1 April 2021 at 16:21:42 UTC, ag0aep6g wrote[...]
>> I have added a lint rule which warns on thus omitted HTML code, and offers to fix it (by adding escaping backslashes).
> Nice, but the warning doesn't show up for me. Probably not deployed yet?
No, it's deployed. Note, though, that the check runs when you click "Send".
You can use the hidden old D group for testing:
> Does the forum even support any HTML tags? If not, there's no point in stripping them. But maybe that's a limitation of the Markdown library you're using.
The implementation does provide a knob with two settings (strip all HTML or allow all HTML). I don't know if it's due to a technical limitation of that particular implementation. I suspect that the reason may be something along the lines of that for the purposes of the formal specification, there should be a simple and clear rule for when sequences of characters are interpreted as HTML vs. when they are not, or something like that.
> As far as I'm aware, the newsgroup and mailing list interfaces are popular among forum regulars. If replying to them with Markdown is difficult, that's going to be annoying for the web users.
> Luckily, the difference Markdown makes will be benign most of the time. It's not a big deal when "**emphasis**" or "`some code`" get interpreted as Markdown.
Yes. But also, though formatting is indeed very useful for *some* posts, it will not significantly improve the majority of posts.