Package: nut Severity: normal Version: 2.4.3-1 Tags: upstream Hi,
Lintian is giving us a warning about a powercom.8 man page nut: manpage-has-errors-from-man usr/share/man/man8/powercom.8.gz 114: warning [p 2, 2.5i]: can't break line I guess this should be fixed upstream Cheers Laurent Bigonville W: nut: manpage-has-errors-from-man usr/share/man/man8/powercom.8.gz 114: warning [p 2, 2.5i]: can't break line N: N: This man page provokes warnings or errors from man. N: N: "cannot adjust" or "can't break" are trouble with paragraph filling, N: usually related to long lines. Adjustment can be helped by left N: justifying, breaks can be helped with hyphenation, see "Manipulating N: Filling and Adjusting" and "Manipulating Hyphenation" in the manual. N: N: "can't find numbered character" usually means latin1 etc in the input, N: and this warning indicates characters will be missing from the output. N: You can change to escapes like \[:a] described on the groff_char man N: page. N: N: Other warnings are often formatting typos, like missing quotes around N: a string argument to .IP. These are likely to result in lost or N: malformed output. See the groff_man (or groff_mdoc if using mdoc) man N: page for information on macros. N: N: This test uses man's --warnings option to enable groff warnings that N: catch common mistakes, such as putting . or ' characters at the start N: of a line when they are intended as literal text rather than groff N: commands. This can be fixed either by reformatting the paragraph so N: that these characters are not at the start of a line, or by adding a N: zero-width space (\&) immediately before them. N: N: At worst, warning messages can be disabled with the .warn directive, N: see "Debugging" in the groff manual. N: N: To test this for yourself you can use the following command: N: LANG=en_US.UTF-8 MANWIDTH=80 man --warnings -E UTF-8 -l <file> >/dev/null N: N: Severity: normal, Certainty: certain N: -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
