Dear Gil: could not resist and tried to build rexxref.pdf, which I finally succeeded thanks to your toolset and explanation!
At first the process seems to have hung, as the "doc2fo.cmd" step was just hanging there. After a few minutes I kept interrupting it, lurked around, just to retry it and so on. Then, when leaving it alone for quite some time, "all of a sudden" the fo file got created! :) It turns out that doing the transformation from docbook to fo takes quite some time. So I tried to use the "--timing" switch to gain some insight and to give the person sitting in front of the computer some feedback such that it does not appear to be hung. With the --timing switch the following screen output gets created: G:\oorexx.tmp\gilDocs>xsltproc --xinclude --timing -o out-rexxref\rexxref.fo pdf.xsl F:\work\svn\oorexx\docs\trunk\rexxref\en-US\rexxref.xml Parsing stylesheet pdf.xsl took 0 ms Parsing document F:\work\svn\oorexx\docs\trunk\rexxref\en-US\rexxref.xml took 8170 ms XInclude processing F:\work\svn\oorexx\docs\trunk\rexxref\en-US\rexxref.xml took 447752 ms Making portrait pages on A4 paper (210mmx297mm) Running stylesheet and saving result took 28080 ms So in total it took eight minutes (484002 millisecs or 484.002 seconds) to create the fo file on my Windows 10 machine using xsltproc (without any visual feedback). Then running fo2pdf.cmd in a relative short time the 12 MB fo file got transformed to a great looking 7 MB PDF file, *great* ! Looking at the freshly generated rexxref.pdf file I do not find the TOC problem that you have described. Comparing "your" rexxref.pdf with the current "rexxref.pdf" of the ooRexx project, the depths of the TOCs seem to be the same! I.e. if there is a need for a depth of four (like with methods of classes) then it is in both versions (and looks very helpful)! --- In any case this means that you have really solved one of the biggest problem of the project, in making the production of the documentation independent of Pelican, yet being able to create the same formatted documentation! This is just *great*! Also it means that more people become able to work with the documentation! Thank you very much for all of your efforts so far, kudos to you! ---rony On 25.02.2020 12:57, Rony G. Flatscher wrote: > > Dear Gil, > > this is super, thank you *very* much!! > > On 24.02.2020 19:48, Gil Barmwater wrote: >> >> It is time to make the package available to this group! I have updated the >> package, zipped it up, >> transferred it to another system, installed it and successfully built the >> rexxref, rxmath and >> readme documents. I apologize for the size of the package - 33.2 MB - but >> most of that size is >> due to FOP. I strongly recommend that after downloading it from here >> <https://www.dropbox.com/s/s5d9mwx63xru1tk/orxbldoc.zip?dl=0> that you first >> extract only the >> read1st.txt file. It will explain the installation requirements as well as >> how to use it. >> > Have downloaded everything and will look into it ASAP (may take a few days > though) as I would like > to become able to generate the docs myself as well. > >> Just a couple of comments: as I have not attempted to build all of the >> ooRexx documents, I >> suspect that there are still some "surprises" lurking out there. I have not >> solved the "extra" >> levels issue in the TOC but felt this was not a serious enough problem to >> delay making the >> package available. And, of course, any questions, comments, criticisms or >> suggestions for >> improvement are welcome. >> > Ad TOC: maybe this <http://www.sagehill.net/docbookxsl/TOCcontrol.html> can > be of help? > > Best regards > > ---rony >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel