In moggy’s entry “Take my Fianc[acute-e]e to see polar bears” at /view/1346, the acute-accented e is not being properly rendered.

I’m not sure it will solve this particular problem, but in the past I’ve worked around similar glitches by explicitly specifying UTF-8 character encoding in the HTTP Content-Type header.