From: "J. Bruce Fields" <bfields@fieldses.org>
To: git@vger.kernel.org
Subject: asciidoc, docbook, "book" doctype
Date: Sun, 10 Dec 2006 22:20:14 -0500 [thread overview]
Message-ID: <20061211032013.GA16054@fieldses.org> (raw)
I've been fooling around with producing a longer piece of documentation
using material from the tutorials, etc., using the docbook backend and
"book" doctype. It's not working quite the way I'd expect. For
example, it doesn't format the literal blocks correctly, and man page
links aren't producing useful clickable links. Should I be going about
this some other way?
All I really want is automatically generated tables of contents and
cross-references.
reply other threads:[~2006-12-11 3:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061211032013.GA16054@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
/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).