Character encoding issue?

[Drunken Monkey]

I've noticed a fair number of older posts now have garbage characters in favor of unicode characters

i.e.

now, you may have seen news in other publications of the forthcoming Ducati Hyperfighter that's allegedly scheduled for a 2008 EICMA debut. The thing is, the machine is a total work of fiction. Created by conceptual artist Oberdan Bezzi for his site Motosketches, the Hyperfighter envisions what a hypothetical future 1098/Hypermotard hybrid might look like. As usual â€" we're big fans of Oberdan's work â€" the concept is full of clever ideas that come together to create a really good-looking bike. Presented alongside a fictional timeline for its development and a description of its technology â€" sort of an imaginary brief for the concept â€" we understand why people want to believe in it. The confusion seems to arise from a reader comment Oberdan left on MCN's website. Their commenting system is confusing, giving equal precedence to content created by both the publication and its commenters, which has led to several other websites reporting on the Hyperfighter as actual news. But honestly people, apply some critical thinking to things.

Not sure if this was already an existing problem, but I've really only noticed it post new server.

I know, this is a weak sauce bug report, but I just thought I'd mention it.

[Drunken Monkey]

Even seems to have affected the BOMB entires:

This is Celli's second Monster.

Weird.

[DarkStaR]

Seems like it's just "quotation" marks and 'apostrophes'.

[darylbowden]

Seems like SQL isn't properly escaping certain characters for some reason.  Lemme take a look and see what I can do about it.

[darylbowden]

Hmm, there might not be anything that can be done about this.  Some old posts are affected and some aren't.  I'm thinking that something happened during the mysqdump from the old db that didn't escape certain characters properly.  I'll try and look into it some more, but we might just have to live with it.

[ducpainter]

IMO, if that's the worst thing that happened in this it's a non issue...

but that's just me.

[darylbowden]

IMO, if that's the worst thing that happened in this it's a non issue...

but that's just me.

I agree.  I've actually only found one post so far that has been affected (I'm sure there's others), but overall I don't think anyone will lose any sleep over it.

[Drunken Monkey]

Yeah, as long as it's fixed for posts going forward, no biggie.

[bigiain]

I'm thinking that something happened during the mysqdump from the old db that didn't escape certain characters properly.

Errrmmm, let me guess, this upgrade crossed over the MySQL4.0 - MySQL4.1 versions?

Gah! (_There's_ some grief I didn't need to remember...)

big

[ducpainter]

Errrmmm, let me guess, this upgrade crossed over the MySQL4.0 - MySQL4.1 versions?

Gah! (_There's_ some grief I didn't need to remember...)

big

new server does use an updated version....