[Tickets #12329] Re: Many fields are ignored when importing vCard files

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12329
------------------------------------------------------------------------------
  Ticket             | 12329
  Updated By         | acn at annachristina.eu
  Summary            | Many fields are ignored when importing vCard files
  Queue              | Turba
  Version            | 4.1.0
  Type               | Bug
  State              | Resolved
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Jan Schneider
------------------------------------------------------------------------------


acn at annachristina.eu (2013-08-15 09:26) wrote:

Hallo,

>> I've exported this card from ownCloud, which simply shows more than
>> one "cell" entry, just as my iDevices do.
> But Turba doesn't. It only supports the attributes in the original  
> config/attributes.php for importing.

Does this mean that if I would use Turba as my primary address book  
and connect some other device via CardDAV and add another phone number  
for "cell phone" from there (people can have multiple cell phones as  
well as multiple home or work phones nowerdays), this number will move  
to /dev/null without notice?

The biggest problem in my opinion is that these values are moved to  
/dev/null without ANY notice to the user.

The user should be informed that his/her data is trashed or should be  
given some way of resolving this issue.

>> From another VCARD, Turba ignores the TEL-field of type "OTHER":
>>
>> (only the TEL lines)
>> TEL;TYPE=CELL;TYPE=VOICE:0179-4722993
>> TEL;TYPE=OTHER;TYPE=VOICE;TYPE=pref:089-12035482
>
> Again, only one cellPhone attribute is supported.

Is this against vCard standard? (you seem to insist on standards, see below)

>> ITEM2.IMPP;X-SERVICE-TYPE=None;TYPE=pref:x-apple:123456789
>> ITEM3.IMPP;X-SERVICE-TYPE=None:x-apple:somename
> There is no IMPP attribute. And using this without an X- prefix is  
> even breaking RFCs.

Okay.

Kind regards,
Anna Christina Naß