GpgOL: Broken Umlauts in progress message (unicode, encoding)
Closed, ResolvedPublic

Assigned To
Authored By
• ebo
Sep 30 2024, 11:07 AM
Tags

Description

The broken messages are the German versions of "Resolving recipients..." and "Encrypt…" in the progress windows:

Details

Version
gpg4win-Beta-50

Event Timeline

I wonder if this has to do with T5960: Kleopatra: Encoding problems with GnuPG output on Windows as this is a recent regression. The Umlauts are ok in Gpg4win 4.3.1

• ebo renamed this task from GpgOL: Broken Umlauts in Resolver message to GpgOL: Broken Umlauts in progress message.Sep 30 2024, 11:20 AM
• werner added projects: i18n, vsd33.
• ebo renamed this task from GpgOL: Broken Umlauts in progress message to GpgOL: Broken Umlauts in progress message (unicode, encoding).Nov 4 2024, 4:16 PM
• ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Nov 5 2024, 1:31 PM
• ikloecker changed the task status from Open to Testing.Nov 5 2024, 1:45 PM
• ikloecker claimed this task.
• ikloecker moved this task from Backlog to WiP on the vsd33 board.

I have reverted the commit mentioned by Carl and another text codec related commit for the Qt 5 builds. This will hopefully fix the broken umlauts in the progress messages.

There's no special branch for VSD 3.3 so that no backporting is necessary.

• ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Nov 8 2024, 2:09 PM
• ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

Gpg4win-Beta-75:

The umlauts are ok again!

• ebo edited projects, added vsd33 (vsd-3.3.0); removed vsd33.