After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 422553 - Adressbook insertion does not show umlauts correctly
Adressbook insertion does not show umlauts correctly
Status: RESOLVED DUPLICATE of bug 324604
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-25 09:23 UTC by Martin Jürgens
Modified: 2007-03-29 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
Screenshot of the behavior (35.42 KB, image/png)
2007-03-25 09:24 UTC, Martin Jürgens
Details

Description Martin Jürgens 2007-03-25 09:23:14 UTC
Please describe the problem:
The adressbook insertion when writing a mail does not show umlauts correctly. Instead, it shows ?=ISO-8859-1?Q? for example.

Steps to reproduce:
1. Add a contact to your adressbook that contains umlauts, for example Hans Dürf
2. Compose a new mail
3. Click on To in order to select a contact
4. Select the contact you just created (note, on the left side the umlaut is displayed correctly)
5. Click on "Add" to get the contact to the right side.


Actual results:
On the right side, then contact name is displayed with ?=ISO-8859-1?Q? in it

Expected results:
The contact name should be displayed like on the left side, with the umlaut.

Does this happen every time?
Yes.

Other information:
-/-
Comment 1 Martin Jürgens 2007-03-25 09:24:22 UTC
Created attachment 85249 [details]
Screenshot of the behavior

Attached is a screenshot of the behavior.
Comment 2 André Klapper 2007-03-29 16:47:46 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 324604 ***