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

[Justin Pryzby]

On Mon, Jan 28, 2008 at 08:44:46AM +0100, Werner Koch wrote:
> 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
> lines?
Probably because I searched for "white spaces" with an "s" and so
didn't find that occurance.  I think most occurances of "white
space[s]" can be changed to "white space[s]", but it's worth it to
check if it makes sense for each case.

> > 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.
I'm not sure about this case; however, in:

./doc/gpg-agent.texi
|@item -s
|@itemx --sh
|@itemx -c
|@itemx --csh
|@opindex s
|@opindex sh
|@opindex c
|@opindex csh
|Format the info output in daemon mode for use with the standard Bourne
|shell respective the C-shell. The default is to guess it based on the
|environment variable @code{SHELL} which is in almost all cases
|correct.

I would say:
|Format the info output in daemon mode for use with the standard Bourne
|shell or the C-shell, respectively. The default is to guess it based on the
|environment variable @code{SHELL} which is correct in almost all cases.

I think "... respectively ..." is what's needed in the other cases I
saw, too (but the rest of the sentence has to be changed, too).

|@item --keep-tty
|@itemx --keep-display
|@opindex keep-tty
|@opindex keep-display
|Ignore requests to change the current @code{tty} or X
|window system @code{DISPLAY} variable, respectively.  This is useful to lock the
|pinentry to pop up at the @code{tty} or display you started the agent.

In ./doc/DETAILS, I'm not sure:

|       The default is the standard gpg Web of Trust model respective
|       the standard X.509 model.  The defined values are

Is this supposed to mean:

|       The default is the standard gpg Web of Trust model, rather than
|       the standard X.509 model.  The defined values are

?

Justin