http://bugzilla.moblin.org/show_bug.cgi?id=5664





--- Comment #10 from pohly <[email protected]>  2009-08-27 07:21:41 ---
(In reply to comment #9)
> FN is blank, but N is populated.  I'm assuming that this isn't expected
> behavior.

I was expecting FN to be missing completely. Having it empty is unexpected. In
a way SyncEvolution and and Evolution do what the server is asking for: storing
and showing a contact with empty full name.

You said that Funambol 8 used to work. Can you contact Funambol and ask for
their opinion and motivation for this change?

> > SyncEvolution could fabricate a FN from the N components. What outcome would
> > you expect in such a case?
> 
> I'm assuming that this related to the indexing issue for names (First Last vs.
> Last, First) compounded by the fact that evolution doesn't break first and 
> last
> names apart.

Indeed, the application cannot really tell what the right composition of the
various name components is. It depends on the origin of the contact. In
Germany, N:Ohly;Patrick should become FN:Patrick Ohly. In China,
N:Zheng;Yanshuang should become FN:Zheng, Yanshuang (if I learned my lessons
well enough).

That's why I believe that FN should be treated as an independent property that
can be set by the user.

But perhaps your contact data doesn't have a FN and Funambol 8 was hiding that
by composing it for you on the fly? Just guessing.

> Is this a problem that should be resolve by SE, or is it properly addressed
> upstream at, *shudder*, funambol?

I think SyncEvolution should at least implement a fallback, because Evolution
and also the Contact GUI in Moblin have problems if the FN is missing. There is
no good solution, so I suggest that we go with "<first>[ <middle>] <last>" as
the FN fallback. This is also the fallback in the new logging code for
SyncEvolution 0.9.1.

-- 
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to