http://bugzilla.meego.com/show_bug.cgi?id=666
Summary: X-OSSO-BOUND property on Maemo
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
OS/Version: IA
Status: NEW
Severity: enhancement
Priority: Low
Component: Maemo 5
AssignedTo: ovek(a)debian.org
ReportedBy: jingke.zhang(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-maemo5-bugs(a)meego.bugs
Estimated Hours: 0.0
This issue is from BMO#1985 (
http://bugzilla.moblin.org/show_bug.cgi?id=1985)
This was originally reported on January 07 2009 by a Chris Davis against
SyncEvolution 0.8.1. It wasn't possible to do anything about it then, but now
the situation is different.
X-OSSO-BOUND is a local extension used by the Maemo address book. It links
certain parts of a contact with instant messaging accounts on the device.
Here's an example:
BEGIN:VCARD
VERSION:3.0
N:zzTestlast;zzTestfirst
UID:pas-id-9999999999999999
X-JABBER;X-OSSO-BOUND="john@gmail.com":firstjabbertest@BLAH.COM
X-JABBER;X-OSSO-BOUND="bar@gmx.de":secondjabbertest@blah.com
X-AIM:firstaimbuddy
X-AIM:secondaimbuddy
X-YAHOO;X-OSSO-BOUND="firstyahooaccount":firstyahoo
X-YAHOO;X-OSSO-BOUND="firstyahooaccount":secondyahoo
X-MSN;X-OSSO-BOUND="firstmsnaccount":firstmsn
X-MSN;X-OSSO-BOUND="secondmsnaccount":secondmsn
EMAIL;X-EVOLUTION-UI-SLOT=1;TYPE=PREF;TYPE=INTERNET:test@blah.com
EMAIL;X-EVOLUTION-UI-SLOT=2;TYPE=INTERNET:testtwo@blah.com
END:VCARD
ScheduleWorld kind of supports preserving such extensions, so it was possible
to synchronize the properties to Evolution on a desktop, but the Evolution GUI
removed it when editing such a contact. Other servers or clients might not
support it at all.
Chris suggested to map the property to non-standard TYPE values. I'm not so
sure about that, because this information doesn't seem to be useful outside of
the device.
With Synthesis we can change SyncEvolution so that the X-OSSO-BOUND value is
never sent to anyone else and preserved when receiving an update for the item:
the internal field list needs to be extended to hold the value and the datatype
definitions for the Evolution side needs to be different from the one used for
peers: the one for Evolution needs to support X-OSSO-BOUND, the other must not.
--
Configure bugmail:
http://bugzilla.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.