Character set conversion(?) failure during initial import from SE
+3
−0
It looks like something went wrong during the import, causing imported posts to get the wrong character encoding.
I fixed one at https://speculative-science.codidact.com/q/225476, but have come across others as well.
Can this somehow be fixed in bulk, ideally in place without having to re-do the import?
It would be a pain to have to go through everything and manually fix non-US-ASCII characters.
1 answer
+2
−0
I've fixed the most obvious failures in SQL. Beyond that... the posts are now UTF8, so fixing the encoding retroactively is difficult if not impossible - if there are other common bugs please let me know and I'll run an automatic replacement, otherwise please edit them to correct.
0 comment threads
0 comment threads