In spite of the lack of posts on this subject recently, P.O., Rony and I have been working diligently to make this work (building the docs w/o requiring access to the 'net). I can now report that we have finally succeeded! And the results are nothing short of spectacular! In addition to using the DTD and style sheet files that have been installed on the local system, we have moved to the most recent version of the style sheets - 1.79.2 - which is now located on GitHub (DocBook has moved their repository from SourceForge). As soon as I update the package documentation, I will commit the changes to SVN.

So how good is the new version of the package? To quote P.O. on his results on Jenkins: "First version used one hour for the PDF generation and 1.5 hours for the HTML. Already this was better than Publican, and MUCH more reliable!

Today PDF generation take 10 minutes (!) and HTML 27 minutes, a complete build, including also the �Buildmachine� in less than 40 minutes."

P.O. and Rony have also been working on adapting the package for use on the Mac! I will let them describe where that effort stands but it is interesting to note that some of the tools needed by the package come already installed on the Mac and some flavors of *ix. So it is not impossible to believe that we could eventually produce our books on most any platform!

Gil B.

On 4/27/2020 12:48 PM, Gil Barmwater wrote:
I, too, have been researching how to do a "local" build of the documentation, i.e. not requiring Internet access during the process. I believe I have determined what is required and am in the process of developing modifications to the package which I will then test. I will post again with the results.

Gil

On 4/27/2020 10:00 AM, Rony G. Flatscher wrote:
On 27.04.2020 15:49, P.O. Jonsson wrote:
Thanks Rony for the information, I have been to most of these places already :-( but indeed you are right, I am entirely in the dark since I do not really understand the logics behind these things.

That said - I will give it a few more tries, but you raise a question that should maybe be explored: How much work would it be to remap the build process to Linux? On Jenkins server (running Ubuntu 18.04) there is plenty of processing power available, also when running Jenkins server.
The step from xml to fo with xsltproc could work out of the box (just checked on my Ubuntu machine, it has docbook 4.5 support in /etc/xml and the files in /usr/share/xml/docbook). The step from fo to pdf needs Java and Gil's findings could be used to get it running on Ubuntu as well.

Did you compare the output quality on your build with Cygwin?
Yes, skimmed through the pdfs and they look as before.
� I remember that for the Publican build the quality of the output was inferior to builds on Windows
This has been strange, probably (pure speculation) the quality of the output was inferior because
the quality of the bitmaps got tampered with.

---

Will try out the xml->fo step on Ubuntu and report back ASAP.

---

Just a word ad Gil's incredible effort to get that going on Windows: just witnessing how difficult it has been (not yet solved) to get it up and running on Windows and still getting locally available dtd/xsl to be honored, it is just incredible how much effort and patience Gil must have thrown at this beast! Allowing creating the docs in the end after a frustratign period where this ability was not there anymore or at least waning due to outdated tools that got more and more problems on Windows!

Even if the documentation could be created on Linux it still would be very important to get the Windows build take locally available dtd/xsl files to speed it up as not everybody has Linux available!

---rony




_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

--
Gil Barmwater



_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to