# .ft tag in man

4 messages from 2009-01-14 to 2009-01-14. Participants: bill lam, Junio C Hamano, Todd Zullinger, Michael J Gruber.
Thread: https://gitlist.dev/t/17163

## bill lam, 2009-01-14 05:21

Subject: .ft tag in man
Message-ID: <20090114052126.GA6849@b2j>
URL: https://gitlist.dev/e/20090114052126.GA6849%40b2j

```
The diagram in man contain some .ft tag, eg inside
PAGE=less git help rebase
it contains

           .ft C
                     A---B---C topic
                    /
               D---E---F---G master
           .ft

Is that intended or just an artefact?

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩244 柳宗元  江雪
    千山鳥飛絕  萬徑人蹤滅  孤舟簑笠翁  獨釣寒江雪

```

## Junio C Hamano, 2009-01-14 05:35

Subject: Re: .ft tag in man
Message-ID: <7veiz678m2.fsf@gitster.siamese.dyndns.org>
URL: https://gitlist.dev/e/7veiz678m2.fsf%40gitster.siamese.dyndns.org
In-Reply-To: <20090114052126.GA6849@b2j>

```
bill lam <cbill.lam@gmail.com> writes:

> The diagram in man contain some .ft tag, eg inside
> PAGE=less git help rebase
> it contains
>
>            .ft C
>                      A---B---C topic
>                     /
>                D---E---F---G master
>            .ft

No, I do not see that neither on my Debian nor on k.org's FC 9.

Perhaps you are using different version of asciidoc/docbook/xmlto
toolchain?

I think we added compatibility definitions in our Makefile to deal with
differences between AsciiDoc 7 vs 8, but I do not recall offhand what
misformatting one would get if it is set incorrectly..

```

## Todd Zullinger, 2009-01-14 06:45

Subject: Re: .ft tag in man
Message-ID: <20090114064510.GZ18365@inocybe.teonanacatl.org>
URL: https://gitlist.dev/e/20090114064510.GZ18365%40inocybe.teonanacatl.org
In-Reply-To: <7veiz678m2.fsf@gitster.siamese.dyndns.org>

```
Junio C Hamano wrote:
> bill lam <cbill.lam@gmail.com> writes:
>
>> The diagram in man contain some .ft tag, eg inside
>> PAGE=less git help rebase
>> it contains
>>
>>            .ft C
>>                      A---B---C topic
>>                     /
>>                D---E---F---G master
>>            .ft
>
> No, I do not see that neither on my Debian nor on k.org's FC 9.

I began seeing this on Fedora 10.  Defining DOCBOOK_XSL_172 fixed
that issue, but seems to have caused another. :/

For example, in git-diff.1, without DOCBOOK_XSL_172, I see:

               .ft C
               $ git diff            (1)
               $ git diff --cached   (2)
               $ git diff HEAD       (3)
               .ft

With DOCBOOK_XSL_172, I get this:

               $ git diff            ▓fB(3)▓fR
               $ git diff --cached   ▓fB(2)▓fR
               $ git diff HEAD       ▓fB(3)▓fR

The '.ft' problem is gone, but '\fB' and '\fR' are replaced by '▓fB'
and '▓fR', respectively.  The paragraphs that follow such a list of
commands show more ugliness:

           ⌂sp ▓fB1. ▓fRChanges in the working tree not yet staged for the
           next commit.  ⌂br ▓fB2. ▓fRChanges between the index and your
           last commit; what you would be committing if you run "git commit"
           without "-a" option.  ⌂br ▓fB3. ▓fRChanges in the working tree
           since your last commit; what you would be committing if you run
           "git commit -a" ⌂br

Defining ASCIIDOC8 seems to have no effect on this problem.

> Perhaps you are using different version of asciidoc/docbook/xmlto
> toolchain?

On Fedora 10, these are the versions:

asciidoc-8.2.5-2.fc9
docbook-dtds-1.0-41.fc10
docbook-style-xsl-1.74.0-4.fc10
xmlto-0.0.21-2.fc10

Fedora 9 has:

asciidoc-8.2.5-2.fc9
docbook-dtds-1.0-38.fc9
docbook-style-xsl-1.73.2-10.fc9
xmlto-0.0.20-3.fc9

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Once ... in the wilds of Afghanistan, I lost my corkscrew, and we were
forced to live on nothing but food and water for days.
    -- W.C. Fields


```

## Michael J Gruber, 2009-01-14 10:11

Subject: Re: .ft tag in man
Message-ID: <496DBA3D.9020502@drmicha.warpmail.net>
URL: https://gitlist.dev/e/496DBA3D.9020502%40drmicha.warpmail.net
In-Reply-To: <20090114064510.GZ18365@inocybe.teonanacatl.org>

```
Todd Zullinger venit, vidit, dixit 14.01.2009 07:45:
...
> I began seeing this on Fedora 10.  Defining DOCBOOK_XSL_172 fixed
> that issue, but seems to have caused another. :/
> 
> For example, in git-diff.1, without DOCBOOK_XSL_172, I see:
> 
>                .ft C
>                $ git diff            (1)
>                $ git diff --cached   (2)
>                $ git diff HEAD       (3)
>                .ft
> 
> With DOCBOOK_XSL_172, I get this:
> 
>                $ git diff            ▓fB(3)▓fR
>                $ git diff --cached   ▓fB(2)▓fR
>                $ git diff HEAD       ▓fB(3)▓fR
> 
> The '.ft' problem is gone, but '\fB' and '\fR' are replaced by '▓fB'
> and '▓fR', respectively.  The paragraphs that follow such a list of
> commands show more ugliness:
> 
>            ⌂sp ▓fB1. ▓fRChanges in the working tree not yet staged for the
>            next commit.  ⌂br ▓fB2. ▓fRChanges between the index and your
>            last commit; what you would be committing if you run "git commit"
>            without "-a" option.  ⌂br ▓fB3. ▓fRChanges in the working tree
>            since your last commit; what you would be committing if you run
>            "git commit -a" ⌂br
> 
> Defining ASCIIDOC8 seems to have no effect on this problem.
> 
>> Perhaps you are using different version of asciidoc/docbook/xmlto
>> toolchain?
> 
> On Fedora 10, these are the versions:
> 
> asciidoc-8.2.5-2.fc9
> docbook-dtds-1.0-41.fc10
> docbook-style-xsl-1.74.0-4.fc10
> xmlto-0.0.21-2.fc10
> 
> Fedora 9 has:
> 
> asciidoc-8.2.5-2.fc9
> docbook-dtds-1.0-38.fc9
> docbook-style-xsl-1.73.2-10.fc9
> xmlto-0.0.20-3.fc9

The problem can be seen even in the F10 release packages for git. Shame
on them ;)

When I get back to my F9 box I'll try upgrading those packages one by
one to their F10 versions (hoping dependencies don't connect all of them).

Michael

```
