Discussion:
[Bitpim-devel] Re: wxPython 2.5 update (Roger Binns)
Peter Pletcher
2004-09-02 08:47:21 UTC
Permalink
Patch to handle the CHARSET= parameter in a vcard is
attached.
I've committed the patch. Please can you send me some sample vcards
that (ab)use charset including what Evolution is doing so that I
can add them to examples/vcards.vcf.
Okay, here's an attached vcard I made up and exported from evolution
that has UTF-8 accented characters in many fields. Also attached is an
image of what the field contents should look like. Bitpim imports this
card just fine with the patch.

Note that I only see the behaviour of putting UTF-8 into untagged
fields with the evolution-addressbook-export utility; 'save as vcard'
works fine.

As for sending this data to the phone, of course I get an exception for
doing str(unicode-string). I know my phone can handle accented
characters but will need to investigate to verify they are encoded as
latin-1. I hope so.
Roger Binns
2004-09-09 05:19:29 UTC
Permalink
Post by Peter Pletcher
I know my phone can handle accented
characters but will need to investigate to verify they are encoded as
latin-1. I hope so.
The easiest thing to do is enter some accented characters and then
look at the phonebook files via the filesystem view.

I couldn't figure out how to enter any on my VX4400 even after
changing the language to Spanish. Couldn't figure it out on the
VX6000 either although I didn't try changing the language.

This is a dump from the brew Spanish messages on the VX4400:

00000040 d7 00 00 00 e8 00 00 00 53 69 4e 6f bf 50 65 72 ........SiNo.Per
00000050 6d 69 74 69 72 20 61 70 6c 69 63 61 63 69 f3 6e mitir aplicaci.n
00000060 20 64 65 20 72 65 64 20 73 6f 6c 69 63 69 74 61 de red solicita
00000070 72 20 75 62 69 63 61 63 69 f3 6e 20 64 65 20 70 r ubicaci.n de p
00000080 6f 73 69 63 69 f3 6e 3f bf 50 65 72 6d 69 74 69 osici.n?.Permiti
00000090 72 20 61 70 6c 69 63 61 63 69 f3 6e 20 68 61 63 r aplicaci.n hac
000000a0 65 72 20 75 6e 61 20 6c 6c 61 6d 61 64 61 3f 41 er una llamada?A
000000b0 76 69 73 6f 20 64 65 20 50 72 69 76 61 63 69 64 viso de Privacid
000000c0 61 64 41 70 6c 69 63 61 63 69 f3 6e 20 73 75 73 adAplicaci.n sus
000000d0 70 65 6e 64 69 64 61 bf 52 65 63 69 62 69 72 20 pendida.Recibir
000000e0 6c 6c 61 6d 61 64 61 3f llamada?

Assuming the missing character in aplicaci?n is an o with an accent to the
right then it indeed looks like latin-1.

Roger
Peter Pletcher
2004-09-10 22:34:40 UTC
Permalink
Post by Roger Binns
I couldn't figure out how to enter any on my VX4400 even after
changing the language to Spanish. Couldn't figure it out on the
VX6000 either although I didn't try changing the language.
Neither could I, on my VX4500. The Spanish portion of the manual is no

help either. How lame. Bitpim etc. may be the only way to enter
latin-1 characters.
Post by Roger Binns
00000040 d7 00 00 00 e8 00 00 00 53 69 4e 6f bf 50 65 72
........SiNo.Per
Post by Roger Binns
00000050 6d 69 74 69 72 20 61 70 6c 69 63 61 63 69 f3 6e mitir
aplicaci.n
Post by Roger Binns
Assuming the missing character in aplicaci?n is an o with an accent
to the right then it indeed looks like latin-1.
Yes, 0xf3 is an oacute which makes perfect sense there.
So how difficult is it to make the phone upload and download path
handle 8-bit character data? :)
Roger Binns
2004-09-12 23:42:43 UTC
Permalink
Post by Peter Pletcher
So how difficult is it to make the phone upload and download path
handle 8-bit character data? :)
I'll do that after this next release. The VX6000 shall be sacrificed
for the cause.

It will help if you examine the various files in the pim directory
since they may be using the upper bit for other things. For example
I know the SMS stuff actually only uses 7 bits for names/numbers and
packs things that way.

Roger

Loading...