Version: 1.5.3 (using KDE 3.1.3) Installed from: SuSE Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB kmail's gpg integration is really great - the only thing that does not work is unicode (at least I guess it's a unicode problem as my system has de_DE.UTF-8 as encoding): German Umlaute and propably other non-latin chars are displayed correctly in konsole using gpg --list-keys - but they are displayed wrong in kmail (one Umlaut char is displayed as two other chars). Maybe this bug report already exists - but bugs.kde.org ignores keywords smaller than 4 chars (like gpg) when searching for duplicates.
Please tell me the key ids of the keys which cause problems. But please note that most likely those keys violate the OpenPGP specification which requires utf-8 encoding for user ids. Unfortunately all PGP implementations up to PGP 6 (at least) did use local encoding instead which leads to a lot of broken names. KMail shouldn't have any problems with correctly encoded user ids (and KMail 1.6 will have some heuristics to interpret broken user ids correctly). Furthermore please tell me the output of 'locale'.
Subject: Re: gpg unicode names not displayed correctly > Please tell me the key ids of the keys which cause problems. But please One ID is 0x5410D294 : It has the ü in it (Christian Stück). This key is displayed wrongly on the PGP key server, too. Maybe gnugp is wrong? A key which is displayed correctly on the key server site and in kpgp (which shows the same behaviour as kmail) is displayed wrongly in gpg on the "konsole" and vice versa. > note that most likely those keys violate the OpenPGP specification which > requires utf-8 encoding for user ids. Unfortunately all PGP implementations I do use utf-8 encoding on my system as you can see below (I don't know if I already used that encoding when creating the key with gnupg - but I believe I did). > up to PGP 6 (at least) did use local encoding instead which leads to a lot I use GnuPG. > of broken names. KMail shouldn't have any problems with correctly encoded > user ids (and KMail 1.6 will have some heuristics to interpret broken user > ids correctly). > > Furthermore please tell me the output of 'locale'. LANG=de_DE.UTF-8 LC_CTYPE=ja_JP.UTF-8 LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE=POSIX LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/iTO9aLqbjH7P7SgRAodUAJ9umidyPeF+zKexRrodpyjhoMh39wCgpdGT LcX0xj4WWslCLfOud6ocPIA= =A2jC -----END PGP SIGNATURE-----
Could this be the problem: $ gpg --search-keys 0x5410D294 (1) Christian St
Subject: Re: gpg unicode names not displayed correctly The output of 'gpg --list-keys --with-colon' is independent of the locale. I verified that KMail parses the user ids correctly independant from the user id. So we must do something stupid with the user ids somewhere else.
If this is still an issue: the same problem existed in KGpg and was fixed in r711018 (see bug:139276)
Can't find any problems with german umlaute in conjunction with gpg in kmail 1.10.1 so i asume that this is fixed.
I can confirm this works in 1.10.1. I have various keys with different encodings and I can see all of them display just fine.