git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Todd Zullinger <tmz@pobox.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	bill lam <cbill.lam@gmail.com>, git <git@vger.kernel.org>
Subject: Re: .ft tag in man
Date: Wed, 14 Jan 2009 11:11:09 +0100	[thread overview]
Message-ID: <496DBA3D.9020502@drmicha.warpmail.net> (raw)
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

      reply	other threads:[~2009-01-14 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  5:21 .ft tag in man bill lam
2009-01-14  5:35 ` Junio C Hamano
2009-01-14  6:45   ` Todd Zullinger
2009-01-14 10:11     ` Michael J Gruber [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=496DBA3D.9020502@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=cbill.lam@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tmz@pobox.com \
    /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).