(forw) Bug#461980: gnupg-agent: manpage typos

Werner Koch wk at gnupg.org
Mon Jan 28 08:44:46 CET 2008

On Sun, 27 Jan 2008 23:55, jpryzby+d at quoininc.com said:

> Including a new patch against the source files, with some additional
> fixes ("manly", "be possible").  Also some of the original fixes
> applied to additional parts.

Thanks.  I applied it except for:

> --- gnupg2-2.0.8/doc/qualified.txt
> +++ gnupg2-2.0.8.orig/doc/qualified.txt
> @@ -4,7 +4,7 @@
>  # signatures are.  Comments like this one and empty lines are allowed
>  # Lines do have a length limit but this is not a serious limitation as
>  # the format of the entries is fixed and checked by gpgsm: A
> +# non-comment line starts with optional white spaces, followed by
> -# non-comment line starts with optional whitespace, followed by
>  # exactly 40 hex character, white space and a lowercased 2 letter
>  # country code.  Additional data delimited with by a white space is
>  # current ignored but might late be used for other purposes.

Is there a reason why you did not fixed "white space" in the next 3

> Also my original note:
> |Note also that use of "respective" seems wrong.  The closest I can
> |think of is "with respect to", but I'm not sure.

  Ignore requests to change the current @code{tty} respective the X
  window system's @code{DISPLAY} variable.  This is useful to lock the

What I mean is: The one option changes @code{tty} and the other option
@code{DISPLAY}.  Thus I use "respective" similar how we use the same
word in German; I am not sure whether this is correct.  However, "with
respect to" is not what I mean.

> Also that I (personally?) prefer "prefix" to "prepend".




Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.

More information about the Gnupg-devel mailing list