Hi everyone, a while ago I "fixed" opie_sync to transmit the FN property for vcards generated from opie-addressbook data and a patch for adding LABEL is pending Tom's approval.
My reasoning behind this was that Evolution does not actually display the full name nor the address, unless FN and LABEL are set. When first editing (or even only confirming) the data in the appropriate dialog, Evolution will (re)create those properties. When Armin was faced with the same problems in his Palm plugin I lightheartedly suggested he do the same but I have now come to realize that I applied the "fix" in the wrong place from the start: 1.) opie-addressbook does not have a property equivalent to the vcard LABEL, nor does opie-sync do anything with them when receiving vcards to sync to the opie device. 2.) Evolution has a a hard-wired layout for LABEL (which kind of beats what the point of a label should be), so by catering for Evo's peculiarities inside of opie_sync, other software might end up having their nicely configured label entries broken. 3.) When doing the exact same thing in two different places, IMO one is likely doing it in the wrong place altogether. Plus, there might be more devices supported in the future that would require the same fixes. So, to me it is suddenly painfully obvious that the evolution_sync plugin should take care of adding LABEL and/or FN if and when needed. As I jumped the gun before in making the "fixes" where I made them, I'd appreciate some comments on whether or not what I just wrote makes some (or, hopefully, a lot of) sense. TIA, Eike -- Eike M. Lang <[EMAIL PROTECTED]> ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
