This has loong been resolved.

Should be fixed in the next version.

This has been commited with 0fecf066e3c944b8ce590d9a805c1ac93ba74d71 5c82f133bd68215a12d852d2ed6782e20d27f783

This has been added and released with Gpg4win-3.1.15

Hi, thanks! I've converted the README to gbk encoding as this was the encoding we had used for the installer before we switched to UTF-8, we use local8bit encoding in the README files to be compatible with Notepad.

We have this.

Modified and commited with: rev. 2859eddfb0c935d3f9eb9ccc1b42c121621123e9 I'm not sure if phabricator automatically does it when I mention the differential as GnuPG-Bug-Id

Thanks for noticing, I did not have Qt4 on my radar when writing this. The delayed raise with the timer might be only necessary on windows, on linux we don't have reports that just doing an activateWindow and raise does not work. So this is mostly for windows and there the Qt4 pinentry is not relevant.

obsolete

That says "Interface not supported" when GpgOL is trying to obtain some data from Outlook. AFAIK this can only happen if the server is either not a Microsoft MAPI server like OpenExchange or KOPANO or so. But even these two are known to work.

Thanks for the report. Some time ago I wrote the code in a way that when setting the HTML body failed it would fallback to the plain body, regardless of the preferences:
So even though there is an error that error is handled. https://dev.gnupg.org/source/gpgol/browse/master/src/mail.cpp;4d57033a095aecf8529606428efef6af466f1196$1488

The related qt bug is: https://bugreports.qt.io/browse/QTBUG-83365

Argh! I had added the translation to GpgOL but forgot to list the file in our installer. So it will only be part of the next version.

Thanks for the feedback

I set it to Normal priority. It would be good to find out what exactly is the problem with this key so that we can fix this in kleopatra and handle it.

The about dialog where it tells unknown windows version means it's Gpg4win-3.1.13 (the only version affected by T5056 )

Released

I've tested this before the Gpg4win release and it worked as expected. Thanks.

Reopening this as I have seen such hangs multiple times during testing. When importing multiple keys with Kleopatra at once this can be reproduced sometimes.

Long since resolved

Noteworthy changes in Version 3.1.15 (unreleased)

We discussed this, the proper solution will be for gpgtar to accept unicode arguments on windows.

We are hoping to have at least a beta release soon with gcrypt 1.9 that we can put in a Gpg4win-4 beta.

This works with the message class changing. We still need to do it for OpenPGP, too.

The problem is not with creation, that works. The problem is also not with files contained in the archive, they also work. The problem is the archive name. And that also seems to be correct in the way gpgtar extracts it as gpgtar successfully extracts the archive, but the created folder name has the broken character.