- User Since
- Sat, Nov 19, 11:16 AM (2 w, 1 d)
Fri, Nov 25
Interestingly enough if I set LC_LCTYPE environment variable in powershell $env:LC_CTYPE = "C.UTF-8" - it behaves correctly and generates UTF-8 encoded names.
Just found out something weird - powershell tells me the default characterset is iso-8859-1
PS C:\Users\bbs> [System.Text.Encoding]::Default
okay, installed 2.2.29 and tried showkey:
C:\Users\bbs> gpg.exe --show-key D:\bbs_gpg.public.pgp pub rsa4096 2022-11-06 [SC] 0F20E48DEA9FD7A5626DBA0067BDA85044042E3B uid BjÃ¸rn Bouet Smith <firstname.lastname@example.org> sub rsa4096 2022-11-06 [E]
Yes, seems so. In either case, there's nothing we can do anything about since the versions provided by us appear to work correctly.
But it is strange that the version can show the characters correctly - so it can encode and decode to the same output.
I am not sure if the export is correct - or if you need something else?
If I import the keys into gpgwin it shows up garbled - both in the console version of gpg.exe and Kleopatra, but if I run
With the old gpg version it shows up as:
/c/Users/bbs/.gnupg/pubring.kbx ------------------------------- pub rsa4096 2022-11-06 [SC] 0F20E48DEA9FD7A5626DBA0067BDA85044042E3B uid [ultimate] Bjørn Bouet Smith <email@example.com> sub rsa4096 2022-11-06 [E]
This is the key exported with:
gpg.exe --output D:\bbs_gpg.public.pgp --armor --export firstname.lastname@example.org
It seems like gpgwin generates keys where the name are not compatible with each other.
Also - gpgwin is no better:
So because I use some thing that "almost everyone does not use" - but something that you distribute you do not even want to fix it?