| Summary: | Wrong key encoding | ||
|---|---|---|---|
| Product: | [Applications] kleopatra | Reporter: | j.marce.igual |
| Component: | general | Assignee: | Andre Heinecke <aheinecke> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | mutz, pim-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Issue showing the rendering of the characters on terminal and Kleopatra | ||
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