Hi Stewart,

On Sat, 21 Aug 2004, Stewart Heitmann wrote:
<snip>
> I have'nt done anything to try and fix this in the kdepim_plugin because that
> requires putting Evolution-specific code into my plugin and I didnt think that
> is very wise.

Agreed.

> I think it would be wiser if the multisync team developed its own list of
> multisync-specific proprietry fields that acted as intermediates for
> mapping the various proprietry codes used by each plugin.
>
> For example, kdeplugin could map X-KADDRESSBOOK-X-AssistantsName
> to an agreed multisync-proprietry code, such as X-MULTISYNC-ASSISTANT,
> and evolution plugin could do the same with X-EVOLUTION-ASSISTANT.
> That way both plugins can happily exchange plugin specific fields without 
> knowing details of the other.
> I imagine the multisync team adding to this list of proprietry codes as
> required, but I suggest the following intermediates as a start
>  X-MULTISYNC-OFFICE 
>  X-MULTISYNC-MANAGER
>  X-MULTISYNC-ASSISTANT
>  X-MULTISYNC-SPOUSE
>         X-MULTISYNC-PROFESSION
>  X-MULTISYNC-ANNIVERSARY
>  X-MULTISYNC-DEPARTMENT
> Any comments from the dev team???

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.

> 
> Secondly, kdepim_plugin sends multiline data out with the newline encoded as
> "\n" (two chars) because thats what KDE Addressbook gives me.
> However the evolution plugin doesnt decode the newlines at all so they are
> visible in the data. I guess this is my fault for sending the wrong thing.
> How exactly is outgoing multi-line data supposed to be encoded anyway?
> Anyone got any code I can cut and paste. I am running short of time these days 
> so any hints would be appreciated. 

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.

> 
> Apart for the newline bug, the kdepim_plugin is nearly ready for
> releasing into the wild.
> Linux x86 users may wish to try the rpm attached, otherwise source code
> is availabe under CVS (tag = branch_08X)
> 

Would you like me to put this up on the website? It will probably get a 
bit more testing that way if you are ready for it.

Tom




-------------------------------------------------------
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

Reply via email to