* .ft tag in man
@ 2009-01-14 5:21 bill lam
2009-01-14 5:35 ` Junio C Hamano
0 siblings, 1 reply; 4+ messages in thread
From: bill lam @ 2009-01-14 5:21 UTC (permalink / raw
To: git
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 柳宗元 江雪
千山鳥飛絕 萬徑人蹤滅 孤舟簑笠翁 獨釣寒江雪
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: .ft tag in man
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
0 siblings, 1 reply; 4+ messages in thread
From: Junio C Hamano @ 2009-01-14 5:35 UTC (permalink / raw
To: bill lam; +Cc: git
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..
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: .ft tag in man
2009-01-14 5:35 ` Junio C Hamano
@ 2009-01-14 6:45 ` Todd Zullinger
2009-01-14 10:11 ` Michael J Gruber
0 siblings, 1 reply; 4+ messages in thread
From: Todd Zullinger @ 2009-01-14 6:45 UTC (permalink / raw
To: Junio C Hamano; +Cc: bill lam, git
[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 542 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: .ft tag in man
2009-01-14 6:45 ` Todd Zullinger
@ 2009-01-14 10:11 ` Michael J Gruber
0 siblings, 0 replies; 4+ messages in thread
From: Michael J Gruber @ 2009-01-14 10:11 UTC (permalink / raw
To: Todd Zullinger; +Cc: Junio C Hamano, bill lam, git
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-01-14 10:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).