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





--- Comment #11 from jfrorie <[email protected]>  2009-08-27 08:30:49 ---
(In reply to comment #10)
> (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?

I think I know the source of the problem.  I think the server is doing what
it's supposed to.  It's the blackberry client that is dropping the ball.

I have a diverse installation.  I run a blackberry, linux laptop and Windows
desktop.  Because of the raging incompatibilities between the clients, I use
the BB as the canonical data source.  When I did the upgrade, I started by
refreshing from BB to server to clear out birth date issues.  I just verified,
while the names are populated, the Display Name on the Funambol web app is
blank.  I can't believe I didn't catch this.  I'm thinking the upgrade to 7.2.3
might have exposed this, but I can't find an OTA 7.1.x link to verify it.

> 
> 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.

That should work well, although I find it painful that you have to implement
something because of someone else's bug.

-- 
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