Mike Noyes wrote: > Greg & Julian, > Here is what we're doing currently for our guides. > > DocBook XML source is generated and placed in our cvs repository. > Generated xhtml, plain text, pdf, and PostScript versions are placed > in cvs with the DocBook XML source. They are then exported daily to > our /pub/doc directory on the shell server (note: this step isn't > implemented yet).
Mike, Thanks this was very helpful. > > CVS doc tree > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/doc/ > > shell server /pub/doc directory > http://leaf-project.org/pub/doc/ > > daily.sh crontab shell script (feedback on this script is appreciated) > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/devel/mhnoyes/sf-admin/ I didn't see anything wrong with daily.sh. However, I do have a question on how to handle images that can be inserted into docbook files using this mechanism described above. The Richard J. Lohman guide "Creating a Firewall Using EigerStein" is missing several images. How can images be used without being lost, checked into cvs, and named so that name space collisions do not occur? For example, I may want to call a file intranet.gif just like Richard did. Here is a sample of the missing images. <a href="es-contents.html"><img src="tux_cont.gif" width="27" height="32"> Contents</a><br> <a href="es-appsused.html"><img src="tux_prev.gif" width="27" height="32"> Applications Used</a><br> <a href="es-primer.html"><img src="tux_next.gif" width="27" height="32"> Linux Primer</a> http://leaf-project.org/pub/doc/guide/install-eigerstein/es-rtaddlnets.html <div align="center"><img src="intranet.gif" width="600" height="400" border="0" name="intranet.gif" align="middle"></div><P> Greg Morgan ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
