Issues in pacutils man pages

[hmartink]

Dear pacutil maintainer,
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including pacutil) as
well for a large variety of target languages.

During their work translators notice different possible issues in the
original (english) man pages. Sometimes this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a
convention not held up and sometimes we simply do not understand the
original.

We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once in a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.

Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to convert into
your source format.

Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.

I'm now reporting the errors for your project. If future reports
should use another channel, please let me know.

Man page: paccapability.1
Issue: libalpm → B(3)

"\&B provides a way to query which features libalpm was built "
"with. Recognized capabilities are:"

"Check if libalpm was built with signature checking:"

Man page: pacconf.1
Issue: normalized → summarized

"Query configuration options from pacman's configuration file. If no "
"\&Is are provided, the entire configuration will be printed in a "
"normalized format. By default, if only a single I is provided, "
"only its value will be printed without the option name. For directives "
"without a value, the directive name will be used as the value."

Man page: pacconf.1
Issue: pacman → B(8)

"The values displayed are the final values as would be parsed by pacman "
"itself. All default values are set, CW<\(CInclude\\*(C'> directives are " "processed, CW<$arch> and \\&CW<$repo> variables in repository servers are " "replaced, and CW<\\*(CArchitecture\(C'> will be replaced if set to CW<"
"\(C`auto\(C'>."

Man page: paclog.1
Issue: but does not a log file → but does not contain a log file

"\&B determines whether or not to read the log file from I "
"based on a naive check using B\|(3). If B is called in an "
"environment, such as a shell function or script being used in a pipe, where "
"I is not connected to a terminal but does not a log file to parse, "
"B should be called with I closed. For POSIX-compatible "
"shells, this can be done with CW<\(C`E&-\(C'>."

Man page: pacrepairdb.1
Issue: cache → cached

"Display the packages to be repaired and the cache packages to be used and "
"exit."

Man page: pacrepairdb.1
Issue: locate → to locate

"\&B does not check for leftover orphaned files. It is the "
"user's responsibility locate and handle orphaned files."