Unicode in BitPim revisit

Even though we have a means to handle unicode data from the phone, 
the basic issue still remains (and borrowing a quote from this 
article http://www.joelonsoftware.com/articles/Unicode.html):

"It does not make sense to have a string without knowing what 
encoding it uses. "

And that's the problem when BitPim gets a string from the phone.  
Currently, we decode most, if not all, strings from the phone using 
iso8859_1 codec, which obviously does not work 100% of the time.  
Some options to consider:

1. Do nothing and tell users to use nothing but basic ascii.
2. Decode with 'replace' or 'ignore'.
3. Try to determine/guess the right codec (if there's such a thing) 
for each phone model .
4. Iterate through all codecs until the decode is successful.
5. Allow users to specify which codec to use through some sort of 
GUI.  This codec info can be stored along with the data as well as 
for specific phone.

Comments and suggestions are welcome.

-Joe Pham



_____________________________________________________________________
PrivatePhone - FREE telephone number & voicemail.
A number so private, you can make it public.
http://www.privatephone.com




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642