AW: problem with german umlauts
hi Ben, you wrote on So, 14.Nov.2010 (02:13:47): On 14/11/10 12:35 AM, Reinhard Irmer wrote: you.wrote on Fr, 12.Nov.2010 (20:10:57): On 13/11/10 5:16 AM, Reinhard Irmer wrote: [...] Now I will test ist out setting charset iso-8859-1 in gpg.conf for version2. Here are the results: [...] Using GnuPG v.1.4.11 with Thunderbird as client charset must be utf-8 to show correct umlauts This makes some sense, Thunderbird needs to be told which character set to use (most will default to iso-8859-1, but it depends on the version installed). I've set it to utf-8 Using GnuPG v.2.0.16 using all possible charsets, 40tude shows correct umlauts, but Thunderbird always shows questionmarks instead of german umlauts You should be able to change the Thunderbird setting to UTF-8 and make it behave in View - Character Encoding. View utf-8: umlauts in body or utf-8-characters in body are OK, umlauts in headerpane are destroyed (shown as ? in black square) View iso-8859-1: umlauts in body are OK, utf-8-characters in body are destroyed (o¿o) = (o¿o), umlauts in headerpane are OK -- regards Reinhard --- [on OUTLOOK2007 with QF-Macros] --- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpg key generation options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have installed gpg version 1.4.10 , the last I think. When I run --gen-key the menù display 4 voices while the guide and manual saw on gpg web page show only 3 voices. Maybe the online documentation is out of date ? My final problem is to get an explanation of fourth voice RSA and RSA , why I can't encrypt a file with a key pair generated with this option ? thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJM3xcrAAoJEMomimwKQvQirbMQAIS0OQNtBfRCPo6a1Sr3Kz3q wQLrsksywRZMA/ijLGZEK7PtM8vW+xG11VeR+4NXl2Bqv/tAbc0sEVWjA+K+1tHJ KUX0R3pDBwCcvtyUw5ebpEIjAIDoc0CJMsJJdVkMqUvepyynx34SGCC2RaN5Ir5E Qc6voZkpnX92ZPHNHaNOkmKp8vSOX5Yt9HfEC+1kPhsyBjHe/OM0wr4Z+mJImPQz n5rHHKS8Q8V60lfC/z06Bm1yEK/nDTBXHytMYi1WOx4eNbrHShcmJv6P7GrVn4k5 ZQUYpfiUSSu0JZP+vyjFp1JkVKgGK4u+Jr79YpwZldFxGSyZwN+8MrxQHlSNe5pF O6a8E/F+nIkECh4CMtvqrsP8uaiZnk5p3RznEOGJMTa4d9JvBX4R2mB6y+Fa+MjP DdgU5aAU7RXtnTRpAIMgoVBByNP4s/MgihJdNDH1pRkjdjim7IJslBosNsfy5+6q nlWsLJstZ2hu2wh7vjOf6ExvqbAAVqi9SJJHClSuWAXug+UEx4g3WiSk1otyO6z2 KvP3tIvCKXO2Yl4OTbOT3YBuHWx6NZ42jaSwNlzT2cfdbvHPLF8MGqoB3ianUiDU 1QPgNm0gnfyPFqzs/l8f9L6OgUPabsg7rWbNTTaDmFMe4dWN+n7qaYf+oZFEEIK4 BVHRuAsuyghDch8HTwdG =6TYA -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: AW: problem with german umlauts
On 14/11/10 8:52 PM, Reinhard Irmer wrote: you wrote on So, 14.Nov.2010 (02:13:47): You should be able to change the Thunderbird setting to UTF-8 and make it behave in View - Character Encoding. View utf-8: umlauts in body or utf-8-characters in body are OK, umlauts in headerpane are destroyed (shown as ? in black square) View iso-8859-1: umlauts in body are OK, utf-8-characters in body are destroyed (o¿o) = (o¿o), umlauts in headerpane are OK Okay, what about the preferences for Thunderbird? I'm assuming you're using Windows for all these, in which case go to Tools - Options - Display - Formatting - Advanced. Character Encodings for both outgoing (composition) and incoming mail are set here (I'm assuming that your setting was only in the View - Character encoding section). You'll want this to match everything else (although it shouldn't matter if View - Character Encoding resets itself to ISO-8859-1 if the other two are set to UTF-8). Regards, Ben signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg key generation options
Francesco Savino wrote the following on 11/13/10 5:54 PM: I have installed gpg version 1.4.10 , the last I think. The current release for GnuPG is 1.4.11, and 2.0.16 for gpg2. But I believe 1.4.10 is fine too. My final problem is to get an explanation of fourth voice RSA and RSA , why I can't encrypt a file with a key pair generated with this option ? In Terminal choice number (4) is: Please select what kind of key you want: (1) RSA and RSA (default) (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) That is: RSA (sign only). As its name indicates, it's only for signing, you can't use it for encryption. As for RSA and RSA choice number (1), I ran a test, and generated an RSA keypair, that includes an Encryption subkey. Regards, Charly MacOS 10.6.5-MacBook Intel C2Duo 2GHz-GnuPG 1.4.11-MacGPG 2.0.16 Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 - Running Enigmail version 1.1.2 (20100629-1412) ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
AW: AW: problem with german umlauts
Hi Ben, you wrote on So, 14.Nov.2010 (11:19:07): On 14/11/10 8:52 PM, Reinhard Irmer wrote: you wrote on So, 14.Nov.2010 (02:13:47): You should be able to change the Thunderbird setting to UTF-8 and make it behave in View - Character Encoding. View utf-8: umlauts in body or utf-8-characters in body are OK, umlauts in headerpane are destroyed (shown as ? in black square) View iso-8859-1: umlauts in body are OK, utf-8-characters in body are destroyed (o¿o) = (o¿o), umlauts in headerpane are OK Okay, what about the preferences for Thunderbird? I'm assuming you're using Windows for all these, in which case go to Tools - Options - Display - Formatting - Advanced. Character Encodings for both outgoing (composition) and incoming mail are set here (I'm assuming that your setting was only in the View - Character encoding section). You'll want this to match everything else (although it shouldn't matter if View - Character Encoding resets itself to ISO-8859-1 if the other two are set to UTF-8). I'm not so familiar with TB because my favourite client is 40tude-dialog, where everything works fine. I only tested the probs with TB to see,if there are differences in showing the characters. I had set the options in TB for incoming/outgoing msgs. to iso-8859-1; now I changed to utf-8 and now I will see, if problems getting solved with this. When I have results I'll tell you. -- So long Reinhard --- [on OUTLOOK2007 with QF-Macros] --- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: AW: AW: problem with german umlauts
On 15/11/10 7:01 AM, Reinhard Irmer wrote: I'm not so familiar with TB because my favourite client is 40tude-dialog, where everything works fine. I only tested the probs with TB to see,if there are differences in showing the characters. I had set the options in TB for incoming/outgoing msgs. to iso-8859-1; now I changed to utf-8 and now I will see, if problems getting solved with this. When I have results I'll tell you. Cool, I just double-checked in a couple of other messages, one in this thread and one in another list, and TB has no problem displaying umlauts in both the body and in the headers (From field). The characters checked were ö and ü. With UTF-8 it also has no problem with most other characters incorporated in the unicode character set (this can sometimes be affected by additions to unicode after the release of the operating system or software used). Somewhere around here I've got an auto-response to a mailing list in Chinese with the Chinese characters in both the headers and the body. In that case I was able to copy those characters into Google's translation page (which is how I know it was an auto-response) and paste my own translated response to it. All of this displayed fine in Thunderbird, even though I didn't use the unicode codes when I entered my response. Regards, Ben signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
