[CGI] MyDbEntries group listing: No shortname Really [NOBUG]
Moderator: AniDB
[CGI] MyDbEntries group listing: No shortname Really [NOBUG]
Well ...
Obviously, the "Knights" don't need a short name as such. Still, the entry I made - http://anidb.ath.cx/perl-bin/animedb.pl ... up&gid=653 - has "Knights" listed both as the full and as the short name for this group. How can this be a lame entry?
Obviously, the "Knights" don't need a short name as such. Still, the entry I made - http://anidb.ath.cx/perl-bin/animedb.pl ... up&gid=653 - has "Knights" listed both as the full and as the short name for this group. How can this be a lame entry?
Changed back, as it doesn't work well with Chii (and would most likely affect AoM aswell).bbaab wrote:Oh, well. Changing the fullname to "Knight<ZERO WIDTH SPACE>s" seems to work around this problem.
Please just ignore the lameness-warning (of which I have several myself) - it doesn't do any harm after all.
There goes my Unicode-fu.wahaha wrote:Changed back, as it doesn't work well with Chii (and would most likely affect AoM aswell).bbaab wrote:Oh, well. Changing the fullname to "Knight<ZERO WIDTH SPACE>s" seems to work around this problem.
No idea about AoM, but if Chii is written in Perl or C on a Unix system, I could write a few simple conversion routines. I had to write them anyway, due to the damn IDN in .com, .net and soon .de ...
*cough*bbaab wrote:No idea about AoM, but if Chii is written in Perl or C on a Unix system, I could write a few simple conversion routines. I could write a few simple conversion routines.
Don't you think that it's somewhat overkill making Chii Unicode-aware mainly to recognize a workaround for the webinterface with the only purpose to make one line of text disappear*? ^^;
*) And change the overall-values at the bottom
Well, yeah, but I don't think it's overkill to make Chii Unicode-aware.wahaha wrote:*cough*bbaab wrote:No idea about AoM, but if Chii is written in Perl or C on a Unix system, I could write a few simple conversion routines. I could write a few simple conversion routines.
Don't you think that it's somewhat overkill making Chii Unicode-aware mainly to recognize a workaround for the webinterface with the only purpose to make one line of text disappear? ^^;
Well, ok, it's your site, of course you can do whatever you please ... still, I'd think that names like "DNA_" or "Kiki_s Delivery Service" just might confuse someone ...exp wrote:all non-ascii chars will be removed from anidb anyway, someday.
i've just been too lazy to do it
the cgi will also convert any non-ascii character to "_" (again, not yet)
so there's really no point in making chii unicode aware }:o)
I didn't realize exp wants to convert everything into 7-bit ASCII. The characters between 128 and 255, which include the German "Umlaut" characters (ä, ö, ü...) as well as most accentuated vowels (á, à, â), are part of extended ASCII, so it's by no means necessary to use unicode, encoding or doublebyte chars to work with these.
Just out of curiousity... what's the reason why the AniDB clients can't work with characters >127? Java and .NET are aware of unicode, C, C++ and Delphi don't care about the byte value of a single byte character, and all extended ASCII chars except 255 are printable on a non-broken terminal.
Just out of curiousity... what's the reason why the AniDB clients can't work with characters >127? Java and .NET are aware of unicode, C, C++ and Delphi don't care about the byte value of a single byte character, and all extended ASCII chars except 255 are printable on a non-broken terminal.
well,
the main cause for it is that switching to full unicode doesn't work bc there are a lot of places where it would lead to problems and that the current way of handling things prevents the java jdbc driver for postgres from accessing the database it doesn't expect >127 chars in an SQL_ASCII database.
this is not that much of a problem atm bc i didn't have the time to finish the java implementation of the anidb api. and i prolly won't finish it any time soon.
as long as i only access the animedb database from perl i have no problem with 8-bit ascii.
BYe!
EXP
the main cause for it is that switching to full unicode doesn't work bc there are a lot of places where it would lead to problems and that the current way of handling things prevents the java jdbc driver for postgres from accessing the database it doesn't expect >127 chars in an SQL_ASCII database.
this is not that much of a problem atm bc i didn't have the time to finish the java implementation of the anidb api. and i prolly won't finish it any time soon.
as long as i only access the animedb database from perl i have no problem with 8-bit ascii.
BYe!
EXP