Re: RE: [BitPim-user] Help: lost response

On Mar 12, 2006, at 4:08 PM, Simon C wrote:
> Browsers let the user choose the encoding type, could we add an option 
> to do
> something similar and set the default encoding type to get past this 
> issue
> (for the short term), that way we don't have to know how the phone is
> configured.
>
But it is the phone that has the encoding.  The user has no way of 
knowing
what the encoding is.

> I'd also explicitly convert all strings to unicode when 
> reading/writing to
> the database.
>
They are.  It is at that point that the exceptions currently happen 
since the
strings aren't already in unicode (or ascii).  Each phone module needs 
to be
updated to convert from unicode to their scheme on writing and vice 
versa
on reading.

I have been looking for a good conversion database.  For example if e 
with
an accent is not supported by the phone encoding then it should be 
converted
to a plain e.  Unfortunately the last time I checked the Python code 
just
removed characters.  Jośe should become Jose not Joe.

Ṝṍḡḝṝ


-------------------------------------------------------
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&kid0944&bid$1720&dat1642