.ft tag in man
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
.ftIs that intended or just an artefact?
Signature · 6 lines
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩244 柳宗元 江雪
千山鳥飛絕 萬徑人蹤滅 孤舟簑笠翁 獨釣寒江雪Quoted 9 lines · bill lam
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..
Quoted 6 lines · Junio C Hamano
Quoted 4 lines · bill lam
The diagram in man contain some .ft tag, eg inside PAGE=less git help rebase
it contains
Quoted 7 lines
Quoted 5 lines
.ft C A---B---C topic / D---E---F---G master .ftNo, 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)▓fRThe '.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.
Quoted 2 lines
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
Signature · 5 lines
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. FieldsTodd Zullinger venit, vidit, dixit 14.01.2009 07:45:
...
Quoted 40 lines
I began seeing this on Fedora 10. Defining
DOCBOOK_XSL_172fixed 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)
.ftWith
DOCBOOK_XSL_172, I get this:$ git diff ▓fB(3)▓fR $ git diff --cached ▓fB(2)▓fR $ git diff HEAD ▓fB(3)▓fRThe '.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.
Quoted 2 lines
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
Quoted 6 lines
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