Comment by londons_explore
16 hours ago
This is probably the case of a bodged migration from one CMS to another.
My blog suffered the same, and going through loads of old pages to check and fix them just isn't worth the effort.
16 hours ago
This is probably the case of a bodged migration from one CMS to another.
My blog suffered the same, and going through loads of old pages to check and fix them just isn't worth the effort.
The archived version from 2012 is showing the characters correct. So probably some migration like you said.
https://web.archive.org/web/20120319180000/https://fffff.at/...
The website itself has been closed since 2015 according to the front page.
https://fffff.at/
Which also suffers from encoding problems making weird characters show up.
But which was showing the characters the way it should on August 1st 2015 when the site was closing down.
https://web.archive.org/web/20150801234212/http://fffff.at/
Who wants to bet that at some point after the closing of the site, they switched over from a live CMS to a static copy of the site and in the process of doing so things got a little screwed up when exporting data from a MySQL database with the different encoding weirdnesses that can sometimes occur with MySQL and how the db schema was set there.
Yeah this really looks like an encoding issue during migration.
I've run into similar problems when moving old content between systems, especially with MySQL and mixed encodings. It can get messy surprisingly quickly.