For anyone interested I have put everything in my dropbox in the folder ooRexxDocs
There are some build errors for winextensions and for the oo- documents, this needs to be looked at by someone, seems like really minor things missing. https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0 <https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0> Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 26.02.2020 um 19:36 schrieb P.O. Jonsson <oor...@jonases.se>: > > Dear Gil, > > I have downloaded your package and started to build the documents. It is an > *Incredibly* simple setup! WOW! Having fiddled with Publican some time now it > is a real ease. I have built the complete set of documents (including > oodialog docs) 3 times now and the results are identical every time, this was > not always the case with Publican… > > I notice you create one folder out-<item> for each item, for me 16 folders in > total, maybe it is sufficient with one output folder? It would be easier to > pick the documents up in an automated process (from Jenkins). But this is not > a big thing. > > It is not possible to build all documents in parallel, as I could do with > Publican, but building all documents sequentially took 1 hour and 12 minutes > on a i7 Windows 10 Machine. Leaving out the ooDialog documents will cut the > time considerably. > > A simple way to get some timing data is to echo %time% before and after each > build. I also made a batch file that launches the build of all the documents > one after the other. > > I have not tried your version with 3 levels, I have build with 4 levels in > the TOC. > > I found several examples where your build process excels over the current > Publican process > > - your process get the Copyright dates correct (up to build year, not to 2017 > or 2018 as in Publican build) > > -I have seen pages where text what pushed over the edge of a page in Publican > where your process gets it correct > > -your process renders text in drawings better than Publican. > > I hope the attached document is not stripped of for the list, here I have > made the comparison in the built documents. > > <Comparison Publican - Gil.docx> > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se <mailto:oor...@jonases.se> > > > >> Am 25.02.2020 um 20:43 schrieb Gil Barmwater <gbarmwa...@alum.rpi.edu >> <mailto:gbarmwa...@alum.rpi.edu>>: >> >> I have now added a warning message to the doc2fo.cmd script that running it >> may take several minutes. I experimented with the --timing switch but most >> of the time is spent in one spot so it still appears to be "hung" there so I >> didn't put it in. I have added the ability, however, to provide additional >> parameters to the xsltproc program so that the user could specify that they >> wanted to use that flag (or others) without having to modify doc2fo.cmd. >> >> I also found the parameter that controls the TOC depth! I have set it to 3 >> to match our historical document appearance but, by using the same mechanism >> mentioned above, a user could change it to 4 if they prefer that look. I >> need to document how to use this option (as well as a corresponding one for >> FOP which would allow one to change the JAVA heap space) and build a new >> package. I will wait a day, however, in case there is additional feedback >> that I can incorporate. >> >> Gil >> >> On 2/25/2020 9:57 AM, Rony G. Flatscher wrote: >>> Dear Gil, >>> >>> On 25.02.2020 15:31, Gil Barmwater wrote: >>>> Thanks so much for the feedback! I was unaware of the "timing " switch so >>>> will consider adding >>>> that to my package in order to give the user some indication that things >>>> are still running. On my >>>> laptop the transform step also takes >5 minutes when building the rexxref >>>> so some visual feedback >>>> would be helpful. >>> Yes, or simple warning that some books may take ten minutes or more (if >>> they get built faster and >>> faster over time, no one would complain ;) ), then the user's expectation >>> are "managed" to take time >>> and patience to wait... >>>> Ad the TOC: the build of ooRexx 5.0.0 that I have installed is at 11978 >>>> which includes a rexxref >>>> at 11974. That version only has three levels of entries compared to what >>>> my package produces which >>>> has four. I have not checked any other more recent versions of the rexxref >>>> so I'm not sure when >>>> the fourth level was introduced. As I mentioned to P.O., the extra level >>>> seems to me a bit >>>> distracting but I am happy to leave it in if that is the general consensus >>>> of the development >>>> team. It should also be noted that even if there are only three levels in >>>> the TOC, the "bookmarks" >>>> displayed by Acrobat Reader on the left of the document do contain all >>>> four levels making >>>> navigation to a specific section simple. >>>> >>> Oh, o.k. I see now. >>> >>> Personally, I actually like it as one can get an even better overview of >>> the structure and the >>> concepts that get documented there. >>> >>> ---rony >>> >>> >>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> -- >> Gil Barmwater >> >> >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto: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
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
