RE: Phone encoding error handling without rugs

> >During testing I've found a problem with internal storage as unicode.
> 
> Since this affects all the phones, I think it's better to do 
> a thorough test on it.  I'm planning build next Monday to 
> clean up all the known discrepancies, and leave this one out. 
>  This would allow more test time as well as having a 
> reasonable stable build.  IMHO, being able to handle Unicode 
> is nice, but not worth the risk at this point.

The CSVSTRING class needs to be modified to handle non-ascii charsets in
order for some of the samsungs and gsm phones to have non-ascii charset
capabilities.
I cannot test this class, so someone else will have to change it. I've
re-organised the STRING class to make this easier.

Simon



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642