Re: Basic support for sktt imt2000

Roger Binns wrote:
>> An issue: I hard coded in a conversion from 'iso-8859-8' character set,
>> but I've put it in a variable that can take it's value from anywhere. I
>> think there should be a list box with encodings in the settings dialog.
>> Another option is to use the current locale for that. What do you think?
> 
> 
> I still don't understand the relevance.  The encoding is a property of the
> phone.  I haven't come across any that let you change their encoding.
> The phone model specific code should detect and use the phone encoding.
> Since all phones are fixed, that isn't particularly hard nor does it need
> to be exposed to the user.

What if a phone is used by a carrier in Israel differently then in USA? 
The encoding would probably still be 8-bit, but decoding from latin1 to 
unicode is not the same as decoding from iso-8859-8. So how can we tell? 
Is it something I can extract from the phone? I browsed through the 
filesystem and couldn't find a clue.

> The actual data in BitPim is stored in Unicode.  Consequently the phone
> model specific code must convert into and out of unicode.  This is 
> something
> that isn't user visible.

I understand that.

> Something I would like is a convertor from unicode that can munge 
> characters
> correctly such as changing an ể with an accent into an 'e'.  The main 
> Python
> convertors just drop the character completely.

This would have to do with character classes. I think perl's Encode 
module can handle those, but I don't know about python.
-- 
    "No, I do not contain myself,"
   were the final words from the set of self-excluding sets. :-)



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click