There are several instances of escaped HTML in the latest issue of The Overflow, Sufficiently advanced HTML conversion feels like magic:

enter image description here

Further down there's another '.

  • 4
    Related: The latest edition of The Overflow's content has incorrectly generated quote and apostrophe characters. On MSO (a while back): There's no escape from HTML entities on the Blog. Maybe it's time we make a general post asking this to be fixed for all past and upcoming blog posts.
    – Justin
    Commented Jul 29, 2022 at 14:21
  • 2
    I feel like there's a certain irony here Commented Jul 29, 2022 at 14:24
  • 3
    I couldn't resist - it's Friday after all ...
    – Glorfindel Mod
    Commented Jul 29, 2022 at 14:27
  • 1
    @Justin we can't ask to prevent future mistakes, the staff working on the blog work in a certain way, and we can't change that. (Publish, wait for feedback telling what's wrong, and when they notice the feedback, fix.) Commented Jul 29, 2022 at 17:24
  • What is the underlying reason for this? Blog content that gets copied from somewhere else and some of it double escaped before it enters the WordPress source? (The WordPress source is a sort of pseudo HTML (e.g., significant hard line breaks, but back to 1995 for styling as italics)). Commented Jul 30, 2022 at 18:07
  • Perhaps it is for Popper to make to a simple tool to detect and/or prevent this problem. And then write about it in a series of blog posts afterwards? It would also give insight into how efficient Stack Exchange, and in particular Stack Overflow, is as a research tool (read-only mode). E.g., how easy is it to find the solutions (presuming they already exist)? Commented Jul 30, 2022 at 18:12
  • @This_is_NOT_a_forum lol that would never happen. But yeah, sounds good. (Such a magic tool to detect human errors and fix them) Commented Jul 31, 2022 at 6:33

2 Answers 2


It seems the escaped HTML in this blog has been unescaped (a.k.a. fixed!) -

enter image description here

  • 1
    Until the next blog... Commented Jul 30, 2022 at 11:15

Thank you for taking the time to report this problem.

I've spoken with the Marketing team, which runs the blog; apparently, this was due to an error in our content management system. That issue has now been fixed, so this shouldn't happen again in future blog posts – but that doesn't automatically fix these HTML issues in previously published blog posts.

In the meantime, the HTML issues in this particular blog post have been fixed, as Justin's answer notes.

  • 1
    It's already in your system via a status-review retag, but you may want to check out this more comprehensive post about the unescaped characters that span a large number of The Overflow's editions.
    – Spevacus
    Commented Aug 2, 2022 at 20:43
  • 1
    @Spevacus: Yep, I'm planning to respond to that one (and to an MSO post reporting the same issue) momentarily.
    – V2Blast
    Commented Aug 2, 2022 at 20:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .