Re: Phone encoding error handling without rugs

On Sunday, 02 April 2006, Simon C is rumored to have said...
> > I don't think anything should be done for tomorrow's build.
> The modified STRING will be ready in time and a couple of phones adjusted
> and tested, do you want me to hold off with this change?
> I tried the vx4400, it dislikes non-ascii characters, but at least has the
> good sense to display a ?. This phone will stay ascii only.

Actually, I was still using a VX4400 when I first started using BitPim.
At that point, I discovered that if I put "Fernández" into BitPim's
phone book and wrote that to the phone, it would show up correctly on
the phone side.  While it's possible there are some characters that
aren't used correctly on the phone, it seems clear that the VX4400 uses
ISO 8859-1 (Latin-1) or some close variant.

At some point, however -- I don't recall when -- I notice this same name
would be written to my phone as "Fernández".  It looked fine in BitPim,
but something changed, and raw UTF-8 characters were being written out
to the phone.  I never reported it as a bug at the time, as I didn't
know enough about how BitPim worked to give a proper diagnosis inside of
the package.  (I barely do now.)

So, ISO-8859-1 should be a close enough match for the VX4400.  I'm sure
some test entries could be created to see what, if any, characters from
that set are *not* copied correctly.

--
Gregory Pratt                                               [email protected]
East Rutherford, NJ, USA                       http://www.panix.com/~gp/
"The only good spammer is a dead spammer."
PGP Key Fingerprint:  DC60 FCDE 91E2 3D41 91A3  45DB B474 3D3A 3621 AAFE


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