|T O P I C R E V I E W
||Posted - Aug 28 2008 : 09:49:15 AM
What is the best way to handle this? On my latest tool if a user rates a jap game with non-standard ASCII text such as this one it will blow the code to kingdom come.
So may question is what would be the best way to detect this string and fix it?
|4 L A T E S T R E P L I E S (Newest First)
||Posted - Sep 03 2008 : 05:01:30 AM
Thanks Squid. I will try and hit ya up later this week. I know your busy so I will try not to take up all your time. We both know you need to get some gaming in that schedule of yours!
||Posted - Aug 29 2008 : 10:31:35 AM
UTF-8 is a text encoding for unicode characters, so yeah any unicode standard, including ascii and other characters such as japanese letters are valid options because of the way its stored and represented.
if you really want to geek out you can read more about it: http://en.wikipedia.org/wiki/UTF-8
if i have some spare i can try and take a stab at helping you probably best to just get a hold of me on IM or something and I can see if i notice anything obvious
||Posted - Aug 29 2008 : 05:47:02 AM
Is that what that text is? UTF-8? Or is supported by UTF-8?
||Posted - Aug 29 2008 : 05:23:40 AM
this is a bit difficult to answer without having a bit more information about detailed steps on what occurs when rating a game, and where the blow up happens.
It could be something completely un-related, or it could be that you don't have your database set to UTF-8 encoding and you are trying to save the UTF-8 string to it, but off the top of my head i think even in that case the insert should not fail.
encoding is one of the most tricky things you deal with with this kind of thing - so it could be a fun one to figure out
you really shouldnt have to do anything to detect or change the string - but like i said its rather tough without knowing the code that is running, what its trying to do, the database layout, and on...and on....and on.