maemo.org Bugzilla – Bug 2781
fails to import non-UTF8 QUOTED-PRINTABLE vcard
Last modified: 2010-02-18 14:48:18 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
create a vcard containing something like say æøå (the norwegian letters) and
try to import it into the contacts list.
fails to import the contact. and if its a multicontact file, fails to import
the rest of the file.
> create a vcard containing something like say æøå (the norwegian letters) and
> try to import it into the contacts list.
Can you please attach an example vcard (remove any confidential data, please)?
Does the vcard has the charset defined?
With which application has the vcard been created?
I remember several such bug reports for Evolution, e.g.
Created an attachment (id=1015) [details]
this vcard contains the norwegian letters æøå.
if one attempt to import it into the addressbook, one will get a error message.
if a contact with similar letters in it is part of a multicontact card, the
import will fail when reaching it.
Created an attachment (id=1018) [details]
Imported vcard from comment 2 in GNOME Evolution.
Might either be an upstream bug or not a bug at all - how should the
application know how to interpret the byte values when there is no charset
from what i can tell, this encoder/decoder here does a fine job of decoding the
quoted-printables used in the vcard:
OK, I'm partially wrong. I should read the specification of QUOTED-PRINTABLE
before adding comments... :-)
Importing a Vcard with the line
works fine in Evolution.
*** Bug 2867 has been marked as a duplicate of this bug. ***
After some testing, this looks like an upstream evolution-data-server bug to
I have filed upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=560681 .
Milan said "It seems EVcard doesn't understand the CHARSET parameter", I guess
that's the basic problem here. See
Any brave C volunteers that want to write a patch? :)
Upstream has a patch for this that has already been committed to svn trunk.
It does not fix the broken vcard attached in comment 2 (that one is just an
invalid card), but it will make it possible to import iso-8859-* charset vcards
if the charset is properly set.
Adding patch keyword (patch attached in upstream bug)
This has been fixed for Fremantle.
Marking patches of interest to Diablo (Maemo4) community updates, please excuse
"Patches" are there:
But you might want to wait a bit before preparing Diablo 4 patches, as I am
working on a related issue right now.
I'm gathering some vcard example data. What device/program produced the
the vcard was from a sonyericsson Z710.