SCIENTIFIC-LINUX-USERS Archives

March 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dag Wieers <[log in to unmask]>
Reply To:
Dag Wieers <[log in to unmask]>
Date:
Thu, 8 Mar 2012 09:28:06 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (34 lines)
On Tue, 6 Mar 2012, Mark Stodola wrote:

> Does anyone have any recent experience writing documentation in docbook with 
> current tools?
> I'm in the process of updating a user manual that I wrote several user ago in 
> docbook xml that used xsltproc, fop, and docbook 4.1.x definitions.  It looks 
> like I've fallen behind and new tools are around.  A search shows that 
> supposedly TUV is using a tool set called Publican, but information is 
> scarce.  I also see docbook-utils and docbook-utils-pdf as available 
> packages.  Grabbing the latest fop and definitions is giving me quite a 
> screen full of errors.  There must be an easier way by now.  I'd like to 
> continue to generate html, pdf, and ps output at a minimum.
>
> What are people using for a tool chain these days?

I prefer AsciiDoc for writing/collaborating on documentation. And am 
working on an ODF backend for AsciiDoc so you can go directly from 
AsciiDoc to ODF to PDF/DOC/... while styling through LibreOffice.

     http://github.com/dagwieers/asciidoc-odf

AsciiDoc converts to HTML by default.

     http://www.methods.co.nz/asciidoc/

But since AsciiDoc translates well to DocBook, you can go from 
AsciiDoc to DocBook to FOP to PDF, as you're used to.

-- 
-- dag wieers, [log in to unmask], http://dag.wieers.com/
-- dagit linux solutions, [log in to unmask], http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]

ATOM RSS1 RSS2