Fri 29 Apr 2011 10:57:22 PM UTC, comment #12:
my understanding of man-db is that it automatically takes care of detecting and recoding (when necessary) for the active locale. so is declaring UTF8 explicitly even necessary ?
for the patch in question, `sed -i` isnt portable. you'd want to run sed into a local temp file and then install that into the final location. i think autoconf also takes care of setting up SED, so you might want to use $(SED) or @SED@ in the makefile instead.
|
Wed 27 Apr 2011 11:11:41 AM UTC, comment #11:
the attached patch solved the issue :-)
|
Mon 18 Apr 2011 02:08:21 PM UTC, comment #10:
Please give the attched patch a try
(file #23267)
|
Fri 15 Apr 2011 09:56:22 PM UTC, comment #9:
looking at the oldest man currently available (released in mid-2005), it has the same behavior. so this isnt anything new.
|
Fri 15 Apr 2011 11:32:20 AM UTC, comment #8:
There are two type of comments in roff, normal comments
which starts with
dot backslash double quote
and in the very first line with
single quote backslash double quote
both are ignored by roff, but the later one is parsed by
both man and man-db to search for the use preprocessors
marked with their starting letter like eqn (e), grap (g),
pic (p), and tbl (t) ... and further man-db search for
its coding tag to be able to detect the used coding of the
manual page. With this tag it is possible to detect
the encoding regardless where the manual page is located.
Now it seems that the cannonical man program does not ignore
unknown tags or letters but simply show a warning message.
|
Fri 15 Apr 2011 10:18:03 AM UTC, comment #7:
i would have thought man-db parsed that as well. is there a "man" spec which could be reviewed to see what the expected behavior for apps ? is this tag parsed by *roff, or simply ignored as a comment ?
my understanding of man-db is that it transparently takes care of converting encodings to whatever the user currently has active.
if sysvinit has always had this tag, i wonder if the parsing is something new to canonical man. i'll have to dig up the older versions to see what it's doing.
|
Tue 12 Apr 2011 09:05:56 AM UTC, comment #6:
... the editor form has eaten the backslashes from the
sed command line 8)
|
Tue 12 Apr 2011 08:46:05 AM UTC, comment #5:
Hmmm ... the question rises: why does the canonical man simply
not ignore this information tag of man-db in the preprocessor
line?
Both Debian and openSUSE are using man-db and it seems that
the tag for man-db was added to all of the manual pages
(beside fstab-decode.8).
For me this looks like this was already part of revision 1
before Savannah, that is the original tar ball from 2009-11-20.
Simply solution would be something like
sed -ri "1{ s@[[:blank:]]-\-[[:blank:]][^\][[:blank:]]-\-@@; }" man/.[1-8]
maybe based on a configure option
|
Mon 11 Apr 2011 07:25:18 PM UTC, comment #4:
it's the very first line. `man` looks at all lines that start with the four chars:
'\"
and uses those as directives for how to invoke the relevant roff
but the request:
-- coding: UTF-8 --
is not recognized by `man` thus it emits the error in question.
also as i said, the commands you listed are not relevant to groff because the error in question isnt coming from groff. it's coming from `man`. thus there is nothing specific to Gentoo that is causing this issue.
i imagine the man package you're using is actually "man-db" rather than the canonical "man" which is why you arent seeing the output we are.
|
Mon 11 Apr 2011 08:06:20 AM UTC, comment #3:
Which directive is specific to the man-db package?
Beside this piping the manual page with cat through
nroff show no errors here. That is that all the
command in my comment #1 work flawless.
|
Mon 11 Apr 2011 12:44:40 AM UTC, comment #2:
the error isnt coming from groff. the shutdown(8) man page is using a directive that is specific to the man-db package.
|
Fri 08 Apr 2011 10:27:37 AM UTC, comment #1:
I do not see any error nor any warning message[1], maybe the
(g)roff installation and/or your locale setup is broken.
Beside this you're talking about a typobut only cite
the message: which typo do you meant?
IMHO you should report this on the bugzilla of Gentoo
and asign this to the groff maintainer at Gentoo.
[1] Tested with
man 8 shutdown
and in the source tree with
cat man/shutdown.8 | nroff -mandoc | less -R
cat man/shutdown.8 | nroff -man | less -R
cat man/shutdown.8 | nroff -mandb | less -R
where the last roff macro package mandb is only
usabel for the mandb package used here.
Sidemark: `nroff' == `groff -T utf8'
|
Fri 08 Apr 2011 10:04:33 AM UTC, original submission:
Under an almost stable Gentoo I get this (probably harmless) error message :
tfoerste@n22 ~ $ man shutdown
Error parsing *roff command from file /usr/share/man/man8/shutdown.8.bz2
B/c the likelihood that the *roff preprocessor under Gentoo has a problem (only) with this particular file, I file this bug report here first.
|