Actually, Gmail supports any text you want in the name field. The
problem comes with parsing and comparing structured names (AB) to
unstructured names (Gmail). Syncman only ever uses the first and last
names when constructing the name to use in Gmail. This decision was
made mainly because it was easier and less prone to errors. However,
now that Syncman is pretty proven and stable, I can revisit utilizing
the other name fields (middle, prefix, etc). I'll add that to my
Hope that explanation wasn't too technical, if you still have
questions I'd be happy to try again.
Also, I'd love to hear about the other issues you are having, even if
they are problems on the Gmail side.
Thanks for your feedback,
Yeah, your experience with addresses is the reason I waited so long in
the first place to add support for them. In short, addresses going
from AB to GM should turn out perfect while from GM to AB could have
strange results. I don't have time at the moment, but I'll give a
more thorough explanation tomorrow of what's actually happening.
A quick follow up, especially since I think having a better
understanding of what Syncman is doing will help everyone use Syncman
to its fullest potential.
So... The underlying problem is that AB uses structured addresses with
GM uses freeform addresses. Therefore, syncing addresses from AB to
GM is straightforward and will always yield good results. Syncing
addresses from GM to AB is something else entirely.
Parsing freeform addresses is a notoriously difficult problem and
unfortunately well outside of the scope of a small project like
Syncman. Therefore, when adding support for addresses, I made the
decision to not attempt this at all (rather than have something that
was broken for a large percentage of cases).
What I do with Syncman is to break down the freeform address into a
structured address in a way that when it is converted back into a
freeform address it is the same as the original. This strategy
enables synchronization to work all the time, with the consequence
that addresses added and/or modified on GM might not be 'parsed'
correctly in AB.
Wow, this is a long mail. Maybe I should get to the point. Addresses
should ideally be added or modified in Address Book. I'll try to
gradually add more intelligence to the address parsing, but it will be
step by step and definitely won't solve all issues immediately.
If you made it this far, I salute you. And if you're still interested
and have any more questions, I'd be glad to answer them... in 2 weeks
when I'm back from vacation. :-)