Admittedly – I'm the denizen of MSE who gets edited the most often. I've a community who reads my posts and spends the effort and time to fix up my quirks.

There are a significant number of posts about random characters that don't render properly – often , errant line breaks and others under the blog tag here. On one hand – it reflects the community's willingness to report such issues.

On the other – to a significant extent, the blog is a tool used to communicate to the 'broader' internet – customers of the paid products, and folks in the peripheries of the community. The quality of the blog reflects on both the company as well as their products and ... this sort of 'minor' error doesn't reflect the effort that's put into many of these posts and work the company does. While I suspect some of this are tooling issues – it feels a lot like these could be caught by proofreading after publication or at least at some stage where the 'final' rendering is done.

As such, could the folks who work on the blog put something in place to check on their posts at the appropriate time to handle these minor formatting issues and errant characters to shorten the loop for fixing it?

  • 3
    Isn't this the same as posted 1 hour ago: Consider having someone spot-check the rendering of blog posts after they are posted
    – bad_coder
    Commented Oct 18, 2022 at 10:57
  • 3
    @bad_coder meta.stackexchange.com/questions/382987/…
    – Tinkeringbell Mod
    Commented Oct 18, 2022 at 11:03
  • 3
    @bad_coder yes it's the same. But this one might be better phrased, so better think twice before deciding which to close as dupe of which. Commented Oct 18, 2022 at 11:03
  • 1
    A lot of these errors seem like technical issues with the rendering of the content that may not show up in whatever they're being previewed in. I'm not sure checking before publishing would reliably catch such errors, and so I'd suggest instead spot-checking the rendering after publishing, perhaps as part of a standard "go live" checklist for blog posts.
    – Ryan M
    Commented Oct 18, 2022 at 11:04
  • 3
    I'm 99% sure the [OBJ] characters are added only after publishing, and not seen in preview, so "something in place to check on their posts before they're publicly published" won't help. Commented Oct 18, 2022 at 11:05
  • @RyanM In my experiences in wordpress - there's usually a way to publish a post but hide it... I'll adjust to reflect after tho Commented Oct 18, 2022 at 11:05
  • @JourneymanGeek but are they using WordPress now? Think they switched to use something else. Commented Oct 18, 2022 at 11:42
  • At the moment I'm pretty sure its a outsourced wordpress instance. I might be wrong, but if so, same feeling, different tool :D Commented Oct 18, 2022 at 11:59
  • Was there a recent blog entry that merited this attention? Commented Oct 18, 2022 at 12:52
  • 1
    It used to be a lot worse on the Stack Overflow blog. I think copy editing by someone else than the author is now part of the workflow. I would be surprised if an automatic tool could achieve such a high hit rate. Commented Oct 18, 2022 at 13:02
  • @Mari-Lou any recent blog post. That's the problem. :/ Commented Oct 18, 2022 at 13:23
  • This was the most recent one but the blog tag has quite a few. Commented Oct 18, 2022 at 13:40
  • Is the copy-editing the real problem, or is it just a symptom of a blog with low quality content? Commented Oct 18, 2022 at 14:14
  • 1
    I would say that's a different problem - which probably would be tackled in another question. But its very much something I brought up before, and needs a lot of interal debate over what the actual goals of the blogs are. Commented Oct 18, 2022 at 14:16


You must log in to answer this question.

Browse other questions tagged .