Unicode test....
öööääääÜÜÜÜÖÖÖÄÄÄÄüüüüßßßßßß§
€€€€€€€€€€€€€€€€€€€€€
Volcano
Jan 10 2003, 15:47
Quotation marks: """"""""""""""""""""
Tilde: ~~~~~
Accents: ééé à à Ã
Cedille: Ç
U-Umlaut: üüü ÜÜÜ
Euro: €
[For anyone wondering, we're just trying to figure something out on IRC, we're not crazy]
€€€€€€€€€€€€€€€€€€uro
ÜÜÜÖÖÖÄÄÄöööäääüüüßßßß§§§§
tangent
Jan 11 2003, 03:48
Chinese doesn't work either. Tried that before.
We had to go back to the iso-8859-1 (Western European) charset for now, since Unicode has some errors on this board. Most likely because Apache encodes in iso-8859-1 per default, even if the board's charset is set to UTF-8. As a result, some user info (Montréal, Mülheim...) is garbled.
Test: ąęśćóńłżź
EDIT: Polish-specific characters doesn't work either.
QUOTE(Cobra @ Jan 13 2003 - 10:08 AM)
Polish-specific characters doesn't work either.
Poland doesn't quite count as western european.

Anyway, first we have to resolve this Apache 2 "default config mistake", then the board can be set to UTF-8 again.
Dibrom
Jan 13 2003, 21:12
QUOTE(CiTay @ Jan 13 2003 - 05:31 AM)
QUOTE(Cobra @ Jan 13 2003 - 10:08 AM)
Polish-specific characters doesn't work either.
Poland doesn't quite count as western european.

Anyway, first we have to resolve this Apache 2 "default config mistake", then the board can be set to UTF-8 again.
I'll look into it.. but the HA server isn't using Apache2.
Sachankara
Jan 14 2003, 04:12
The reason why "Invision Board", "phpBB", etc, can't handle UTF-8 is because they convert "&" to "&" so for example "み" becomes "み". And it simply doesn't work because of that...
The only forum software that I know of that doesn't convert & to & is "vBulletin". So unicode works just fine with it...
QUOTE(Sachankara @ Jan 14 2003 - 11:12 AM)
And it simply doesn't work because of that...
The Unicode stuff we tested worked fine. The stuff you see in the first and second post are remnants of that, which look garbled now, since it's set to western european again. But the only thing that didn't work during our limited testing was the user info, and as far as we know, this is the backend's fault, not IBF's.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.