Bug 277018 - wrong character encoding
Summary: wrong character encoding
Status: RESOLVED NOT A BUG
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 0.40 (KDE 3.x)
Platform: Unlisted Binaries Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-03 17:21 UTC by muabruns
Modified: 2013-05-10 06:44 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot of new outlook-email (35.47 KB, image/jpeg)
2011-07-03 17:21 UTC, muabruns 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description muabruns 2011-07-03 17:21:08 UTC 
Created attachment 61582 [details]
Screenshot of new outlook-email

Version:           0.40 (KDE 3.x)
OS:                MS Windows

The text of the Outlook-Menue (Outlook 2007) "Add inns" shows "Nachrichten verschl?sseln" instead of the correct "Nachrichten verschlüsseln".
This would be not a problem, if there were no other character-encoding-difficulties: Decoding Emails encoded under GnuPG v1.4.10 (GNU/Linux) leads to the error message "Fehler im UTF-8-Code".

Reproducible: Always

Steps to Reproduce:
There is nothing to do to reproduce the problem out of opening the Add Inns-menue of outlook 2007 or to recieve Emails encoded under GnuPG v1.4.10 (GNU/Linux)!


Expected Results:  
The german "ä", "ö", "ü" should be processed correctly.

OS: Microsoft Windows (i686) release 6.0 (Vista Professional)
Compiler: i586-mingw32msvc-gcc
Comment 1 muabruns 2011-07-15 20:46:04 UTC 
15.07.2011
Decoding Emails encoded under GnuPG v1.4.10 (GNU/Linux) leads to the error message "Fehler im UTF-8-Code" - vanished after reinstalling "gpg4win"-package.

Emails encoded under GnuPG v1.4.10(GNU/Linux)now are decoded correctly, out of the german "ä", "ö", "ü", which are deleted.
Comment 2 H.Schoenen 2013-03-23 18:46:40 UTC 
Same to me! My environment W7 64bit. Kleopatra 2.1.0
H.Schoenen, Dormund
Comment 3 Emanuel Schütze 2013-05-10 06:44:36 UTC 
This is a GpgOL bug, see https://bugs.g10code.com/gnupg/issue1247