asciidoc, git, and DocBook XSL manpages output

[Michael(tm) Smith-4]

Greetings from Tokyo.

I'm the maintainer of the manpages stylesheet in the DocBook XSL
Stylesheets distribution, and I'm writing to say I've done a
little exploration into asciidoc after noticing the git
maintainers are using it as the source for their docs, including
their man pages.

I've very recently made a number of tweaks and additions to the
manpages stylesheet to fix some general problems I noticed in
looking at the git man pages. The additions include adding native
support to the manpages stylesheet for rendering callouts (the git
team was using a patch to handle them) and putting asciidoc
"Listing Blocks" (DocBook literallayout content) in a proper
monospace font (though that has effect only in PS output from the
man page, not in TTY output). (For making the monospace font, the
git doc build is currently using some custom asciidoc config to
cause a hack that attempts to pass some literal groff markup through.)

Anyway, I'm interested in making sure that any other projects and
individuals using the asciidoc to author document source for man
pages don't have to rely on any patches or hacks to get the
man-page output they expect. So, I'm subscribed to this list now,
and want to say that if you have bug reports or suggestions for
improvements to the handling of your asciidoc source when
processed through the manpages stylesheet, I'm happy to discuss
them here any time and/or on the docbook-apps mailing list -

  http://wiki.docbook.org/topic/DocBookAppsMailingList

I also have some questions and comments myself about the DocBook
XML refentry output from asciidoc. I'll post those in a separate
message.

  --Mike

--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/


_______________________________________________
asciidoc-discuss mailing list
asciidoc-discuss@...
http://lists.metaperl.com/cgi-bin/mailman/listinfo/asciidoc-discuss