mgansler / mscgen

Automatically exported from code.google.com/p/mscgen
GNU General Public License v2.0
1 stars 0 forks source link

[minor] About the man-page #25

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi

Recently there started a discussion about translated man-pages on one of
the Debian mailing lists and how to ensure that the user knew if they out
of date. 

One of the debaters noted that the first "line" in a man-page[1] is:

.TH title section date source manual

mscgen.1 only fills out "title" and "section".

~Niels

[1] man 7 man-pages
http://www.kernel.org/doc/man-pages/online/pages/man7/man-pages.7.html

Original issue reported on code.google.com by NThykier@gmail.com on 17 Aug 2009 at 7:13

GoogleCodeExporter commented 8 years ago
Also I got this warning:
 hyphen-used-as-minus-sign usr/share/man/man1/mscgen.1.gz:29 [1]

I am uncertain why it did not question the "-l" in line 17 as well.

~Niels

[1] http://lintian.debian.org/tags/hyphen-used-as-minus-sign.html

Original comment by NThykier@gmail.com on 17 Aug 2009 at 9:08

GoogleCodeExporter commented 8 years ago
Ah - putting the date on the page is easy and a good idea.  I tried the 
following to
find any warnings in the page:

$ groff -man -ww man/mscgen.1  > /dev/null

I found it had Windows line endings as well as an embedded \n which needed 
escaping.
 I fixed the escaping the -l on line 17, but don't see anything at line 29?

I'll submit a change shortly - please could you verify the warning is done and 
the
heading is okay for Debian?

Original comment by Michael....@gmail.com on 24 Aug 2009 at 8:18

GoogleCodeExporter commented 8 years ago
This issue was closed by revision r92.

Original comment by Michael....@gmail.com on 24 Aug 2009 at 8:20

GoogleCodeExporter commented 8 years ago
Hi

I have reopened this as lintian still complains. I found the sinner, which is 
the
"-i" in line 28 (r93). As in:

"The '-i' option maybe omitted if <infile> is specified as the last option."

Turning that into a '\-i' fixes this.

It does not seem to react to the lone "un-escaped" '-' which appears earlier in 
that
line.

~Niels

Original comment by NThykier@gmail.com on 26 Aug 2009 at 9:49

GoogleCodeExporter commented 8 years ago
This issue was closed by revision r94.

Original comment by Michael....@gmail.com on 30 Aug 2009 at 11:31