Well, I had apparently decided that the PDF_files directory needed to be
in the package because I had created the appropriate info.txt file but
then forgot that it needed to go in the package :-[. I have now added
the folder and file to both the delta folder and the package zip-file.
I also discovered the problem Rony found with the "No adjustColumnWidths
function available" was also found in the PDF process. Luckily, the fix
was as easy as changing a parameter in the stylesheet. The package and
delta now have an updated xhtml-common.xsl file.
Perhaps this is the last surprise ;-).
Gil
On 3/29/2020 6:06 AM, P.O. Jonsson wrote:
Am 29.03.2020 um 01:15 schrieb Gil Barmwater <gbarmwa...@alum.rpi.edu
<mailto:gbarmwa...@alum.rpi.edu>>:
Once again I seem to have confused the folks I was trying to help
<sigh>. In version 2, the folders fo_files and log_files are included
and each contain a single, one-line file names info.txt. This was
supposed to eliminate the need to create them dynamically. I thought
I had remembered that FOP would create the PDF_files folder the first
time a PDF is created but perhaps I am wrong. If so I will make sure
that this folder is part of the package (with an info.txt file) as
well. Sorry for not explaining that change. Gil
per Aspera ad Astra :-)
I have compared version 1 (pdf only) with version 2 (pdf and html) and
indeed in v2 the fo_files and log_files are included and contain
single, one-line files info.txt. But the PDF_files directory is
missing, hence the confusion. If you add that with the distro there is
no need to check dynamically.
Re testing: I am building the PDFs in the merge of V1+ Diff now to see
that it runs as it should, thereafter I will go for the html. Every
run takes and hour and a half so there might be some time before I
have anything to report.
I noticed that you (I guess?) have amended the XML in the
„buildmachine“ folder so I will try to build that as well. I noticed
earlier that inside the buildmachine folder there was a reference to
ooRexxBuild rather than to buildmachine. I changed the name of the
folder to ooRexxBuild and then I could get a book.
Regarding the name buildmachine: The book in question describes not
only the (obsolete) build machine from before Jenkins was moved, there
is also information on how to build ooRexx in general. I think it
would make sense to change the name from buildmachine to ooRexxBuild
(or oorexxbuild to be inline with the rest), what is the opinion of
the developers? I had in mind to update this book once I am finished
with the samples. All the info from the WIKI and Erichs info on how to
build could be documented here, as well as my own notes from how to
build on macOS and a plurality of Linux dialects.
/P.O.
_______________________________________________
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
