Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Actually, P.O., the HTML in your Dropbox should be enough to point me in the right direction. Right away I see that my process does not create the Common_Content or Images folders so perhaps the lack of images in my HTML. This should help a great deal! Thanks again. GB On 3/2/2020 4:01 PM,

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, I will do that (what version do you want?) but in the meantime please have a look in my dropbox , in oorexxdocs/oorexxDocs_11982_Publican you will find all pdf and html as they are created by the publican

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

I have progress to report on this front. After some debugging of stylesheets, I have been able to create a set of HTML files for the rxmath book (started small :-)). When I look at the HTML files for that book on ooRexx.org - the 4.0.0 version - I see lots of things that are different but at

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Hi Rony, I will have another look at this - the missing directories - for the next version although anyone other than the three of us should never encounter it :-). Ad using errorlevel: my goal has been to make the least number of modifications as possible to the tools being used but rather

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Thanks for that Enrico. I used the "built-in" capability of Windows 10 so it seems to be specific to that implementation. Of course putting a "info" file in each directory would have been another solution. Gil B. On 3/2/2020 8:24 AM, Enrico Sorichetti via Oorexx-devel wrote: Now to the

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, On 02.03.2020 14:09, Gil Barmwater wrote: > I definitely should have made that more clear for you and Rony. I, too, ran > into that issue as I > mentioned in my post when Rony stumbled over it. As I said then, the problem > arises because I > could not include the empty folders in the

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

>> Now to the specific items in the order you listed them. The issue with the >> "missing folders" is one I ran into as well. It comes from the fact that I >> was not able to include empty folders in the zip file and so had to create >> them the first time they were needed. I chose to do that

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

P.O., I definitely should have made that more clear for you and Rony. I, too, ran into that issue as I mentioned in my post when Rony stumbled over it. As I said then, the problem arises because I could not include the empty folders in the zip file. They only need to be created once so I did

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, I have not started looking at this yet, I got stuck since your last amendment did not work for me and I did not want to bother you until I found out why. I had the problem that the new version did not create the work folders correctly and I could not for my life figure out what I did

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

