security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-06-01 22:28:02 +02:00
Code Activity

* gpg.sgml: Clarify that --charset applies to informational strings and

Browse Source 
does not recode messages themselves.  Remove include-non-rfc
export-option.
This commit is contained in:
David Shaw 2004-05-20 03:01:46 +00:00
parent 3cef407e06
commit e2e267e823
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/ChangeLog
View File

@ -1,3 +1,9 @@
2004-05-19 David Shaw <dshaw@jabberwocky.com>
* 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 <dshaw@jabberwocky.com>
* DETAILS, credits-1.0, credits-1.2: ElGamal -> Elgamal.

14
doc/gpg.sgml
View File

@ -1276,12 +1276,6 @@ exporting keys. Options can be prepended with a `no-' to give the
opposite meaning. The options are:
<variablelist>
<varlistentry>
<term>include-non-rfc</term>
<listitem><para>
Include non-RFC compliant keys in the export. Defaults to yes.
</para></listitem></varlistentry>
<varlistentry>
<term>include-local-sigs</term>
<listitem><para>
@ -1549,10 +1543,10 @@ $GNUPGHOME.
<term>--charset &ParmName;</term>
<listitem><para>
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:</para>
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:</para>
<variablelist>
<varlistentry>
<term>iso-8859-1</term><listitem><para>This is the Latin 1 set.</para></listitem>