Hi, I had a go. I'm using windows ME, and had to do a lot of stuff manually, since I'm not using Cygwin. I had to edit catalog.xml, removing some extra punctuation and changing some of the slashes from windows style to uri style (ie. c:\src\boost\ to c:/src/boost/). After that I wrote a little batch file to run xsltproc and it worked fine. But of course, that should be fixed in boost build eventually.
I did do one stupid thing though. When I first went to download the DocBook DTD, I downloaded just docbookx.dtd instead of the whole archive. I think this was just me being clumsy, but you could say 'download the zip archive' or something. Daniel ----- Original Message ----- From: "Douglas Paul Gregor" <[EMAIL PROTECTED]> Newsgroups: gmane.comp.lib.boost.devel Sent: Thursday, March 27, 2003 5:30 AM Subject: [BoostBook] Guinea pig request > BoostBook is nearing the point where building documentation is as easy as > building libraries. The Boost.Build v2 modules for BoostBook (and > associated tools) are quite functional and work well for me, but I want to > verify the they will work well for someone else. > > I would like a volunteer to try out the BoostBook tools to see if they can > easily build documentation, and report your successes, failures, and > general level of frustration to the Boost documentation list or to me > personally so I can improve the situation for future users and developers. > You'll need a few tools, a very recent checkout of Boost CVS, and > possibly a little patience, but everything is explained (I hope) in the > "Getting Started" guide here: > http://www.cs.rpi.edu/~gregod/boost/tools/boostbook/doc/html/ > > Any takers? Please? > > Doug > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
