On Sun, 22 Aug 2004 03:03 am, Tom Foottit wrote: > Agreed that something like this should be done. There are a lot of > "frindge" pieces of data like this that are not part of vCard but are used > in various programs. Currently we only deal with the Evolution ones since > everything has always revolved around Evo. As that changes I agree that we > need to have a mapping scheme for these non-standard fields.
This scheme, if adopted, will require cooperation/coordination between the plugin developers if it is to be successful, particularly in the introduction phase. So first thing is to get everybody's agreement. Presuming everybody agrees, next thing to do is designate (and maintain) an official list of X-MULTISYNC-<nnnn> tags. I suggest the plugin developers howto is a good place for it. The howto can be put into CVS, under multisync/docs, so that all developers can add to it as required. > Seeme to me that we usually encode as "\n", but I'll have to and check to > be sure. I'll get back to you on this. yes please. > Would you like me to put this up on the website? yes please. -- Stewart Heitmann <[EMAIL PROTECTED]> ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
