Re: Displaying Hebrew characters

Roger Binns wrote:
>> So, I guess I need to tell it what encoding I'm using, but I could not 
>> find where to do so. Can anyone direct me?
> 
> BitPim originally used host encoding which was whatever flavour of
> 8 bit codepage the user had.
> 
> During the migration to wxPython 2.5, we switched over to using Unicode
> everywhere.  (BTW Mac doesn't have a Unicode 2.5.2 so things are worse
> there).
> 
> There is currently zero code that deals with characters going to or from
> phones.  This is in the todo list to fix:  http://bitpim.org/todo.html
> 
> Data that comes from external sources such as Outlook, vCards etc should
> work fine.

Ok, I have a workaround that will alow me to work for now: 
some_string.decode('cp1255') right where I get the string. I think after 
I get something working I can work on adding an encoding listbox to the 
settings dialog and enforce its value in (I think) common.py: 
forceascii->force_user_enc or something. Haven't really dug in yet.

BTW - Ely, didn't you have to deal with the same issue? I see you are 
with Pelephone too.

Roger kept on writing:
 >> And not to be only on the asking side, I'm attaching a Makefile I
 >> wrote to replace makepackets.sh. The advantage of it is that if you're
 >> only updating your own protocol, there's no need to remake all other
 >> protocols (not really an issue now, but I'm a forward thinker).
 >
 >
 > The shell file has the advantage of automatically picking up all
 > the files.  The previous scheme often had people forgetting to
 > add new .p files to the main list.  We were also adding new phones
 > at a considerably higher rate.
 >

I like Stephen's idea.
-- 
  Keep on rocking in a free world!


-------------------------------------------------------
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_id=6595&alloc_id=14396&op=click