Comment # 11 on bug 66038 from
(In reply to comment #4)
> Created attachment 81243 [details]
> labels seen in vcard file
> see the vcard file corresponding to the "TEST" card

What I don't see in this example is the "personal fax" and "professional fax"
that you mentioned earlier. What the example are normal business (TYPE=WORK)
and private (TYPE=HOME) phone numbers, which, by default, are of TYPE=VOICE.

It is also not clear yet how you synchronize with Android.

It's not hard to strip the explicit "VOICE" flag before storing in Akonadi.
This should solve problem 3, at least in the Android -> Akonadi direction. All
it takes is someone with the time and interest to set up a test environment, do
some minor changes to the source code and then write an "incoming script"
similar to the one that already exists for EDS.

See akonadisyncsource.h and getSynthesisInfo():
         * Disable the default VCARD_BEFOREWRITE_SCRIPT_EVOLUTION.
         * If any KDE-specific transformations via such a script
         * are needed, it can be named here and then defined by appending
         * to the fragments.
        info.m_beforeWriteScript = ""; // "$VCARD_BEFOREWRITE_SCRIPT_KDE;";
        // fragments.m_datatypes["VCARD_BEFOREWRITE_SCRIPT_KDE"] = "<macro
name=\"VCARD_BEFOREWRITE_SCRIPT_KDE\"><![DATA[ ... ]]></macro>";

The corresponding script for EDS is in VCARD_BEFOREWRITE_SCRIPT_EVOLUTION.

(In reply to comment #5)
> there is another pb wich may lead to conflict
> in the vcard file we see that it is a 3.0 vcard format
> in syncevolution/sources/addressbbok/config.ini
> we see
> KDE Address Book = KDE Contacts = addressbook = contacts = kde-contacts
> #     vCard 2.1 (default) = text/x-vcard
> #     vCard 3.0 = text/vcard
> the default format used by syncevolution is 2.1 and the format used by
> kaddressbook is 3.0
> may be it would be better syncevolution use 3.0. no ?

For exchanging data with Akonadi, vCard 3.0 is always used. The comment above
refers to the format used when exchanging with a SyncML peer. In SyncML, vCard
2.1 often works better because vCard 3.0 is less common and some peers do not
implement it properly. If a peer supports it, vCard 3.0 can be enabled. The
peer templates already do that where appropriate.

You are receiving this mail because: