From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Re: Weird rendering of \*(C+
Date: Tue, 5 Oct 2010 17:51:10 +0200 [thread overview]
Message-ID: <20101005155110.GQ65440@acme.spoerlein.net> (raw)
In-Reply-To: <20101004204721.GC16469@iris.usta.de>
On Mon, 04.10.2010 at 22:47:21 +0200, Ingo Schwarze wrote:
> Hi Ulrich,
>
> Ulrich Spoerlein wrote on Mon, Oct 04, 2010 at 10:35:48PM +0200:
>
> > FreeBSD has added pod2man'd manpages for clang(1) and tblgen(1), they
> > render quite similar to groff, except for \*(C+ which is completely out
> > of whack, please see attached snippet from the manpages.
> >
> > It renders like:
> >
> > DESCRIPTION
> > clang is a C, Cv'-.1v'h'-1p'+h'-1p'+v'.1v'h'-1p', and Objective-C
>
> Just update to mandoc-1.10.6, it renders:
Gah! I was using a stale binary, ie. 1.10.5
Sorry for the noise. The pages render just like groff, kudos to y'all!
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-10-05 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 20:35 Ulrich Spörlein
2010-10-04 20:47 ` Ingo Schwarze
2010-10-05 15:51 ` Ulrich Spörlein [this message]
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=20101005155110.GQ65440@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--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).