Re: [Opensync-users] Problems with syncing SonyEricsson P910i and Evolution

[Armin B. <arm...@de...>]

Stian Jordet wrote:
> Hi, Armin.
>=20
> Armin Bauer wrote:
>> ok. i can see the problem now. the cause of the problem is that evo2
>> stores the name in 3 ways:
>>
>> - the N value, where each name part is separated by a ;
>> - The FN (formatted Name) which is something like "firstname lastname"=

>> - the fileAs attribute which is "lastname, firstname"
>>
>> the problem is: which one should i use?
>>
>> if i either use FN or fileAs to other one would be lost during the syn=
c
>> (or i have to regenerate it in the evo2 plugin)
>=20
> Good question. It seems the P910 only uses the N value? Is that what
> other phones are doing as well? So perhaps the problem is with Evo2? Or=

> is it a phone bug?
>=20
> Either way, it would be (very) nice with an option to "create" the othe=
r
> two fields from the N value on my phone... But you know this best.

yes, i can generate the value from the N field. The problem appears if a
user changed the fileAs attribute in evo2.

lets say someone replaced the fileAs attribute with which was "Doe,
John" before with "John". If we would generate the fileAs attribute
during the sync we would overwrite this change again with "Doe, John".
Dont know if there is a easy solution to this problem. I guess the best
approach would be just to generate these fields and hope not too many
people fill in custom values.

>=20
>> this was a bug in libsyncml. i fixed it now in the dev branch of
>> libsyncml. please run:
>>
>> svn switch http://svn.opensync.org/libsyncml/branches/6620-branch .
>>
>> in the main libsyncml directory to switch to this branch.
>>
>> please let me know if this problem is fixed then.
>=20
>=20
> I'll test this after work :)
>=20
> Thanks!
>=20
> Best regards,
> Stian
>=20