[boostbook] xsltproc using the internet?
Howdy, I'm trying to build the boostbook docs. Having looked through the boostbook.jam file, seems like I should get a warning message if any DTDs are going to be fetched over the internet. I set the location of the DTD and XSL files in user-config.jam to values that I *think* are correct. In any case, It appears that the command "xsl-xsltproc" is still fetching some data remotely. A) Should I be receiving a warning about this, or am I misunderstanding the boostbook jamfile B) How exactly do I make it stop? I'm trying to use the docbook-dtd and docbook-xsl information installed on my machine using a package manager (fink). If I incorrectly specify these directories, should I expect an error that specifically points this out, or general "badness" instead? Thanks, ron
On Friday 13 February 2004 12:19 pm, Ronald Garcia wrote:
A) Should I be receiving a warning about this, or am I misunderstanding the boostbook jamfile
If you omit it, you should receive a warning. If you get it wrong, you'll end up getting an error when it gets to the DocBook->whatever stage.
B) How exactly do I make it stop?
(This is a known, annoying bug in boostbook.jam): when you change user-config.jam (or whichever configuration file you're using), remove "catalog.xml" from the directory where you are generating the documentation. Otherwise, it will use the old locations. Doug
Hi Doug, Douglas Gregor wrote:
On Friday 13 February 2004 12:19 pm, Ronald Garcia wrote:
A) Should I be receiving a warning about this, or am I misunderstanding the boostbook jamfile
If you omit it, you should receive a warning. If you get it wrong, you'll end up getting an error when it gets to the DocBook->whatever stage.
Got it.
B) How exactly do I make it stop?
(This is a known, annoying bug in boostbook.jam): when you change user-config.jam (or whichever configuration file you're using), remove "catalog.xml" from the directory where you are generating the documentation. Otherwise, it will use the old locations.
Thanks. I downloaded copies of docbook-dtd and docbook-xsl from the listed sources, and that worked like a charm. I will let you know if I figure out how to use it with the package installation under OS X. A few other comments: Since the files in my CVS don't have write permissions until I explicitly change them, building the boostbook html fails for the files that already exist (the redirect files) in CVS. It might be worthwhile to mention in the documentation that folks building boostbook in a CVS tree might need to erase the redirecting html files before running bjam. Also, is there an archive (zip, tarfile, etc) of the generated html that could be dropped into the boost tree? These days I only use boost CVS trees, and when I'm disconnected from the internet I sometimes need to check docs for libraries. It would be great if I could just drop the documentation into the tree if it's not going to exist in human-palatable form in CVS anymore. Thanks for the help, ron
On Friday 13 February 2004 05:05 pm, Ronald Garcia wrote:
Since the files in my CVS don't have write permissions until I explicitly change them, building the boostbook html fails for the files that already exist (the redirect files) in CVS. It might be worthwhile to mention in the documentation that folks building boostbook in a CVS tree might need to erase the redirecting html files before running bjam.
Ah, right. I've mentioned this in the docs.
Also, is there an archive (zip, tarfile, etc) of the generated html that could be dropped into the boost tree? These days I only use boost CVS trees, and when I'm disconnected from the internet I sometimes need to check docs for libraries. It would be great if I could just drop the documentation into the tree if it's not going to exist in human-palatable form in CVS anymore.
Yes, it would be nice to generate those. Probably just another line in the script Metacomm is using to build the docs. Doug
Douglas Gregor <gregod@cs.rpi.edu> writes:
On Friday 13 February 2004 05:05 pm, Ronald Garcia wrote: Ah, right. I've mentioned this in the docs.
Also, is there an archive (zip, tarfile, etc) of the generated html that could be dropped into the boost tree? These days I only use boost CVS trees, and when I'm disconnected from the internet I sometimes need to check docs for libraries. It would be great if I could just drop the documentation into the tree if it's not going to exist in human-palatable form in CVS anymore.
Yes, it would be nice to generate those. Probably just another line in the script Metacomm is using to build the docs.
Done, http://tinyurl.com/jvyc has now link to zipball and tarball. I am not a Unix guy, so the tarball might be not built according to all the necessary rules. If something is built incorrectly, I would appreciate if you could tell me the proper tar command line. The link to zipball and tarballs should probably go to the main page though. -- Misha Bergal MetaCommunications Engineering
On Friday 13 February 2004 04:25 pm, Misha Bergal wrote:
Douglas Gregor <gregod@cs.rpi.edu> writes:
Yes, it would be nice to generate those. Probably just another line in the script Metacomm is using to build the docs.
Done, http://tinyurl.com/jvyc has now link to zipball and tarball. I am not a Unix guy, so the tarball might be not built according to all the necessary rules. If something is built incorrectly, I would appreciate if you could tell me the proper tar command line.
Thanks again!
The link to zipball and tarballs should probably go to the main page though.
Sure. Doug
participants (3)
-
Douglas Gregor -
Misha Bergal -
Ronald Garcia