Found some Evolution <--> Zaurus Contacts sync problems. Right now of 1151 contacts in the Z, only 384 survive the round trip Z -> Evolution -> Z. Here is what I've found so far:
1a. With this notes string on the Z, a contact will be synced as some
sort of empty/blank contact to Evolution (in Evo it appears like there
is a contact defined but no data: in my Evo address cards view, it's a
blank grey rectangle -- in which the name usually appears -- and nothing
more):
<Contact LastName="test" FileAs="test," Gender="0"
opie-contactfield-order="012_0_____" Uid="-1061300558"
Notes="a23456789112345678921234567893123456789412345678951234567896123456789712345aaa1:"
/>
It appears to have something to do with a string that:
starts with a letter
is approx >= 80 characters long
and has a colon around the 80 char mark
1b. Change the trailing "1:" to "a:" and the contact won't get synced
from the Z to Evolution at all (new items in Evo will get to the Z,
though).
1c. change the last "5" to an "a" so there are four a's ("aaaa") before
the "1:" at the sync from Z to Evo works alright for the other fields
(cursory check), except the Notes field is truncated and the last
surviving characters are changed to a "{"
before:
"a23456789112345678921234567893123456789412345678951234567896123456789712345aaa#a"
after:
"a2345678911234567892123456789312345678941234567895123456789612345678971234{"
2. As a separate issue, Multisync appears to be stripping out Opie's
"opie-contactfield-order" XML attribute from the <Contact> XML tag when
syncing data back to the Z.
My next test will be to strip the notes fields from all my contacts and
see how many survive the round trip -- it may just be the notes field
handling causing all the problems.
Martin
-- The price of freedom is eternal vigilance. The greatest dangers to
liberty lurk in insidious encroachment by men of zeal, well-meaning but
without understanding. [www.martindengler.com/privacy.html] intercept
software
signature.asc
Description: This is a digitally signed message part
