-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, I'm using Enigmail 1.9.1 with gnupg 2.0.30 under Windows 8.1. If I e.g. update my keys by the command line I get gpg: fordere Schl³ssel 8ABDF3D7 von hkp-Server keys.gnupg.net an but in the widow log "Enigmail Meldung" that is shown if I update the keys within enigmail I only get gpg: fordere Schl ]ssel 8ABDF3D7 von hkp-Server keys.gnupg.net a The encoding is wrong in both cases (the umlaut in "Schlüssel" is displayed wrong) but this is an gnupg problem (I already mentioned it on o their mailing list as part of an other problem https://lists.gnupg.org/pipermail/gnupg-users/2016-May/055931.html , unfortunately till now without any reply). But in enigmail additionally the last letter ("n") is missing. This is not only the case in the above example but also in other messages and also where the last character is actually important. I already wondered why enigmail processes only 2 of the 21 keys in one of my keyrings as it shows "gpg: Anzahl insgesamt bearbeiteter Schl ]ssel: 2" (total number of keys that were processed : 2). If I run it in the command line it gives gpg: Anzahl insgesamt bearbeiteter Schl³ssel: 21 (total number of keys that were processed : 21) which makes much more sense :-) Maybe there is some off-by-one-error in the way enigmail processes the strings (maybe due to the special characters)? Kind regards, Hauke -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlcxDRUACgkQjz8jfoq989eu8wCePRjLl/WqDsTGKNjIR6hl3uIO quQAn0TQ+5BxZIThaNd0wW2gnIgKk4b7 =mvIw -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
