Page MenuHome GnuPG

yat2m created manpages lead to a man-warning for @samp{} content
Closed, ResolvedPublic

Description

The manpages created with yat2m lead to a few warnings. E.g. gpg.1:

$ man --warning -l doc/gpg.1 > /dev/null
<standard input>:153: name expected (got a special character): treated as missing
<standard input>:1449: warning: `GPG_AGENT_INFO'' not defined
<standard input>:1450: warning: `This' not defined
<standard input>:2800: warning: `-'' not defined

The problem is the @samp{} handling, that leads to an apostrophe at the
beginning of the line, which is interpreted as a control character. If you just
want to put it into apostrophes, I would suggest the following handling in yat2m.c:

{ "samp", 0, "\\(aq", "\\(aq" },

So the content is put into apostrophes, but without any linebreaks to work
around leading apostrophes and dots at the beginning of a file, where they are
control characters.

Maybe you further want to surround it with \fB...\fR to make the content bold.

Event Timeline

Applied to 1.4 and 2.0. Thanks. Do you know where I can find a list of the glyphs?

Take a look at the top comment in
http://docbook.sourceforge.net/release/xsl/current/manpages/charmap.groff.xsl.
It lists the references for this charmap - you can also use this charmap as a
reference (it's the most complete I know).

werner claimed this task.

In the change in the stable tree you maybe forgot to remove the apostrophe on
the right side. It currently says:

\\(aq'

isntead of

\\(aq

Ooops.
Fixed. I also use \(oq and \(cq for @env and @file instead of the backticks.