Re: Unicode in BitPim revisit

> 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.  

No, we use ascii for most of the phones, iso8859_1 is only used for phones
that we know use this encoding. There have been no user complaints about the
phonebook/calendar/memo on the (newer) LG phones since they started using
the USTRING correctly, it works 100% AFAIK. 
The only user messages that come through now are where the phone has not had
the encoding set correctly in the packet definitions. E.g. the recent vx4650
calendar issue (fixed in rev. 3434).
A recent sanyo 8100 issue is because the packet definition is wrong, the fix
is to change 
    16 USTRING {'raiseonunterminatedread': False, 'raiseontruncate': False,
'terminator': None} name
to
    16 USTRING {'encoding': PHONE_ENCODING, 'raiseonunterminatedread':
False, 'raiseontruncate': False, 'terminator': None} name

All filesystem brew commands use ascii even on phones we know use iso8859_1.
We need to spend the time putting the correct encoding into the packets,
this is a little more involved as we cannot just assume all phones are
8859-1, pelephone for instance is 8859-3.

All that we need to do is put the correct encoding into the PACKETS.

Simon 



-------------------------------------------------------------------------
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