Replies

Given that I’m server- and client-side, I’ll give my opinion (which is no more or less valid than yours)

Yes, you can fix it with JS, but that doesn’t address the root cause. I was *wrong* about the root cause and I don’t mind admitting that. The code and the db are solid.

There’s just a little bit of code which gets executed when displaying the thread with comments that screws everything up. People have reported that pasting text into the post box works, and that it’s fine on preview. It’s stored in the DB without problem. It shows on the main page just fine. UTF-8 FTW.

Something is filtering text on the display thread view. And that something only understands ASCII. That’s my bet. A $5 bet, if you’re interested ;)

Nobody should have to cleanse their input, everything should just work. That’s how it should be. In my opinion.

OK, quick test:

é–ªæ›¬

I’m wrong again, that broke on preview.

Another useful clue is that, if you summon up old threads (prior to last October or whenever), there is no problem with the content. That indicates the bug is in whatever now processes new user input.

E.g., post straight quotes surrounding something. The server converts your non-HTML post to HTML, adding a <br> here or there, and converting your left and right straight quotes to curly quotes. Your post looks fine. You probably don't even notice what happened to your quotes.

Now somebody quotes your post. That involves selecting your now curly quotes and pasting them into some sort of reply. The bug intervenes and entitizes the three bytes of the UTF-8 representation of your opening and closing curlies. The result is a mess.

Nobody should have to cleanse their input, everything should just work. That’s how it should be. In my opinion.

Absolutely. UTF-8 end to end!