discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Thomas Klausner <wiz@NetBSD.org>
To: discuss@mdocml.bsd.lv
Subject: mandoc -Tman bugs
Date: Mon, 8 Apr 2013 11:27:43 +0200	[thread overview]
Message-ID: <20130408092743.GU18461@danbala.tuwien.ac.at> (raw)

Hi!

I've run mandoc -Tman over the man pages in libzip.
     hg clone http://hg.nih.at/libzip/
     cd libzip/man
     mkdir mandoc
     for i in *.mdoc; do j=${i%%mdoc}man; mandoc -Tman $i > mandoc/$j; done

Then I looked at the output. I found two repeating problems:

1) Lots of pages spew stuff like:
zip_errors.man:92: warning: numeric expression expected (got `X')
The line here is .TP XZIPXERXCOMPNOTSUPPXX

2) In the SYNOPSIS, there are no parentheses around the function
arguments, and no ';' at the end. For example, the mdoc code (in
zip_close.mdoc):

.Ft int
.Fn zip_close "struct zip *archive"

which is usually printed as

     int
     zip_close(struct zip *archive);

is converted to the following man code:

int
zip_close struct zip *archive

Other than that, the output looks very good!
 Thomas
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

                 reply	other threads:[~2013-04-08  9:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130408092743.GU18461@danbala.tuwien.ac.at \
    --to=wiz@netbsd.org \
    --cc=discuss@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).