Jeff Garland wrote:
On Wed, 15 Sep 2004 08:26:35 +0800, Joel wrote


I could hack these tools (QuickDoc is especially easy) to
remove the boost- and Spirit-specific features, but I would
prefer to be able to use out-of-the-box generic documentation
tools that are actively used and maintained by a community larger
than just me.

Any recommendations on what I should do?

It's easy to decouple QuickBook a bit. A command line flag can be used to make it generate either DocBook or BoostBook (a superset of DocBook). I think that's what I want to do now. This question has been asked a couple of times now.


You'll be a super-hero (you're already a hero :-) if you can allow some other
document forms.  That is replacing this top stuff which is only good for
library documentation

[library date_time
    [version 1.0]
    [authors Jeff Garland]
    [copyright 2001-2004 CrystalClear Software]
    [category misc]
    [purpose A killer date time library]
]

with something like this

[article
    [authors Jeff Garland]
    [copyright 2001-2004 CrystalClear Software]
    [title A killer date time library]
]

If it's a pain, don't sweat it I can always transform the xml if needed...

That's the plan. I noticed this need when writing the QuickBook documentation itself. It's not a library. It would be a waste if QuickBook is only useful for library documentation.

I think it's easy to do. Yet, I'd like to hear from the boost-book
guys how to best achieve this. Doug? Guys?

Regards,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net


------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs

Reply via email to