All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: git@vger.kernel.org, Chris Johnsen <chris_johnsen@pobox.com>
Subject: Re: groff .ft command use in asciidoc
Date: Wed, 17 Nov 2010 04:15:16 -0600	[thread overview]
Message-ID: <20101117101516.GA12416@burratino> (raw)
In-Reply-To: <20101117095233.GA23817@basil.fritz.box>

Hi,

Andi Kleen wrote:

> The git manpages on my opensuse 11.3 (git 1.7.1-1.14)
> frequently use the .ft command the opensuse groff does not 
> render.
> 
> For example from the final output of "man git-commit":
> 
>            .ft C
>            $ edit hello.c
>            $ git rm goodbye.c
>            $ git add hello.c
>            $ git commit
>            .ft

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 think the only reason this is not the default is that no one has
tested it with old DocBook XSL versions, but I'm not sure.
Documentation/Makefile has some notes about this.

Hope that helps,
Jonathan

  reply	other threads:[~2010-11-17 10:16 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 [this message]
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
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=20101117101516.GA12416@burratino \
    --to=jrnieder@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=chris_johnsen@pobox.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.