chiffre is German (and possibly French?) for "cipher" (http://dictionary.reverso.net/german-english/Chiffre). Attach an encrypted file. Personally, I love the linguistics and I'd like to see future versions keep "chiffred", but the English localization should, probably, unfortunately, read "encrypt & attach a file". Maybe keep "chiffred" (it's so succinct), and add some roll-over text with the longer translation.
2 2007-05-21 16:40:15
Re: Unable to verify a message (7 replies, posted in Bugs & problems)
Use rich text to preserve the string. See this thread.
3 2007-05-21 16:37:24
Re: The first signature of this mail is not valid. (3 replies, posted in Bugs & problems)
Use rich text. See this thread: http://firegpg.tuxfamily.org/forum/viewtopic.php?id=111
4 2007-05-21 16:05:28
Re: First signature of this email is not valid (12 replies, posted in Bugs & problems)
I ran a few tests
1. Didn't work. Checked this forum.
2. Signed whole message. Didn't work.
3. Does one of the algorithms truncate ending spaces or other "hidden" characters? Signed a part in the middle of the message. Didn't work.
4. Is it the word wrap? Gmail allows word wrap in plaintext email during composition and then inserts its own carriage returns (I think after the last word such that each line is 80 characters or less). I tested just my contact info, every line has a carriage return, and then the signature verified.
5. In rich text mode, which doesn't force wordwraps, the above tests all work.
6. In basic html mode, which is inherently plaintext, forcing wordwraps, tests 1 - 4 didn't work.
7. In rich text mode, signing and then encrypting also works.
This thread has some additional reports. The first post advises composing in plaintext, which the above tests indicate is the wrong advice. Use rich text. You don't have to use the bad features of rich text, just use it because it preserve the data string.
http://firegpg.tuxfamily.org/forum/viewtopic.php?id=3
Hope this helps.