Ticket #289 (assigned defect)

Opened 2 years ago

Last modified 2 months ago

modification: ignore spaces in phone numbers

Reported by: lesid Assigned to: dfriedrich (accepted)
Priority: high Milestone: 0.41
Component: OpenSync Version: 0.35
Severity: blocker Keywords:
Cc:

Description

In kdepim, I saved my numbers as +41 761234567 (the space is required by outlook, which I synced with Plaxo of which I imported the data into kdepim using an ldif file). When syncing with the empty address book of the SE k750i, the number is saved as +41761234567. When I sync again without making further changes, opensync reports a conflict and asks what to do. It would be nice, if such a difference was ignored automatically, since pressing i for ignore for 300 contacts takes quite some time.

Change History

08/22/06 21:17:44 changed by dgollub

Maybe we should really add a special compare function for phone numbers or/and other fields. Also the gnokii-sync plugin requires something similar because it can only handle some few characters for telephone number (example: +49800/123456 - '/' is not allowed for gnokii-sync).

So there will be also a conflict with: +49800123456 != +49800/123456

But maybe this should be done for the dev-branch.

09/07/06 18:32:32 changed by abauer

  • status changed from new to assigned.
  • version set to 0.31.

10/15/07 23:30:42 changed by dgollub

  • owner changed from abauer to dfriedrich.
  • priority changed from normal to highest.
  • status changed from assigned to new.
  • severity changed from normal to blocker.

Maybe we should implement "weak compare" handling for specific fields like phone numbers. This would require changes on xmlformat_compare function - to provide such "weak compare field" hook tables...

Daniel, something for 0.40?

12/26/07 17:57:36 changed by dfriedrich

  • priority changed from highest to high.
  • status changed from new to assigned.
  • version changed from 0.31 to 0.35.

We also could implement a customizable auto format function for some fields. Which could be global enabled/disabled. But a special compare function will be better, so we do not touch the data. But we should search for a clean solution that we can register special compare function for some formats.

01/20/08 10:48:09 changed by felixmoeller

http://www.opensync.org/ticket/338 might be closed as a duplicate, if we are aiming at a generic compare function.

08/03/08 14:21:21 changed by tuju

  • milestone set to 0.38.

08/20/08 09:45:16 changed by dgollub

What about introducing for xmlformat_compare() compare function pointer for certain fields. We might register those function pointer with the score table - to allow per field a special compare function, which does some "weak" comparsion - e.g. for Telephone numbers and spaces. So the return value of the compare function is the same like xmlformat_compare(): SAME, SIMLAR, MISMATCH ... and we might subsctract one score point or something like that. OTOH - this is anyway onl requried for SlowSync? - right? So if someone tries to change the space or + in a telephone number intentionatly this should not cause call of xmlformat_compare()...

Any volunteers?

08/23/08 18:35:56 changed by dgollub

  • milestone changed from 0.38 to 0.41.

(Unfortutanley dfriedrich is on vaction walking down the Jakobs-path somewhere in Spain. I fear there is not Wifi... reschedule for post 0.40)

10/04/08 22:06:33 changed by Lavrinenko

This should be fairly easy to implement: 1. get contact's number from mobile device 2. get contact's number from gnokii/kdepim/etc 3. remove any non-digit letters from 1) and 2) 4. compare 5. return match/mismatch