Re: Phone encoding error handling without rugs

>> The really difficult part is to make sure that round trips
>> work correctly.  For example if a contact is created named
>> Grid but is written to the phone as Grid.

Hey your mailer munged what I wrote.  The first "grīd"
has an i with a macron (horizontal line) over it.

> We will have the problem of distinguishing real change in the phones data
> from munged data.

The phonebook merge code believes the name already in BitPim
over that coming from the phone.

> Contacts should be OK because of the index, although we will dumb down when
> we read back and is that really a bad thing?

I have friends with accented letters in their names.  It is unbelievably
bad how they keep being stripped off in places.  (Even worse is the guy
whose name is Stéphane.  Many places assume he is actually a she and
unable to spell her own name, Stephanie.)

> We already munge the ringtone filenames (RINGTONE_FILENAME_CHARS) not that
> we shouldn't fix it.

That is for names as the user adds to the BitPim user interface.  There
have been cases in the past where people have downloaded ringtones
over the air and they have had accented characters in the filename.
(One even had a backslash IIRC).

> Are you ok with handling unmunging later as a separate item. I cannot think
> of how to do it using escaping, some fields are very limited on space.

I don't think anything should be done for tomorrow's build.  After that
stick some sort of plan in dev-doc.  Worst case we could use UTF-7 :-)

Roger 



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