[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: Bug#35614: KMail do not interoperate properly with GnuPG, when key contains nonASCII characters
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2001-12-01 13:26:01
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 01 December 2001 03:37, kulakow@ceti.pl wrote:
> I create PGP key using GnuPG. This key contains some iso8859-2
> characters, namely "³" (twice). I tried to do this in 3 ways:
> a)passing an --charset iso-8859-2 option to GnuPG, b) passing utf-8,
> c) with no additional options. KMail does nothing when asked to
> encrypt/sign with this key. What's more when I try to attach this key
> using an 'Attach Public Key' option, i get the "Could not attch
> public key, perhaps its format is invalid(e.g. key contains umlaut
> with wrong encoding)" message. Option 'Attach My Public Key' works.
> Additionally, the nonASCII characters are displayed as '?' in the
> popup menu.
>
> Encrypting/signing from a command line works. It also works when I
> use KMail with a key generated without these characters.
>
> AFAIK GnuPG uses utf internally and I have problems with the key I
> created myself, so I suppose this is not the same problem as the ones
> with PGP/GnuPG compatibility (already closed).

All charset related problems are fixed in the developer version (it will 
be in KDE 3).
For now you will have to add a second user id to this key pair which 
doesn't contain any non-ASCII characters.

Regards,
Ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8CNppGnR+RTDgudgRAjESAKCUYTM7L1KQChem47sj5YVuUWUWPgCgo61U
BjtaTUkFv6iOhh/ODMNP2kA=
=0asN
-----END PGP SIGNATURE-----
_______________________________________________
kmail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]