Support vCard version 3 natively

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Import a vcard file containing photos
2.  Photos do not show on the phone
3.  Export to a new vcard, photos are still there but the format doesn't comply 
with
RFC2426

What is the expected output? What do you see instead?
Expected:
PHOTO;ENCODING=b;TYPE=jpeg:/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGB

Got:
PHOTO;TYPE=JPEG;ENCODING=BASE64:
/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB

What version of the product are you using? On what operating system?
Version 0.8

Please provide any additional information below.

Original issue reported on code.google.com by momtchil...@gmail.com on 22 May 2009 at 10:22

[GoogleCodeExporter]

I was working from the IMC standard (http://www.imc.org/pdi/vcard-21.txt) 
rather than
RFC2426. I think this is the format output by Sony Ericsson phones, but I'm not 
sure. 

Which phone are you using?

I don't have time to support alternative input/output formats, but 
(a) this can be done fairly easily outside the phone
(b) I will accept patches that do so as long as they maintain the original 
format by
default (subject to review).

Original comment by duckt...@gmail.com on 28 May 2009 at 4:10

[GoogleCodeExporter]

This is on a HTC Magic running Cupcake, but I would be surprised if Google 
switched vcard formats
between versions (but then again who knows)
I will try to get you a patch this weekend

Original comment by momtchil...@gmail.com on 28 May 2009 at 10:52

[GoogleCodeExporter]

The original file comes from KDE Kontact

Original comment by momtchil...@gmail.com on 28 May 2009 at 10:53

[GoogleCodeExporter]

Same problem here - my vcard comes from kaddressbook version 3.5.10

Original comment by madc...@gmail.com on 4 Jun 2009 at 8:34

[GoogleCodeExporter]

Changing this from a defect to a request for enhancement.

Original comment by duckt...@gmail.com on 8 Jun 2009 at 7:54

• Changed title: Support vCard version 3 natively
• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Issue 7 has been merged into this issue.

Original comment by duckt...@gmail.com on 8 Jun 2009 at 8:19

[GoogleCodeExporter]

Issue 9 has been merged into this issue.

Original comment by duckt...@gmail.com on 4 Jul 2009 at 7:06

[GoogleCodeExporter]

Original comment by duckt...@gmail.com on 4 Jul 2009 at 7:07

• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

All the commas in my "notes" field have now a \ in front of them. I guess it's 
for
character escaping, but it would be nice to remove them before the final 
import. Or
is it a missinterpretation by the Android Contacts app?

I'm not sure if it's the right issue to attach this to but I think it has to do 
with
parsing the vcf-file, too...

Original comment by spamgang...@googlemail.com on 17 Oct 2009 at 6:03

[GoogleCodeExporter]

I use KDE Kontact (ver. 4.3.2).

I was able to import my photos by opening my vcf file in a text editor, and 
doing a
search and replace of

PHOTO;ENCODING=b to PHOTO;ENCODING=BASE64

The import of photographs was then successful.

However all phone numbers types are listed as "other" after the import, instead 
of
Cell, Home, Work, etc...

And multiple imports add multiple entries of each email address in a vcard.

Original comment by threebre...@gmail.com on 25 Nov 2009 at 5:27

[GoogleCodeExporter]

Issue 26 has been merged into this issue.

Original comment by duckt...@gmail.com on 5 Mar 2010 at 6:03

[GoogleCodeExporter]

I have a hack that supports the TYPE= thing for TEL items for CELL/HOME/WORK, 
I'm not sure how to do a pullup request, but it's the most recent push to my 
clone of the repo.

http://code.google.com/r/jasper-youtube-vcardv3/source/detail?r=921b7e011a50eb63
ee663f6ee73440eb63c7eb94&name=sms

Original comment by jasper-y...@pointless.net on 13 Dec 2011 at 2:18