[lucid-updates regression] escaping of contact names is broken

Thanks for reporting this bug and helping to make ubuntu better.

Can you try apt-cache policy evolution-data-server?
We tried to reproduce there on a French system to reply to a name with an umlaut and we don't get this issue.
Do you know exactly when it broke, was it working before last update?

also, does the issue happens in the composer or in the email sent?
Is it the case with any names with an umlaut?

seems similar to bug #596531

the issue could be due to bug #229187, I can't confirm the issue though, I tried to:
- create a contact name with space in the name and an email
- compose a new email
- clicked on the "to" button and pick the name in the list, clicked "add", and "ok"
- wrote a title and some text
- sent the email

the email source in the sent folder is correctly formatted and there is no error from the server

Ok, confirmed now with the sru updates

TESTCASE:
* compose an email
* write "One. Bug Email <bug@localhost>" in the to entry
* send the email
* go to the send directory
* check the email source

The email is "To: "One.BugE" <"mail bug"@localhost>" there

Uploaded in lucid-proposed:

evolution-data-server (2.28.3.1-0ubuntu4) lucid-proposed; urgency=low

  * remove debian/patches/92_git_return_formatted_address.patch:
    create a lot of issues with names containing a ". " as the recipient
    (LP: #595867)

TESTCASE:
* compose an email
* write "One. Bug Email <bug@localhost>" in the to entry
* send the email
* go to the send directory
* check the email source
-> The email should contain the sender name and address, NOT "To: "One.BugE" <"mail bug"@localhost>"

Accepted evolution-data-server into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I can confirm the issue with the current lucid-updates version and I can confirm that the issue is resolved after upgraded to the current lucid-proposed versions, evolution seems also to work correctly with that version and I've noticed no other issue

This bug was fixed in the package evolution-data-server - 2.28.3.1-0ubuntu4

---------------
evolution-data-server (2.28.3.1-0ubuntu4) lucid-proposed; urgency=low

  * remove debian/patches/92_git_return_formatted_address.patch:
    create a lot of issues with names containing a ". " as the recipient
    (LP: #595867)
 -- Didier Roche <email address hidden> Mon, 21 Jun 2010 14:22:29 +0200

Sorry for the trouble! I'm still trying to grok the code paths...

upstream reverted this change yesterday and fixed the api documentation and the bug the update tried to fixed by a fix in evolution

Thank, yes, I'm also following the upstream bug reports...

I was indeed mislead by the API documentation but I still think issues remain with the vcard export which is not so visible but probably not lucid material either.

The data structures used by evolution are still foreign to me.

This bug was fixed in the package evolution-data-server - 2.30.2-0ubuntu2

---------------
evolution-data-server (2.30.2-0ubuntu2) maverick; urgency=low

  * debian/patches/91_revert_formatted_adress.patch:
    - create a lot of issues with names containing a ". " as the recipient
      (LP: #595867)
  * debian/patches/92_crash_on_format_itip.patch:
    - don't crash when receiving a new event email
 -- Didier Roche <email address hidden> Mon, 28 Jun 2010 11:22:46 +0200

If this bug was fixed in the package evolution-data-server (2.30.2-0ubuntu2) maverick, why can't I see it in lucid?

Wait, i mean... when will 2.28.3.1-0ubuntu4 get pushed to lucid-updates? Right now the latest is 2.28.3-0ubuntu10.