diff options
| author | Daniel Kahn Gillmor <[email protected]> | 2016-09-15 18:21:15 +0000 |
|---|---|---|
| committer | NIIBE Yutaka <[email protected]> | 2016-09-17 07:00:37 +0000 |
| commit | 0d67241e317b172a258a910c02d90639e2b08fce (patch) | |
| tree | f1f68c8a94af20f1a3273da46633c7f8af750bc4 /doc/DETAILS | |
| parent | move some file encodings to UTF-8 (diff) | |
| download | gnupg-0d67241e317b172a258a910c02d90639e2b08fce.tar.gz gnupg-0d67241e317b172a258a910c02d90639e2b08fce.zip | |
Fix more spelling
* NEWS, acinclude.m4, agent/command-ssh.c, agent/command.c,
agent/gpg-agent.c, agent/keyformat.txt, agent/protect-tool.c,
common/asshelp.c, common/b64enc.c, common/recsel.c, doc/DETAILS,
doc/HACKING, doc/Notes, doc/TRANSLATE, doc/dirmngr.texi,
doc/faq.org, doc/gpg-agent.texi, doc/gpg.texi, doc/gpgsm.texi,
doc/instguide.texi, g10/armor.c, g10/gpg.c, g10/keyedit.c,
g10/mainproc.c, g10/pkclist.c, g10/tofu.c, g13/sh-cmd.c,
g13/sh-dmcrypt.c, kbx/keybox-init.c, m4/pkg.m4, sm/call-dirmngr.c,
sm/gpgsm.c, tests/Makefile.am, tests/gpgscm/Manual.txt,
tests/gpgscm/scheme.c, tests/openpgp/gpgv-forged-keyring.scm,
tests/openpgp/multisig.test, tests/openpgp/verify.scm,
tests/pkits/README, tools/applygnupgdefaults,
tools/gpg-connect-agent.c, tools/mime-maker.c, tools/mime-parser.c:
minor spelling cleanup.
Signed-off-by: Daniel Kahn Gillmor <[email protected]>
Diffstat (limited to 'doc/DETAILS')
| -rw-r--r-- | doc/DETAILS | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/DETAILS b/doc/DETAILS index b5431d004..1e9682dcd 100644 --- a/doc/DETAILS +++ b/doc/DETAILS @@ -15,6 +15,8 @@ This is the DETAILS file for GnuPG which specifies some internals and parts of the external API for GPG and GPGSM. * Format of the colon listings + +* The format is a based on colon separated record, each recods starts with a tag string and extends to the end of the line. Here is an example: @@ -91,7 +93,7 @@ described here. ultimately valid. - w :: The key has a well known private part. - s :: The key has special validity. This means that it might be - self-signed and expected to be used in the STEED sytem. + self-signed and expected to be used in the STEED system. If the validity information is given for a UID or UAT record, it describes the validity calculated based on this user ID. If given @@ -120,7 +122,7 @@ described here. The creation date of the key is given in UTC. For UID and UAT records, this is used for the self-signature date. Note that the - date is usally printed in seconds since epoch, however, we are + date is usually printed in seconds since epoch, however, we are migrating to an ISO 8601 format (e.g. "19660205T091500"). This is currently only relevant for X.509. A simple way to detect the new format is to scan for the 'T'. Note that old versions of gpg @@ -136,7 +138,7 @@ described here. Used for serial number in crt records. For UID and UAT records, this is a hash of the user ID contents used to represent that exact user ID. For trust signatures, this is the trust depth - seperated by the trust value by a space. + separated by the trust value by a space. *** Field 9 - Ownertrust @@ -715,7 +717,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB: Tofu information. The fingerprint is the fingerprint of the primary key and the mbox is in general the addr-spec part of the userid encoded in UTF-8 and percent escaped. The fingerprint is - indentical for all TOFU_USER lines up to a NEWSIG line. + identical for all TOFU_USER lines up to a NEWSIG line. *** TOFU_STATS <validity> <sign-count> 0 [<policy> [<tm1> <tm2> <tm3> <tm4>]] @@ -930,7 +932,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB: commencing with a letter or such a string prefixed with a numerical error code and an underscore; e.g.: "151011327_EOF". *** SUCCESS [<location>] - Postive confirmation that an operation succeeded. It is used + Positive confirmation that an operation succeeded. It is used similar to ISO-C's EXIT_SUCCESS. <location> is optional but if given should not contain spaces. Used only with a few commands. @@ -987,7 +989,7 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB: <name> is a percent-plus escaped filename describing the mountpoint for the current operation (e.g. used by "g13 --mount"). This may either be the specified mountpoint or one randomly - choosen by g13. + chosen by g13. *** PINENTRY_LAUNCHED <pid> This status line is emitted by gpg to notify a client that a |
