Re: 1.5.7 BUG: character set in traditional PGP
Dne Sat, Feb 12, 2005 at 09:31:40PM +0100, Thomas Roessler napsal:
> Werner, how about including that as a command line option? Shouldn't
> be so difficult.
Very good idea which I didn't get before. But man says:
--display-charset name
Set the name of the native character set. This is used to
convert some
informational strings like user IDs to the proper UTF-8
encoding. If this
option is not used, the default character set is determined
from the cur-
rent locale. A verbosity level of 3 shows the chosen set.
Valid values
for name are:
and it is true, You can change charset of names in keyring, but not the
content of encypted message.
The mail message is from gpg point of view only some file. It can be binary
file, mail, OpenOffice.org...., there is no need to translate it on gpg
side. In fact, encrypting and decrypting shouldnt modify message any way
(yes I know, it is true for MUA too).
You can say, this is problem on MUA. The sender should send only UTF-8
messages, but You will never bring the people to do it. All MUAs which
I know are sending gpg encrypted mail in native charset.
But we can modify gpg_decrypt command to call iconv in pipe. But after
decrypting You dont have anymore access to original message, where is the
gpg charset header, so You will need choose only one charset and use them
for all messages.
cheers
dan