Rene Rivera <[EMAIL PROTECTED]> writes: > Not sure if that's what we all want ;-) I should come clean and mention > what I currently want... I have a use I want to put quickbook to. I > need/want to use the quickbook syntax within a wiki context. This comes > from evaluating the variety of wiki formats and realizing that they just > plain suck. The structuring features of quickbook alone blow away any > current wiki format. So ultimately I want a quickbook library I can plug > into a web server, either directly or through PHP, to translate from > user edited quickbook content to XHTML fragments, as fast as possible.
Like the Trac wiki currently does with ReStructuredText (using Python, of course ;-) I've been hoping we'll make a Trac plugin for QuickBook, too. > But to put it closer to "home". It would really cool if the > officially supported Boost wiki used quicbook content. Also it would > be nice to be able to dynamically present Boost documentation on the > website without having to go through the slow docbook translation > and check in into CVS. Yep. >>> In fairness, my suggestion does impose the requirement to have Python >>> installed, even on developers who aren't interested in Python, but >>> doesn't everybody have Python already? ;-) >> >> Most people who use Boost, but not everyone. > > And more likely the decision of what tools to use are not up to the > developer. What developer? I mean, who are we trying to reach with QuickBook? Is it so crucial to be able to serve that small minority of developers who are allowed to use C++ but not Python? -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
