This comment I posted shows the URL parsing bug I just encountered. It's pretty self-explanatory.

  • The parser appears to have stopped at an n-dash. I remember some time ago extended ASCII characters in URLs were encoded, and shown, as %-sequences in browsers' address lines. They show normally now but maybe that's just a browser feature, maybe the standard still requires the address to consist of 7-bit chars only?
    – Andriy M
    Mar 12, 2014 at 6:19
  • URL Encoding is still required for some characters like %20 for a space, but I'm guessing this is unrelated and is an issue with whatever regex or parsing the site is doing in the comments.
    – JNK
    Mar 12, 2014 at 12:17
  • 1
    I would usually post URLs using [text](url) markdown, e.g. en.wikipedia.org/wiki/Entity–attribute–value_model. Of course this drastically reduces the amount of text you can put in a comment (maybe that's by design :-)). Anyway I think this affects the whole network, not just dba.se...
    – Aaron Bertrand Staff
    Mar 12, 2014 at 16:06
  • or his one: meta.stackexchange.com/questions/88297/… Mar 12, 2014 at 16:25


Browse other questions tagged .