From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Adam Flott <adam@npjh.com>,
git@vger.kernel.org, Jonas Fonseca <fonseca@diku.dk>
Subject: Re: man pages are littered with .ft C and others
Date: Sun, 3 Feb 2008 11:39:47 +0100 [thread overview]
Message-ID: <200802031139.48752.jnareb@gmail.com> (raw)
In-Reply-To: <7vejbuxwpu.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>>
>> I see the same error in manpages, for example in git-diff-tree(1)
>
> http://thread.gmane.org/gmane.comp.version-control.git/53457/focus=53458
>
> rings a bell?
You mean:
Julian Phillips:
> Are you using docbook xsl 1.72? There are known problems building the
> manpages with that version. 1.71 works, and 1.73 should work when it get
> released.
No, I am using docbook-style-xsl-1.68.1-1, and compiling git from RPM.
Besids, I have different set of problems; only with literal blocks.
So while DOCBOOK_XSL_172 is not set... let me check...
Hmmm...
Before
$ man git-diff-tree
Example:
.ft C
:100644 100644 5be4a4...... 000000...... M file.c
.ft
$ make DOCBOOK_XSL_172=YesPlease doc
$ man Documentation/git-diff-tree.1
Example:
:100644 100644 5be4a4...... 000000...... M file.cWhen -z option is
not used, TAB, LF, and backslash characters in pathnames are repre-
sented as \t, \n, and \\, respectively.
So setting DOCBOOK_XSL_172 while it fixes the bug (even if docbook-xsl
is version 1.68.1, not 1.72), but introduces another.
Unfortunately I don't know enough about AsciiDoc, DocBook and XML
toolchain to even *try* to fix this issue.
P.S. Alternate soution would be for SRPM to contain pre-compiled
manpages, and not require asciidoc and its toolchain to provide
manpages.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-02-03 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 17:25 man pages are littered with .ft C and others Adam Flott
2008-02-02 17:46 ` Geert Bosch
2008-02-02 18:49 ` Jakub Narebski
2008-02-03 8:36 ` Junio C Hamano
2008-02-03 10:39 ` Jakub Narebski [this message]
2008-02-04 22:01 ` Jonas Fonseca
2008-02-04 23:26 ` Jakub Narebski
2008-02-05 0:00 ` Jonas Fonseca
2008-02-05 0:28 ` Junio C Hamano
2008-02-05 1:21 ` Jakub Narebski
2008-02-05 9:59 ` Junio C Hamano
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=200802031139.48752.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=adam@npjh.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=gitster@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).