From e2e267e8234fe5b74a7728a1142bf8ba016c9fbd Mon Sep 17 00:00:00 2001 From: David Shaw Date: Thu, 20 May 2004 03:01:46 +0000 Subject: [PATCH] * gpg.sgml: Clarify that --charset applies to informational strings and does not recode messages themselves. Remove include-non-rfc export-option. --- doc/ChangeLog | 6 ++++++ doc/gpg.sgml | 14 ++++---------- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 572bf4df9..18ab887e1 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,9 @@ +2004-05-19 David Shaw + + * gpg.sgml: Clarify that --charset applies to informational + strings and does not recode messages themselves. Remove + include-non-rfc export-option. + 2004-05-08 David Shaw * DETAILS, credits-1.0, credits-1.2: ElGamal -> Elgamal. diff --git a/doc/gpg.sgml b/doc/gpg.sgml index 8fd2888bf..9bdf78083 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -1276,12 +1276,6 @@ exporting keys. Options can be prepended with a `no-' to give the opposite meaning. The options are: - -include-non-rfc - -Include non-RFC compliant keys in the export. Defaults to yes. - - include-local-sigs @@ -1549,10 +1543,10 @@ $GNUPGHOME. --charset &ParmName; Set the name of the native character set. This is used to convert -some strings to proper UTF-8 encoding. If this option is not used, the -default character set is determined from the current locale. A -verbosity level of 3 shows the used one. Valid values for &ParmName; -are: +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 current locale. A verbosity level of 3 shows the +used one. Valid values for &ParmName; are: iso-8859-1This is the Latin 1 set.