4 ms·
> The usual work-around is to encode the offending character(s). In this example, `!` becomes `%21`. Yeah, that was my speculation: > > Maybe a percent-encodi
by JadeNB 6y ago
> The usual work-around is to encode the offending character(s). In this example, `!` becomes `%21`.
Yeah, that was my speculation:
> > Maybe a percent-encoding would have been the way to go.
> The HN software is RFC ignorant. Could you please send an email to the Web master so the bug can get fixed?
I try to be conscientious in general about reporting bugs I find in software, but arguing about the details of Markdown parsers is an endless full-time job with no reward. Of course you are welcome to do it if you think it's worth the time.
- jwilk 6y agoIt reported this bug to HN (back in 2016…), and they acknowledged it.