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: --comment works with all armored messages. Clarify that

Browse Source 
--charset applies to informational strings and does not recode messages
themselves.
This commit is contained in:
David Shaw 2004-05-05 18:28:39 +00:00
parent a382a86e64
commit 0c8c110b17
2 changed files with 12 additions and 6 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-05 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: --comment works with all armored messages. Clarify
that --charset applies to informational strings and does not
recode messages themselves.
2004-05-03 Werner Koch <wk@gnupg.org>
* gpgv.sgml: Removed reference to non-available option

12
doc/gpg.sgml
View File

@ -1332,10 +1332,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>
@ -1471,8 +1471,8 @@ soon.
<varlistentry>
<term>--comment &ParmString;</term>
<listitem><para>
Use &ParmString; as the comment string in clear text signatures. The
default behavior is not to use a comment string.
Use &ParmString; as the comment string in ASCII armored or clearsigned
messages. The default behavior is to not use a comment string.
</para></listitem></varlistentry>