All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: git@vger.kernel.org
Subject: Re: groff .ft command use in asciidoc
Date: Thu, 18 Nov 2010 17:47:19 +0000 (UTC)	[thread overview]
Message-ID: <ic3or7$dfi$1@dough.gmane.org> (raw)
In-Reply-To: 20101117101516.GA12416@burratino

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


> 
> 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



> Hope that helps,
> Jonathan

  parent reply	other threads:[~2010-11-18 17:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  9:52 groff .ft command use in asciidoc Andi Kleen
2010-11-17 10:15 ` Jonathan Nieder
2010-11-17 11:52   ` Andi Kleen
2010-11-17 14:38   ` Jeff King
2010-11-17 15:48     ` Andi Kleen
2010-11-19 17:54       ` Jeff King
2010-11-19 18:22         ` Jonathan Nieder
2010-11-19 18:37           ` Jeff King
2010-11-19 20:34         ` Drew Northup
2010-11-19 20:40           ` Jeff King
2010-11-19 20:53             ` Drew Northup
2010-11-19 22:58             ` Junio C Hamano
2010-11-20  1:48               ` Todd Zullinger
2010-11-18 17:47   ` Alejandro Riveira Fernández [this message]
2010-11-18 21:11     ` Drew Northup
2010-11-18 23:15       ` Alejandro Riveira Fernández

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='ic3or7$dfi$1@dough.gmane.org' \
    --to=ariveira@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.