Bug reports about character set problems

Post by **PetriW** » Fri Apr 02, 2004 11:10 am

Well, the API switched character set without notice again so I've decided that AOM no longer supports non-ascii characters, any character outside the standard ascii set is considered invalid, AOM will accept them but won't care for how they are converted.
So, if you see something using some weird chars like ü, ö or é display wrong don't post a bugreport, post a CReq.

Skywalka · Post by **Skywalka** » Fri Apr 02, 2004 1:33 pm

Err I don't get this

Where is it that non-ascii characters are no longer allowed?

Kanji can hardly beconsidered ascii and AniDB shows those so I was just wondering what exactly does not allow anything else than ascii - file names?

I am just asking becaue I started filing creqs again and maybe there is something I should take notice of.

Post by **PetriW** » Fri Apr 02, 2004 2:31 pm

Kanji must be written as html encoded characters, like for example:
星界の紋章 (星界の紋章)

A clear example of non-ascii characters can be seen for example here:
http://anidb.ath.cx/perl-bin/animedb.pl ... me&aid=516

(until a mod denies all my creqs again!!!, /rude Exp

My new goal, find non-ascii characters and beat everyone in denied creqs!)

Skywalka · Post by **Skywalka** » Sat Apr 03, 2004 11:42 am

I added all those descriptons and I honestly don't know the HTML encode values for the Umlaute I used

They just happen to be on my keyboard, you know

I guess I have to stop by on IRC and do a !creq to find out who is the all time leader in denied creqs now