Bug 475508 - Wrong key encoding
Summary: Wrong key encoding
Status: REPORTED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-12 09:18 UTC by j.marce.igual
Modified: 2023-10-12 09:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Issue showing the rendering of the characters on terminal and Kleopatra (39.18 KB, image/png)
2023-10-12 09:18 UTC, j.marce.igual 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description j.marce.igual 2023-10-12 09:18:14 UTC 
Created attachment 162243 [details]
Issue showing the rendering of the characters on terminal and Kleopatra

SUMMARY
When I create a key with Kleopatra under Windows with special characters (èáë) it shows properly in Kleopatra but the characters are not shown properly when running gpg -K. The opposite is also true.

STEPS TO REPRODUCE
1. Create a pair key with Kleopatra and use special characters "èáä"
2. Read the key from the terminal using gpg -K
3. Key shows with weird characters

OBSERVED RESULT
I've attached a picture showing the issue. The characters are not printed properly.


EXPECTED RESULT
The characters are printed properly whether it's in Kleopatra or in the terminal.


SOFTWARE/OS VERSIONS
Windows: 11 22H2 OS Build 22621.2283
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.9
Kleopatra version: Gpg4win-4.2.0