[sync] Empty CNs with some vCards
Sven Heuer
s.heuer at hicom.de
Tue Oct 31 06:56:39 PST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hallo Karsten
Ich gehe davon aus, dass Du entsprechend deiner Email-Adresse deutsch
sprichst also schreibe lieber in deutsch um den Verlust durch meine
Übersetzung zu vermeiden :-)
Nach weiteren Nachforschungen entstehen die Vcard's ohne Namen im WM5
und wahrscheinlich auch im WM2003. Der Synthesis Client überträgt es
dann entsprechend.
Outlook 2003
BEGIN:VCARD
VERSION:2.1
N:;Taxi;;Firma
FN:Taxi
ORG:Taxi
NOTE;ENCODING=QUOTED-PRINTABLE:W=FCrfelfunk=0D=0A=0D=0ACabcall=0D=0A
TEL;WORK;VOICE:+49 (800) 2222255
REV:20061031T132720Z
END:VCARD
WM5 via Active Sync
BEGIN:VCARD
VERSION:3.0
N:;;;Firma
FN:Taxi
ORG:Taxi
TEL;PREF;WORK;VOICE:+49 (800) 2222255
TEL;PREF;HOME;VOICE:
EMAIL;PREF;INTERNET:
EMAIL;INTERNET:
EMAIL;IM:
EMAIL;IM:
EMAIL;IM:
END:VCARD
Horde via SynthesisClient
BEGIN:VCARD
VERSION:2.1
N:;;;Firma;
FN:Taxi
TITLE:
ORG:Taxi;
BDAY:
TEL;HOME;VOICE;X-Synthesis-Ref1:
TEL;WORK;VOICE;X-Synthesis-Ref1:+49 (800) 2222255
EMAIL:
URL:
NOTE:
ADR;HOME:;;;;;;
PHOTO:
END:VCARD
Mein Vorschlag wäre die Re-Formatierung in das der RFC entsprechende Format.
Gruß Sven
Karsten Fourmont wrote:
>> 2. why is firstname AND lastname mandatory ?
>
> Never said so. I've been referring to the vcard (2.1) specification from
> www.imc.org. (http://www.imc.org/pdi/vcard-21.doc)
> In a vcard, the "N" attribute specifies the name as follows:
>
> N:last_name;first_name;addidional_names;name_prefix;name_suffix
>
> The N attribute itself is mandatory. However individual fields may be
> empty.
>
> On the other hand, the FN fields is completly optional.
>
> So if you only have one name field in your database, how would you deal
> with an entry
>
> N:Mouse;Mickey;;;
> FN:Donald Duck
> Would you store Donald or Mickey? Currently Turba stores "Mickey Mouse"
> as this is from the mandatory field.
> But then, what wouls you store as name for this:
> N:;;;;
> FN:Donald Duck
> Donald or empty? In this case Turba chooses "Donald Duck". An FN value
> is better than nothing.
>
> Turbas data fields are completly user configurable. Generally it's
> better to have seperate first and last name fields. To do so, see my
> post on Oct 15th about "Re: [sync] Syncing Turba contacts"
>
> You could also configure your Turba config so that you have first name,
> last name and name (FN, displayname) as three completly seperate fields.
>
> Cheers,
> Karsten
>
> Quoting Sven Heuer <s.heuer at hicom.de>:
>
> Hi
>
> 1. i think overwriting of mandatory attributes with other Values is not
> usable. Either i can handle it or not !
>
> 2. why is firstname AND lastname mandatory ?
>
>
> The usage of FN in Outlook and other Clints is "Save/Display as" with
> variants:
>
> lastname, firstname
> firstname lastname
> company
> lastname, firstname (company)
> company (lastname, firstname)
>
> In my opinion mandatory attributes firstname OR lastname OR company in
> any combination are sufficient.
>
>
>
> bugs at bugs.horde.org wrote:
>>>> DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
>>>>
>>>> Ticket URL: http://bugs.horde.org/ticket/?id=4509
>>>> -----------------------------------------------------------------------
>>>> Ticket | 4509
>>>> Updated By | Karsten Fourmont <karsten at horde.org>
>>>> Summary | Empty CNs with some vCards
>>>> Queue | Turba
>>>> Version | HEAD
>>>> Type | Bug
>>>> State | Assigned
>>>> Priority | 1. Low
>>>> Owners | Karsten Fourmont
>>>> -----------------------------------------------------------------------
>>>>
>>>>
>>>> Karsten Fourmont <karsten at horde.org> (2006-10-28 08:02) wrote:
>>>>
>>>> We currently have only one name field in turba and so have to deceide
>>>> whether to store info from "N" or "FN".
>>>> The "N" attribute currently overwrites the "FN" attribute as the
>>>> latter is
>>>> optional while the former is mandatory. However in cases where firstname
>>>> and lastname in "N" are empty, the FN should be used to avoid empty
>>>> names.
>>>>
>>>> Implemented accordingly in cvs. IMHO resolved.
>>>>
>>>>
>
- --
sync mailing list - Join the hunt: http://horde.org/bounties/#sync
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: sync-unsubscribe at lists.horde.org
>>
> --sync mailing list - Join the hunt: http://horde.org/bounties/#sync
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: sync-unsubscribe at lists.horde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFFR2QmXOfGByLZzqgRAmbjAJ9IpufYCnpCttRmQlCX29R/xRN+TQCbBDqw
88UJIVVEYX3GuestlNiFyX4=
=DCN6
-----END PGP SIGNATURE-----
More information about the sync
mailing list