My examples from the other thread:
Examples:
Wrong: ’ Right: ' - Direct3D games in DosBox
Wrong: А подробнее могут рассказать на Призраках Right: А подробнее могут рассказать на - Identify a strange card
Wrong: weg ähm Right: weg ähm - What the hell is that?
Wrong: Â¥WeedsÂ¥ Right: ¥Weeds¥ - Duke Nukem's "Mighty Foot" Russian Folk Dance LOL!
(Right is according to robertmo)

Boss key in Ész-kerék crashes DOSBox:
É --> É
é --> é
á --> á

(Google still has cached copies of the old forum, so that's one way to find the correct fixes.)

虚空漂流ニルゲンツ
Correct is: 虚空漂流ニルゲンツ

3D Accelerated Games List (Proprietary APIs - No 3DFX/Direct3D)

wouldn't it be better to make it the other way:
convert all known characters from most popular languages to wrong characters and we will have a complete database this way

If you thought someone might have done that already, you'd be right.
http://www.i18nqa.com/debug/utf8-debug.html

was also wondering if it would be possible to make another vogons forum conversion from the date it was changed, but this time without this mistake. And then just compare both forums (excluding new posts).

Funky characters, are we talking about letters too ? such as Ææ Øø Åå ?

I don't know what ³ is, but it's annoying in this thread:
How to pull a directory listing from a CD with multiple sub-directories? 1997 CD Burn with lots-o-drivers

The aforementioned page indicates that ³ is supposed to be... ³ ?

As that was apparently the piped output of "tree", odds are it never rendered properly when it was originally pasted either.

Ah, those appear to have been desired to be "tab" characters then.

[EDIT] Correction, the "tree" command creates a nifty ASCII-art file directory. So the different characters are the classic menu-drawing ASCII, and whitespace.

[EDIT2] Furthermore, piping it to a text file on Windows results in those bad characters instead of the ASCII-art menus.

[EDIT3]
³ = │ = Extended ASCII 179 = 0xB3
À = └ = Extended ASCII 192 = 0xC0
 = ┬ = Extended ASCII 194 = 0xC2
à = ├ = Extended ASCII 195 = 0xC3
Ä = ─ = Extended ASCII 196 = 0xC4
etc.

[EDIT4]
http://stackoverflow.com/questions/138576/sav … unicode-support

Anyhow, this isn't the board conversion's fault. Dunno if we should fix this...

There's more of this output from other utilities, example for Qbix:
https://www.google.com/search?q=%22%C3%82%C2% … iw=1429&bih=585