> Am 29.04.2020 um 12:59 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > Hi P.O., > On 28.04.2020 22:16, P.O. Jonsson wrote: >> Hi Rony and thanks for the script. I have adapted it to my needs and can >> make the .fo files now. As it turns out xsltproc is included with macOS >> itself so once I got the redirect for the http: working everything fell into >> place. I use homebrew instead of macPorts bit it works approx the same. The >> XML files are here for my setup: >> >> export XML_CATALOG_FILES="/usr/local/etc/xml/catalog“ > Are you sure you need to set that environment variable? The Linux and Mac > versions of xsltproc are setup by default to use the catalog files which they > know the (their standard) location. > I will try without it. I took this setting from the installation of xsltproc from Homebrew. In the meantime I learned that xsltproc is standard on macOS so the version i installed using homebrew probably is not active.
Using the options —nonet —load-trace I could confirm where the catalog files reside, here one of 650 calls that now go by file IO rather than over http:, just for rexxpg Loaded URL="file:/usr/local/opt/docbook-xsl/docbook-xsl/VERSION.xsl" ID="(null)“ When I look in /usr/local/opt there are symlinks to /usr/local/Cellar/docbook-xsl/1.79.2_1/docbook-xsl, these are installs from homebrew. In /usr/local/etc/xml here is a single file catalog (without extension) with a lot of pointers to <?xml version="1.0"?> <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <nextCatalog catalog="file:///usr/local/opt/docbook/docbook/xml/4.2/catalog.xml"/> and so on, so I think it is as it should. Remember that macPorts and Homebrew use entirely different strategies where and how to store files. > Therefore I suggest, once this nut got cracked to document briefly the > architecture of docbook (dtd and xsl), the mechanics and the > interdependencies. In addition a little howto for creating a new Rexx book > which would automatically explain the interdependencies and naming > conventions. > Agree. I am documenting my steps as I go along for a start. > In the end, after xsltproc runs on all platforms and fop generates comparable > results on all platforms, it may be worthwhile to look into creating > "epub"/"epub3" renderings of the books (there seem to be docbook-xsl > definitions for them) allowing them to be used in electronic bookreaders > (which may allow to change the fonts, their sizes, have bookmarks placed > etc.). > For the future, I need to get back to the samples business :-) > Best regards > > ---rony > P.S.: Also, once everything is set up and humming away, it may be interesting > to create a pure Java solution, i.e. replacing xsltproc by Apache > Xalan/Xerces, that should be able to run unchanged on all platforms. More important is to get 5.0.0 to release or at least GA status > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
