Eric Niebler writes: > Aleksey Gurtovoy wrote: > > 'xsltproc' under Cygwin, I suppose? Hmm, it works for me (although it's > > unbelievably slow comparing to native binaries) with DocBook 1.66.1. > > Here's my xsltproc version info: > > > > Using libxml 20609, libxslt 10106 and libexslt 804 > > xsltproc was compiled against libxml 20609, libxslt 10106 and libexslt 804 > > libxslt 10106 was compiled against libxml 20609 > > libexslt 804 was compiled against libxml 20609 > > > > Is yours one different? > > > > > Actually, this isn't under cygwin -- that's just the local directory > where I have the docbook xsl files.
Did you update the tools as per my original message: > > ****************************************************************************** > Important > > If you are using non-Cygwin xsltproc binaries on Windows, to be able > to work with the new stylesheets in the CVS you need to grab a patched > version of the tools from here -- > http://www.meta-comm.com/engineering/boost/xsltproc-win32.zip > > ****************************************************************************** ? > It might have been easier to figure out if I had given you the whole error: > > Writing xpressive/reference.html for section(xpressive.reference) > I/O error : No such file or directory > runtime error: file > file:///C%3A/cygwin/home/ericne/docbook-xsl-1.65.1/html/chunker.xsl line > 215 element document > > Turns out the trouble was that there was no html/xpressive subdirectory. > After creating it manually, it worked. Any chance you could fix it to > create the directories automatically? They are created automatically with the patched versions of libxslt/libxml we provide. I'm working on making sure the patch gets into the next version of the "official" binaries. > > The other more serious problem is that relative paths to images and the > CSS are not getting fixed up to accomodate the extra directory. Surely they are. I specifially spent half an hour fixing this. > So now everything except my index.html is totally busted. :-( Please do a clean checkout/build and double check it. I just did it myself, and everything is in the CVS and works as expected. > I notice the boost docs you put up have the same problem. They don't. If you take a closer look, you'll see that the logo is there, and the "People" link (for instance) points to the right place, but doesn't work simply because there is no "people/people.htm" page in the site's root location (http://www.meta-comm.com/engineering/boost/nightly/); I just didn't went to the trouble of making a copy of the whole Boost site. -- Aleksey Gurtovoy MetaCommunications Engineering ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
