Bug 205672 - Umlaut import issues when using Import (from KMail it works)
Summary: Umlaut import issues when using Import (from KMail it works)
Status: RESOLVED FIXED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-08-30 11:59 UTC by Carsten Niehaus
Modified: 2018-09-19 14:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Niehaus 2009-08-30 11:59:25 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    SuSE RPMs

I recieved a vCard with ~140 Persons. Many of them have ß or Umlauts (öäüÖÜÄ) in their names. When I save the .vcf file and import it in KAddressbook I am getting names like

"Fabian M�nnich"

The � should be an "ö". This is the same for every Umlaut.

When I click on "import contact" in KMail, the Person is correctly imported into KAddressbook (but of course I won't import 140 persons by hand). Therefore I guess that there are two code-path', one that works and one with an UTF-8 issue.

A contact looks like this (I removed some lines):


BEGIN:VCARD
PRODID:-//KGS Rastede//vCardExport 1.0//EN
VERSION:3.0
N;CHARSET=UTF-8:Böker;Michael;;;
FN;CHARSET=UTF-8:Michael Böker

<snip>

X-OUTL-IMADDRESS;CHARSET=UTF-8:
CATEGORIES;CHARSET=UTF-8:KGS
REV;CHARSET=UTF-8:20090829T000010
END:VCARD



You can have the full .vcf-file as a private mail if you want, but I cannot add it to the attachemant as it contains real data of real persons.
Comment 1 Tobias Koenig 2010-01-10 00:07:37 UTC
Hej Carsten,

can you send me one vcard file for testing, please?

Ciao,
Tobias
Comment 2 Andrew Crouthamel 2018-09-19 14:28:05 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.