Noticed during release test. I think gpgtar is the issue here but I can't reproduce it on the command line as I can't pass utf8 on windows through the console, and my naive try to use "gpgtar --utf8-strings --extract -T filename.txt"
with filename.txt containing the filename utf8-encoded just shows the usage string.
To test create a folder with an umlaut, encrypt it with kleopatra. Then decrypt it. It works but it will have an invalid character in the folder name instead of the umlaut.
As the file is correctly decrypted I think the issue is with gpgtar which creates the output folder