[prev in list] [next in list] [prev in thread] [next in thread]
List: ipcop-cvs
Subject: [IPCop-cvs] CVS: IPCopDoc README.output,1.1,1.2
From: Harry Goldschmitt <goldharv () users ! sourceforge ! net>
Date: 2002-08-23 19:34:01
[Download RAW message or body]
Update of /cvsroot/ipcop/IPCopDoc
In directory usw-pr-cvs1:/tmp/cvs-serv15990
Modified Files:
README.output
Log Message:
Included info on xmlto and a little on FOP and saxon.
Index: README.output
===================================================================
RCS file: /cvsroot/ipcop/IPCopDoc/README.output,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** README.output 12 Aug 2002 07:13:11 -0000 1.1
--- README.output 23 Aug 2002 19:33:59 -0000 1.2
***************
*** 7,19 ****
run in the Windows environment.
! There are two ways to generate output from XML, DSSSL and XSLT. DSSSL files
! are found on the SGML side of the house. The Openjade processor will use
! DSSSLs to generate its output. XSLT files are found on the XML side of the
! house and are used by xsltproc to generate its output.
! I have been using both to generate the output. For all output other than
! HTML, Openjade is easier to use. Unfortunately, it seems not to be able
! to generate "chunk" html output or allow you to name the resulting .html
! file(s). xsltproc is far superior for generating html.
Non-HTML Output
--- 7,23 ----
run in the Windows environment.
! I have converted my environment from Red Hat 7.2 to 7.3 at the suggestion
! of Tim Waugh who wrote the excellent xmlto program. RH 7.3 contains fixes
! for many of the problems with previous DocBook toolchains.
! There are two ways to generate output from XML, DSSSL and XSLT. At the
! current time DSSSL output is generated by OpenJade and its associated
! shell scripts. It will easily generate all forms of output, except
! "chunk HTML". Chunk HTML creates separate files for each web page,
! avoiding the problem of a browser having to download a huge web page,
! before it can be viewed.
!
! I have been using xsltproc to generate web pages, using an XSLT style
! sheet from the Linux Documentation Project.
Non-HTML Output
***************
*** 24,73 ****
will generate a ipcop-installation-en.pdf file in the current directory.
db2pdf, db2ps, db2rtf are all available, as is docbook2text. db2html is
! available, but has several deficiencies.
! Before running any of these commands get all the images from the IPCop
! TWiki web site. Put them in an image directory off the directory that
! holds your DocBook files.
HTML Output
___________
! I've been using the xsltproc command, along with the Linux Documentation
! Project's XSLT to create html output. The LDP's print XSLT does not
! currently work, and as far as I can see, xsltproc isn't much better.
! the LDP's XSLT is available at <http://www.tldp.org/authors/tools/ldp-xsl.zip>.
The use of this stylesheet as well as a very good intro to DocBook can
be found at <http://tldp.org/LDP/LDP-Author-Guide>.
! I've been using xsltproc in the following way:
! 1) Get all the images (png and jpg files) from the IPCop TWiki site and
! put them into an images directory off the directory that will end up with
! the html files.
! 2) cd to the directory that will contain the html files. xsltproc -o
doesn't seem to work.
3) Issue:
$ xsltproc /path/to/ldpxsl/dir/ldp-xsl/ldp-html-chunk.xsl /path/to/install.xml
! 4) There should be several files in the current directory, including
! index.html. This is the start of the manual.
! GOTTCHA
_______
! There is one problem. The Openjade suite does not recognize the:
!
! <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
! "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
! or
! <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
! "file:///path/to/docbookx.dtd">
! sequences at the start of the document. Unfortunately, xsltproc requires
! them. Openjade only works if the first statement is:
!
! <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN">
!
! I've been playing games, commenting out the lines containing the dtd
! locations when I run Openjade and uncommenting them when I run xsltproc.
! Also, be aware that if the http: version of the docbookx.dtd is used,
! xsltproc will really download it from the web site, every time it's run.
--- 28,84 ----
will generate a ipcop-installation-en.pdf file in the current directory.
db2pdf, db2ps, db2rtf are all available, as is docbook2text. db2html is
! available, but only creates large html documents.
! On the other hand, these commands seem to give the best diagnostics of
! problems with your source.
!
! I've tried the apache FOP processor and it produces reasonable output,
! given a good XSLT style sheet.
!
! In addition, xmlto can be used to create printable output. It is a
! wrapper around xsltproc. It calls PassiveTeX to produce printable output.
! At this time, PassiveTex can't handle relative paths to directories. So,
! I've changed the path to the images directory to /path/to/IPCopDoc/images.
! Please use an editor to change /path/to to the correct path. PassiveTeX,
! apparently, doesn't do any line rules, like those around tables. Column
! widths for table columns have to be explicitly specified.
HTML Output
___________
! I've been using both the xsltproc and xmlto commands, along with the
! Linux Documentation Project's XSLT to create html output. The LDP's
! print XSLT does not currently work.
! The LDP's XSLT is available at:
! <http://www.tldp.org/authors/tools/ldp-xsl.zip>.
The use of this stylesheet as well as a very good intro to DocBook can
be found at <http://tldp.org/LDP/LDP-Author-Guide>.
! Tim Waugh's xmlto home page is:
! <http://tim.cyberelk.net/tim/xmlto/index.html>
!
! I've been using both xsltproc and xmlto in the following way:
! 1) Get all the images (png and jpg files) from the IPCop CVS repository.
! 2) Edit the .xml file and change /path/to/IPCopDoc to the path to your
! images directory.
! 3) cd to the directory that will contain the html files. xsltproc -o
doesn't seem to work.
3) Issue:
$ xsltproc /path/to/ldpxsl/dir/ldp-xsl/ldp-html-chunk.xsl /path/to/install.xml
! or
! $ xmlto html -x /path/to/ldpxsl/dir/ldp-xsl/ldp-html-chunk.xsl /path/to/install.xml
!
! 4) After the programs run there should be several files in the current
! directory, including index.html. This is the start of the manual.
! WINDOWS
_______
! If you are using Windows to produce output from DocBook xml, both the
! apache FOP program and saxon are available. They are written in java.
! I haven't had the time to play with these programs. If you wish, please
! add information on how to use them.
! Harry Goldschmitt
! 08/23/2002
-------------------------------------------------------
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
_______________________________________________
IPCop-cvs mailing list
IPCop-cvs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-cvs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic