Re: groff .ft command use in asciidoc

From: Drew Northup <drew.northup@maine.edu>
Date: Nov 18, 2010, 21:11 UTC
Message-ID: <1290114671.2316.12.camel@drew-northup.unet.maine.edu>
In-Reply-To: <ic3or7$dfi$1@dough.gmane.org>

On Thu, 2010-11-18 at 17:47 +0000, Alejandro Riveira Fernández wrote:

> On Wed, 17 Nov 2010 04:15:16 -0600, Jonathan Nieder wrote:

Show 14 quoted lines

> > This is in my opinion a bug: unless you use ASCIIDOC_NO_ROFF, git's
> > asciidoc.conf will include raw roff directives in the docbook markup it
> > generates.  And then docbook will escape the periods, producing the
> > output you see.
> > 
> > The workaround is very simple: set ASCIIDOC_NO_ROFF to nonempty when you
> > build documentation.
> 
>  I use make quick-install-man which, afaik, installs man pages 
> "prerendered" from the man branch and i see the same artifact.
>  
>  So can those man pages be rendered with this workaraound?
>  
>  Thanks

Out of curiosity I went ahead and ran that make script. I then ran the following in the directory that the manpage directories were written out to (an alternate DESTDIR):

[dnorthup@drew-northup man]$ grep -R "\.ft" * [dnorthup@drew-northup man]$

Note that it returned nothing. This is based on the current git.git. (I just pulled to be sure of that...)

As noted, all that make script essentially does is write out the manpages found in origin/man--so it matters not what my current platform is.

Run "man git-commit" in one terminal open up a second and run "ps ax | grep man" and report on the results.

-- 
-Drew Northup N1XIM
   AKA RvnPhnx on OPN
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59