On Mon, 30 Jul 2001 20:40:33 -0700, Jon Callas said:
Is this an implementation problem, or a standard problem?
It is a matter how the implementation is used to create an rfc2015
compliant message. Some translations of GnuPG do translate the
default comment string and then you might see non ascii characters.
The solution is to use "gpg --comment '' ..." to disable the armor
commentline or use sed to cut it out later.
So it is definitely not a standard problem.
Werner
--
Werner Koch Omnis enim res, quae dando non deficit, dum habetur
g10 Code GmbH et non datur, nondum habetur, quomodo habenda est.
Privacy Solutions -- Augustinus