Hello! This kind of parsing is not unusual, so don't be too afraid of it. When it comes to using only LABEL, please read the RFC's first and do what they say. If this does not work with Evolution, fine, we will fix it in the Evo plugin. This is being done right now, but the other way around: If there is an ADR field but no LABEL, the latter is created. Otherwise Evo wouldn't show the address at all.
/Bo > Now when i write the ldap plugin i get the vcard where these values are > split apart into the properties like this: Post Office Address (first > field) Extended Address (second field), Street (third field), Locality > (fourth field), Region (fifth field), Postal Code (six field), and > Country (seventh field). For a correct handling i would have to parse > this back into the original address and then save it to the ldap server. > And if someone wants to sync with the ldap server i would have to take > this field (homePostalAddress) and parse it back into these 7 vcard > props probably with doubtable results... > > so here is my question: is it sufficient to provide the LABEL property > with the vcard, since this field already holds the address in clear > text? > > Armin > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Multisync-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/multisync-devel -- Bo Lincoln <[EMAIL PROTECTED]> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