P.O., I have done some further digging into Docbook to HTML and the Docbook documentation has quite a lot to say about it. I hope most of this is in the html.xsl file but if you are running into problems, this link may help. GB On 3/1/2020

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Sorry P.O. :-(. I totally missed the fact that I wasn't passing an argument to svnversion. I will update the package (again!) at the same link. The version - 1.1 - is in the read1st.txt file at the bottom and I have kept it the same since we are just fixing bugs at this point. Thanks for

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, re > Am 01.03.2020 um 17:05 schrieb Gil Barmwater : > > Yes, that was the error I corrected yesterday so the Dropbox link should have > the fixed version. Either I cannot get to the latest version or you missed the proposal of today, the „doubledots“ was yesterday, today I am

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Yes, that was the error I corrected yesterday so the Dropbox link should have the fixed version. A little background on this obscure code: my setup is as follows - an older laptop that has Tortoise SVN and all of the package files and is where I did the majority of the development and

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, In the meantime I found another typo in doc2fo.cmd. It should be: where svnversion /q if %errorlevel% EQU 0 ( svnversion %docpath% > %docpath%\..\svnrev.tmp ) else echo ?> %docpath%\..\svnrev.tmp Otherwise svn revision will run on the wrong directory level. Since I am not using

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Thanks P.O. I suspected it might be something along those lines but I was not sure how the multiple HTML output files were specified. The examples tend to be simple single-file output. GB On 3/1/2020 9:38 AM, P.O. Jonsson wrote: Am 01.03.2020 um 15:27 schrieb Rick McGuire

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Thanks for the pointer Rick. I will look into it! GB On 3/1/2020 9:27 AM, Rick McGuire wrote: On Sat, Feb 29, 2020 at 11:13 AM Gil Barmwater mailto:gbarmwa...@alum.rpi.edu>> wrote: Hi Rony, First of all, thanks for the kind comments! And I really appreciate the feedback and

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

> Am 01.03.2020 um 15:27 schrieb Rick McGuire : > > Gil, I believe publican generated them directly using a style sheet. This can > also be done using xsltproc: > https://codeghar.wordpress.com/2012/02/07/generate-html-and-pdf-from-docbook-in-debian/ > >

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

On Sat, Feb 29, 2020 at 11:13 AM Gil Barmwater wrote: > Hi Rony, > > First of all, thanks for the kind comments! And I really appreciate the > feedback and suggestions as well. > > Now to the specific items in the order you listed them. The issue with the > "missing folders" is one I ran into as

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

When I first started investigating how the documents were created, I discovered that each document/book had its own entity file (*.ent). Most of the entries in those files were duplicates of entries in other .ent files so there seemed to be the need for a lot of manual editing to keep them all

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, On 29.02.2020 17:11, Gil Barmwater wrote: ... cut ... > The svn revision on the cover page of the rexxref is "hard coded"; i.e. a DTD > entity supplies this > value which is set in the file rexxref.ent. So a manual update of that file > is required which > doesn't always happen when

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

The previous link will now give you the corrected package. GB On 2/29/2020 11:16 AM, Gil Barmwater wrote: Indeed! My bad :-(. I will make the change and replace the package. Thanks! On 2/29/2020 10:48 AM, P.O. Jonsson wrote: Dear Gil, Ad oodguide errors Am 28.02.2020 um 19:12 schrieb Gil

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Indeed! My bad :-(. I will make the change and replace the package. Thanks! On 2/29/2020 10:48 AM, P.O. Jonsson wrote: Dear Gil, Ad oodguide errors Am 28.02.2020 um 19:12 schrieb Gil Barmwater >: Ad oodguide errors: I have added some code to create the files

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Hi Rony, First of all, thanks for the kind comments! And I really appreciate the feedback and suggestions as well. Now to the specific items in the order you listed them. The issue with the "missing folders" is one I ran into as well. It comes from the fact that I was not able to include

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, Ad oodguide errors > Am 28.02.2020 um 19:12 schrieb Gil Barmwater : > > Ad oodguide errors: I have added some code to create the files that book is > trying to include but be aware that they are in the PARENT folder of the > folder specified for docpath. This will cause a

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil: On 28.02.2020 19:12, Gil Barmwater wrote: > > I have just uploaded version 1.1 of the package to my Dropbox. In addition to > the changes I > mentioned earlier (see below), I have modified the location of the output > files. There are now > only three folders - fo_files, log_files,

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

I have just uploaded version 1.1 of the package to my Dropbox. In addition to the changes I mentioned earlier (see below), I have modified the location of the output files. There are now only three folders - fo_files, log_files, and PDF_files - instead of a folder per document. The link I

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Hi P.O. and Gil, Thank you very much for this work, this is a big step forward. best regards, René > On 28 Feb 2020, at 10:37, P.O. Jonsson wrote: > > Dear Gil, > > This is just to say that I have set up the Jenkins Win build machine to build > the docs now, I will add your changes when

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, This is just to say that I have set up the Jenkins Win build machine to build the docs now, I will add your changes when they are ready. I am currently building all documents (17 books), one could consider to split the building in two different runs for ooRexx/ooDialog. Also, since

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

 I am testing it on the Win build machine right now, will be interesting to see how long it takes  Take your time I will include all what you have done when it is finished. PS I have resurrected also the „Buildmachine“ Book. It is describing 4.3 situation but once all this is finalised it

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

P.O., I am almost ready to upload an updated version of the package which includes: the TOC with 3 levels, warning messages about the time it takes to run doc2fo, timestamps (thanks to you!) for the start and end of both doc2fo and fo2pdf, the ability to specify parameters to both FOP and

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, I did not find out how to set the index to 3 levels rather than 4, where do you change this? Personally I prefer 3 levels (as it is today) rather that with 4, where you cannot see the forest for all the threes :-) but I can live with whatever is decided. Hälsningar/Regards/Grüsse,

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, for these warnings in the oo-documents: ooRexxDocSVN/oodguide/en-US/Book_Info.xml:48: element include: XInclude error : could not load datepub.tmp, and no fallback was found ooRexxDocSVN/oodguide/en-US/Book_Info.xml:49: element include: XInclude error : could not load svnrev.tmp, and

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Hi P.O., Thanks for the kind words about the ease of use of the package. It was one of my main goals to make it so that anyone could use it, even if they were not a "power" Windows user. Per the comment re. the output folders: I chose that setup as there are three files generated for each

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

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.

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

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

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

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

Re: [Oorexx-devel] A first (successful) run on creating the rexxref.pdf documentation! (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Rony, 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