Re Windows 7 testing: I have been reading up on the thread from 2018 between Rick and Erich titled „Building the docs“ trying to document the steps necessary to myself.
This is the last mail I can read; there is an indication that there are a further pages with >1>2 >>> but when I click for the 2nd page I get a 404 error. Is there further mail exchange after this mail? I would like to have a copy. Re: [Oorexx-devel] Building the docs <https://sourceforge.net/p/oorexx/mailman/message/36502234/>From: Rick McGuire <object.rexx@gm...> - 2018-12-26 15:43:24 Attachments: Message as HTML <https://sourceforge.net/p/oorexx/mailman/attachment/CAPJz3Gt9c0BXb_pfq_ipqQz5xrRR-nkZ86uXn8nqu-33pKYG%3DA%40mail.gmail.com/1/> I'm sort of in a mixed state right now. I just made a clone of my VM. I'm going to set one up for FOP and the other for wkhtmltopdf and generate a full set both ways. Rick On Wed, Dec 26, 2018 at 10:36 AM Erich Steinböck <erich.steinboeck@...> wrote: > Amazing! > How does the generated PDF look like? Images, font, tables, index etc. > Can you upload (or else make available) the Ubuntu-built fop and > wkhtmltopdf versions of any doc you have done? > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 15.01.2020 um 20:40 schrieb Gil Barmwater <gbarmwa...@alum.rpi.edu>: > > As I noted in the previous post (below), merely letting XSLTPROC find the > Common_Content files does not let it do the transformation successfully. > Analyzing the changes I needed to make to those files to get past the error > messages from XSLTPROC reveals that Publican ignores the DOCTYPE declarations > in those files while merging their contents into the main document. So any > errors like a mismatch between the document type in that statement and the > top level tag are not caught by Publican. Neither are any entity > substitutions processed until the entire document is assembled. XSLTPROC on > the other hand treats each sub-document on its own, validating it against the > DOCTYPE statement and substituting any entity references before merging the > result into the document. > > So the bad news is that there is no work-around for this issue - the files > must be changed in order to be successfully processed by XSLTPROC. But the > good news is that the changes only affect the DOCTYPE statements which are > ignored by Publican when doing the merge so the changes should not prevent > building the documents with Publican. I am opening a document bug for these > changes - #270 - which will contain a patch file for all the Common_Content > files. If someone who has a Windows 7 system w/ a working Publican > installation could apply the patches and then verify that Publican can still > build the docs, we will know if the patches can be committed. > > One other bit of good news is that the combination of these patches and the > Common_Content sub-folder work-around are the only required changes in order > to use the XSLTPROC and FOP tools to successfully build our documents. I will > describe that process in my next post. > > On 1/6/2020 2:07 PM, Gil Barmwater wrote: >> >> Having gotten by the Common_Content issue, running XSLTPROC reveals another >> problem caused by the way Publican does the merge of the Common_Content >> files which I will describe in the next posting. >> > -- > Gil Barmwater > > > > _______________________________________________ > 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
