After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613259 - Evolution Mail: google-contact synchroni...
Evolution Mail: google-contact synchroni...
Status: RESOLVED DUPLICATE of bug 602244
Product: evolution
Classification: Applications
Component: general
2.28.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2010-03-18 17:19 UTC by Kilian Klaiber
Modified: 2013-09-13 01:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Kilian Klaiber 2010-03-18 17:19:50 UTC
google-contact synchronization incomplete and buggy:

1. Not all information from google contact is downloaded to evolution. For example, the field "company" is not synchronized at all with evolution.

2. If you simply enter the company name in the google name field, this is what happens: The google name field does not discriminate between first and second names. However, this is automatically done in evolution. However, if you enter a company name, then the first part is treated like the first name and the last part, for example ltd is treated like the last name. In the end, you get a whole list of companies all listed under limited, ....

For example: BMW Ltd in google contact is going to appear as
			Ltd, BMW in evolution, because evolution thinks BMW=first name, Ltd=last name.

I hope you get my drift. The nitty gritty is: There is no reasonable way to synchronize company names and respective addresses between google and evolution.

I hope this is of interest and possibly of help to you!

Regards


Distribution: Ubuntu 9.10 (karmic)
Gnome Release: 2.28.1 2009-11-03 (Ubuntu)
BugBuddy Version: 2.28.0
Comment 1 Akhil Laddha 2010-03-19 03:29:19 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 602244 ***