Re: [Oorexx-devel] Building the documentation for ooRexx on Jenkins

[Gilbert Barmwater]

On 2/21/2022 5:36 PM, P.O. Jonsson wrote:
Does anyone remember what this setting is for in the build step for 
the documentation?


:-- list change sets
curl %BUILD_URL%api/json

With Jenkins upgraded from http:// to https:// this seems to generate 
an error


jenkins@DELLGX760 C:\Users\jenkins\workspace\ooRexx-docs-build>curl 
https://build.oorexx.org/job/ooRexx-docs-build/102/api/json
  % Total    % Received % Xferd  Average Speed   Time    Time     Time 
 Current

                             Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- 
--:--:--     0
100   625  100   625    0     0   7052      0 --:--:-- --:--:-- 
--:--:--  7183
content='1;url=/login?from=%2Fjob%2FooRexx-docs-build%2F102%2Fapi%2Fjson'/>window.location.replace('/login?from=%2Fjob%2FooRexx-docs-build%2F102%2Fapi%2Fjson');style='background-color:white; color:white;'>



Authentication required




As a second question: I am also looking for a volunteer (nudge, nudge 
Gil) to migrate the documentation build jobs from the physical Windows 
10 machine (intended for retirement) into a VM. I have a Windows 7 PRO 
VM with a legit license I no longer use myself available for this 
task. I take it it does not matter if we build on W7 or W10?


During or after this migration it would be great if we could make the 
documentation build only when there are actual changes to the 
documentation. My rather blunt setup of Gils build tools build 
everything every time there is a commit which is mostly not related to 
the documentation. I am more than happy to replace that with something 
smarter. I will provide the necessary access information to whoever 
wants to have a go at migrating the documentation jobs.
While I am unable to take on this task, I do have some thoughts on 
making the process "smarter".  In order to only build the documents that 
have been changed, we need to know what level the previously-built 
document is and what level the source in SVN is.  I would suggest 
creating a properties file whose entries are the document names with 
values that are the revision level of each document.  Then one could get 
the current revision level of the source for the document and if it is 
different than the value in the properties file for that document, we 
need to rebuild the document AND update the properties file.  I'm 
attaching a short program that shows how to use the 'svn log' command to 
get the current revision of a document.


@René: of course you were right, BUILD_URL is a setting within Jenkins 
itself. I owe you a beer next time you are in Berlin :-)


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se





___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel/* Get the SVN revision level of a document. Expects one argument - the name of
the document specified as the directory name of the source under docs/trunk.
E.g. the Rexx Reference book is rexxref.*/

parse arg doc
-- use the svn log command to get the most recent change info for the 
document
svncmd = "svn log https://svn.code.sf.net/p/oorexx/code-0/docs/trunk/"doc 
"-l 1"
address path svncmd with output stem log.
-- the second line of the output starts with the revision number; e.g. 
r12347
parse var log.2 rev .
say "The" doc "document is at revision" rev"."
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation for ooRexx

[Gil Barmwater]

I just had a quick look at setup.rex and noted two problems.  The first 
is that the program is trying to download fop-2.4 while the current 
version is 2.6.  The second is that the "mirror" used to obtain the zip 
file is now "refusing" connections.  So I will do some debugging as time 
permits and update SF with a working setup.rex.  Thanks again for 
letting us know about this issue.


Gil

On 7/19/2021 8:49 AM, Gil Barmwater wrote:

On 7/19/2021 7:32 AM, Jean Louis Faucher wrote:
Just to share that I was able to build all the pdf/html files with 
MacPorts under MacOs High Sierra.

My version of FOP is old (v1.1) but it worked.
P.O., thank you for the very clear instructions, it was easy to follow.
It took 1 hour 10 min on my old laptop Mid 2010.

I had just to put in comment this line:
export XML_CATALOG_FILES=/usr/local/etc/xml/catalog
in doc2fo.sh and doc2html.sh
because the variable is already defined and its value is different 
for MacPorts.


I switched to Gil’s toolkit because rexxpg and rexxref no longer 
build with Publican (at least for me).
Gil, thank you for this toolkit. The section "DocBook DTD and Style 
Sheets” in sources.txt gives interesting informations.


I tested the setup under Windows.


Not having run setup in quite a while, I'll take a look at it later 
today and report back.  Thanks for the "heads up"!


Gil B.


The URL for FOP  seems not working, don’t know if it”s temporary.
I replaced it with 
https://archive.apache.org/dist/xmlgraphics/fop/binaries/ 




Jean-Louis



On 19 May 2020, at 19:56, P.O. Jonsson > wrote:


Dear developers,

I have ported Gils tools for building the documentation to macOS and 
to Ubuntu Linux.


I have followed Gil´s logics as far as I could and the names of the 
scripts are in essence the same and the way to use them as well.


For macOS I could make the build run on local files so it is just as 
fast as the Windows version. For Ubuntu I failed this so the Ubuntu 
version rely on an internet connection and is substantially slower. 
But the output for PDF and HTML is (as far as I can judge) identical 
for all three build processes. So at least this constitutes a proof 
of concept for building on all platforms.


Different from on Windows it was not possible for me to make a 
self-contained version of the build tools, neither on macOS nor on 
Linux. I have set out what tools need to be installed in a file 
WhatISHere.txt and explained how to install them + I have  briefly 
explained he build process. Since the readme for Windows is so 
complete I refer to it for the deeper understanding of the build 
process.


Further I have set up a Dropbox folder Jenkinsshare 
 where 
I have put zipped copies of the scripts. To try them out copy either 
one o*f oorexxdocs-macOS.zip* or *oorexxdocs-Ubuntu.zip* to a local 
folder, unzip and follow the instructions in *WhatIsHere.txt*. 
Feedback is welcome.


Jenkinsshare 
 also 
contains 3 complete sets of the documentation (Win/macOS/Ubuntu 
Linux), please have a look and let us know what you think.


Jenkinsshare is intended as a platform for sharing files during 
development. Gil, myself and Rony use it for sharing work on the 
documentation. JenkinsShare is owned by Jenkins and present on the 
master and my Jenkins slaves. Any developer who wants permanent 
access can send me a mail and I will set it up. It is NOT a 
replacement for SVN/Sourceforge, just a quick way of sharing data. 
Since the folder is shared by many I ask you to be moderate when 
putting data there.


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 



___
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



___
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

Re: [Oorexx-devel] Building the Documentation for ooRexx

[Gil Barmwater]

On 7/19/2021 7:32 AM, Jean Louis Faucher wrote:
Just to share that I was able to build all the pdf/html files with 
MacPorts under MacOs High Sierra.

My version of FOP is old (v1.1) but it worked.
P.O., thank you for the very clear instructions, it was easy to follow.
It took 1 hour 10 min on my old laptop Mid 2010.

I had just to put in comment this line:
export XML_CATALOG_FILES=/usr/local/etc/xml/catalog
in doc2fo.sh and doc2html.sh
because the variable is already defined and its value is different for 
MacPorts.


I switched to Gil’s toolkit because rexxpg and rexxref no longer build 
with Publican (at least for me).
Gil, thank you for this toolkit. The section "DocBook DTD and Style 
Sheets” in sources.txt gives interesting informations.


I tested the setup under Windows.


Not having run setup in quite a while, I'll take a look at it later 
today and report back.  Thanks for the "heads up"!


Gil B.


The URL for FOP  seems not working, don’t know if it”s temporary.
I replaced it with 
https://archive.apache.org/dist/xmlgraphics/fop/binaries/ 




Jean-Louis



On 19 May 2020, at 19:56, P.O. Jonsson > wrote:


Dear developers,

I have ported Gils tools for building the documentation to macOS and 
to Ubuntu Linux.


I have followed Gil´s logics as far as I could and the names of the 
scripts are in essence the same and the way to use them as well.


For macOS I could make the build run on local files so it is just as 
fast as the Windows version. For Ubuntu I failed this so the Ubuntu 
version rely on an internet connection and is substantially slower. 
But the output for PDF and HTML is (as far as I can judge) identical 
for all three build processes. So at least this constitutes a proof 
of concept for building on all platforms.


Different from on Windows it was not possible for me to make a 
self-contained version of the build tools, neither on macOS nor on 
Linux. I have set out what tools need to be installed in a file 
WhatISHere.txt and explained how to install them + I have  briefly 
explained he build process. Since the readme for Windows is so 
complete I refer to it for the deeper understanding of the build process.


Further I have set up a Dropbox folder Jenkinsshare 
 where 
I have put zipped copies of the scripts. To try them out copy either 
one o*f oorexxdocs-macOS.zip* or *oorexxdocs-Ubuntu.zip* to a local 
folder, unzip and follow the instructions in *WhatIsHere.txt*. 
Feedback is welcome.


Jenkinsshare 
 also 
contains 3 complete sets of the documentation (Win/macOS/Ubuntu 
Linux), please have a look and let us know what you think.


Jenkinsshare is intended as a platform for sharing files during 
development. Gil, myself and Rony use it for sharing work on the 
documentation. JenkinsShare is owned by Jenkins and present on the 
master and my Jenkins slaves. Any developer who wants permanent 
access can send me a mail and I will set it up. It is NOT a 
replacement for SVN/Sourceforge, just a quick way of sharing data. 
Since the folder is shared by many I ask you to be moderate when 
putting data there.


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 



___
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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation for ooRexx

[Jean Louis Faucher]

Just to share that I was able to build all the pdf/html files with MacPorts 
under MacOs High Sierra.
My version of FOP is old (v1.1) but it worked.
P.O., thank you for the very clear instructions, it was easy to follow.
It took 1 hour 10 min on my old laptop Mid 2010.

I had just to put in comment this line:
export XML_CATALOG_FILES=/usr/local/etc/xml/catalog
in doc2fo.sh and doc2html.sh
because the variable is already defined and its value is different for MacPorts.

I switched to Gil’s toolkit because rexxpg and rexxref no longer build with 
Publican (at least for me).
Gil, thank you for this toolkit. The section "DocBook DTD and Style Sheets” in 
sources.txt gives interesting informations.

I tested the setup under Windows.
The URL for FOP  seems not working, don’t know if it”s temporary.
I replaced it with https://archive.apache.org/dist/xmlgraphics/fop/binaries/


Jean-Louis



> On 19 May 2020, at 19:56, P.O. Jonsson  wrote:
> 
> Dear developers,
> 
> I have ported Gils tools for building the documentation to macOS and to 
> Ubuntu Linux.
> 
> I have followed Gil´s logics as far as I could and the names of the scripts 
> are in essence the same and the way to use them as well.
> 
> For macOS I could make the build run on local files so it is just as fast as 
> the Windows version. For Ubuntu I failed this so the Ubuntu version rely on 
> an internet connection and is substantially slower. But the output for PDF 
> and HTML is (as far as I can judge) identical for all three build processes. 
> So at least this constitutes a proof of concept for building on all platforms.
> 
> Different from on Windows it was not possible for me to make a self-contained 
> version of the build tools, neither on macOS nor on Linux. I have set out 
> what tools need to be installed in a file WhatISHere.txt and explained how to 
> install them + I have  briefly explained he build process. Since the readme 
> for Windows is so complete I refer to it for the deeper understanding of the 
> build process.
> 
> Further I have set up a Dropbox folder Jenkinsshare 
>  
> where I have put zipped copies of the scripts. To try them out copy either 
> one of oorexxdocs-macOS.zip or oorexxdocs-Ubuntu.zip to a local folder, unzip 
> and follow the instructions in WhatIsHere.txt. Feedback is welcome.
> 
> Jenkinsshare 
>  
> also contains 3 complete sets of the documentation (Win/macOS/Ubuntu Linux), 
> please have a look and let us know what you think.
> 
> Jenkinsshare is intended as a platform for sharing files during development. 
> Gil, myself and Rony use it for sharing work on the documentation. 
> JenkinsShare is owned by Jenkins and present on the master and my Jenkins 
> slaves. Any developer who wants permanent access can send me a mail and I 
> will set it up. It is NOT a replacement for SVN/Sourceforge, just a quick way 
> of sharing data. Since the folder is shared by many I ask you to be moderate 
> when putting data there.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

Re: [Oorexx-devel] Building the Documentation

[Gil Barmwater]

Having given this some more thought, I now propose to 1) place the 
"non-external" portions of the package in SVN as I originally proposed 
and 2) place a copy of each of the zip files, the files that are 
actually downloaded from the Internet by the Setup program, in an 
appropriate place in the Files section of the SourceForge ooRexx site. 
This addresses the concern of having a "backup" copy of the external 
tools while not having two copies of the other files that would require 
synchronization.


Gil

On 4/16/2020 3:58 PM, Jeremy Nicoll wrote:

On Thu, 16 Apr 2020, at 18:59, Gil Barmwater wrote:

  I do not believe by any means that this is the
"last" version of these tools. For example, we should look at moving to
DocBook 5 and that will surely involve changes. We might want to
explore using a different tool to do the transform, one that might
support syntax highlighting of our code examples.

I'm not against that in any way.  What I am suggesting is that whatever
is the toolset du jour, there should be a complete copy of that stored
by this project, not dependent on external repositories.


--
Gil Barmwater



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation

[Gil Barmwater]

OK, thanks Rick, will do.

Gil

On 4/16/2020 2:57 PM, Rick McGuire wrote:

For all new stuff leave off the IBM line.


On Thu, Apr 16, 2020 at 2:44 PM Gil Barmwater > wrote:


On 4/16/2020 11:45 AM, Rick McGuire wrote:

Yes, any text files probably should have a copyright, if
practical. Just grab the text from any file that includes one.

-- 


So I notice that many/most of the ones I've looked at start with:

/* Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. */

Since this is all new code, is this line necessary? Or should I
start with the next line:

/* Copyright (c) 2020 Rexx Language Association. All rights
reserved. */

(Just want to get it right :-) .)


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


--
Gil Barmwater

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation

[Jeremy Nicoll]

On Thu, 16 Apr 2020, at 18:59, Gil Barmwater wrote:
>  I do not believe by any means that this is the 
> "last" version of these tools. For example, we should look at moving to 
> DocBook 5 and that will surely involve changes. We might want to 
> explore using a different tool to do the transform, one that might 
> support syntax highlighting of our code examples. 

I'm not against that in any way.  What I am suggesting is that whatever
is the toolset du jour, there should be a complete copy of that stored
by this project, not dependent on external repositories.

-- 
Jeremy Nicoll - my opinions are my own.


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation

[Rick McGuire]

For all new stuff leave off the IBM line.


On Thu, Apr 16, 2020 at 2:44 PM Gil Barmwater 
wrote:

> On 4/16/2020 11:45 AM, Rick McGuire wrote:
>
> Yes, any text files probably should have a copyright, if practical. Just
> grab the text from any file that includes one.
>
>> --
>
> So I notice that many/most of the ones I've looked at start with:
>
> /* Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. 
> */
>
> Since this is all new code, is this line necessary? Or should I start with
> the next line:
>
> /* Copyright (c) 2020 Rexx Language Association. All rights reserved. 
> */
>
> (Just want to get it right :-) .)
>
>
> --
> 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

Re: [Oorexx-devel] Building the Documentation

[Gil Barmwater]

On 4/16/2020 11:45 AM, Rick McGuire wrote:
Yes, any text files probably should have a copyright, if practical. 
Just grab the text from any file that includes one.


-- 


So I notice that many/most of the ones I've looked at start with:

/* Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. */

Since this is all new code, is this line necessary? Or should I start 
with the next line:


/* Copyright (c) 2020 Rexx Language Association. All rights reserved. */

(Just want to get it right :-) .)

--
Gil Barmwater

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation

[Gil Barmwater]

The reason for putting the package, at least the non-binary files, on 
SVN is to make them officially part of the ooRexx project. That way, 
anyone can modify them when the need arises (at least anyone with 
committer status). I do not believe by any means that this is the "last" 
version of these tools. For example, we should look at moving to DocBook 
5 and that will surely involve changes. We might want to explore using a 
different tool to do the transform, one that might support syntax 
highlighting of our code examples. We certainly should create a version 
of the package that runs on *ix so anyone not on Windows can also build 
the documentation. And I am sure there are others as well.


I am happy to also put the "complete" package up as well, presumably in 
the Files section where the Publican-related tools are stored, but I 
will need some direction on how to do so.


Gil

On 4/16/2020 1:28 PM, P.O. Jonsson wrote:
I agree with Jeremy, I spent a LOT of time trying to resurrect 
Publican and would not have succeeded unless Erich had saved some of 
the necessary items on Sourceforge. I am in favor of saving a complete 
standalone package.


I don´t see a point with using SVN to get the tools. If there is a 
„Tools“ repository that one can use http to get to this is easier for 
most user?


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 



Am 16.04.2020 um 18:58 schrieb Jeremy Nicoll 
mailto:jn.ml.sfrg...@letterboxes.org>>:


On Thu, 16 Apr 2020, at 15:08, Gil Barmwater wrote:


The problem that arises is
that the complete package contains binary files which are not normally
kept in SVN. So I can either upload the entire package anyway or just
upload the parts that are not obtained from the Internet and write
detailed instructions on what and how to obtain the other portions. The
first has the advantage that the package is immediately usable once it
is checked out while the second is much "cleaner" but requires the user
to do additional "installation" work before it can be used.


If there's not at least a reference copy of the binaries then in a 
few years
time, when the external tools change, it might impossible for other 
people

to repeat the current process.

If on the other hand the current binaries are also stored, they 
should be

runnable in future if necessary (even if that has to be done in a virtual
machine running some ancient OS like Windows 10).

--
Jeremy Nicoll - my opinions are my own.


___
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


--
Gil Barmwater

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation

[P.O. Jonsson]

I agree with Jeremy, I spent a LOT of time trying to resurrect Publican and 
would not have succeeded unless Erich had saved some of the necessary items on 
Sourceforge. I am in favor of saving a complete standalone package.

I don´t see a point with using SVN to get the tools. If there is a „Tools“ 
repository that one can use http to get to this is easier for most user?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 16.04.2020 um 18:58 schrieb Jeremy Nicoll :
> 
> On Thu, 16 Apr 2020, at 15:08, Gil Barmwater wrote:
> 
>> The problem that arises is 
>> that the complete package contains binary files which are not normally 
>> kept in SVN. So I can either upload the entire package anyway or just 
>> upload the parts that are not obtained from the Internet and write 
>> detailed instructions on what and how to obtain the other portions. The 
>> first has the advantage that the package is immediately usable once it 
>> is checked out while the second is much "cleaner" but requires the user 
>> to do additional "installation" work before it can be used. 
> 
> If there's not at least a reference copy of the binaries then in a few years
> time, when the external tools change, it might impossible for other people
> to repeat the current process.
> 
> If on the other hand the current binaries are also stored, they should be 
> runnable in future if necessary (even if that has to be done in a virtual
> machine running some ancient OS like Windows 10).
> 
> -- 
> Jeremy Nicoll - my opinions are my own.
> 
> 
> ___
> 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

Re: [Oorexx-devel] Building the Documentation

[Jeremy Nicoll]

On Thu, 16 Apr 2020, at 15:08, Gil Barmwater wrote:

> The problem that arises is 
> that the complete package contains binary files which are not normally 
> kept in SVN. So I can either upload the entire package anyway or just 
> upload the parts that are not obtained from the Internet and write 
> detailed instructions on what and how to obtain the other portions. The 
> first has the advantage that the package is immediately usable once it 
> is checked out while the second is much "cleaner" but requires the user 
> to do additional "installation" work before it can be used. 

If there's not at least a reference copy of the binaries then in a few years
time, when the external tools change, it might impossible for other people
to repeat the current process.

If on the other hand the current binaries are also stored, they should be 
runnable in future if necessary (even if that has to be done in a virtual
machine running some ancient OS like Windows 10).

-- 
Jeremy Nicoll - my opinions are my own.


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the Documentation

[Rick McGuire]

On Thu, Apr 16, 2020 at 10:30 AM Gil Barmwater 
wrote:

> Although it seems that work on this has stopped, I have actually been
> still working on it! The functionality of the package seems stable so I
> have been thinking about how best to make it available in a more
> "official" way than through my DropBox. We now have a folder named tools
> in the docs portion of the SVN repository thanks to Rony so that seems
> to be the logical place to put the package. The problem that arises is
> that the complete package contains binary files which are not normally
> kept in SVN.


Binary files in SVN are not really an issue. We have lots of binaries
already in the tree, such as images, icons, etc. The other option would be
to upload the package to the project Files section such as has been done
with the NSIS package used to build the Windows installer. My personal
preference would be SVN.


> So I can either upload the entire package anyway or just
> upload the parts that are not obtained from the Internet and write
> detailed instructions on what and how to obtain the other portions. The
> first has the advantage that the package is immediately usable once it
> is checked out while the second is much "cleaner" but requires the user
> to do additional "installation" work before it can be used. I did not
> like either choice so I have written an ooRexx program named Setup that
> does that "installation" work automatically. It downloads all seven
> packages, unzips them into the correct locations and, in the case of the
> xsltproc packages, copies the executable files into the main folder. The
> Setup program should only have to be run once after the package is
> checked out if the user's internet connection is stable - mine has not
> been lately - but can be safely rerun if it does not run to successful
> completion.
>
> So my intention now is to check-in the portions of the package without
> the "external" tools but with the Setup program. These consist of one
> .cfg file, six .cmd files, three .rex programs, two .txt files, and four
> .xsl stylesheets. Before I do so I need some guidance on including the
> "boilerplate" regarding license and copyright information. Clearly, the
> ooRexx programs need it but what about the other file types? And should
> I just take the text from one of the "samples" files or something else?
>

Yes, any text files probably should have a copyright, if practical. Just
grab the text from any file that includes one.

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

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

Hi Gil,

No objections whatsoever, I just wonder if this is the same cause as found 
while trying (failing :-( ) to find the cause earlier:

Hi Chris,
The role value 'italic' is not actually a recognized value in the 
stylesheets.  Rather, italic font-style is the default output for emphasis. 
In FO, if role is not 'strong' or 'bold', you automatically get the default 
italic.

-> Try changing  to 


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 01.04.2020 um 17:21 schrieb Gil Barmwater :
> 
> This inspired me to do some digging into the problem now that Rony has 
> determined the cause. It appears that the  tag confuses the 
> stlyesheet which would have otherwise picked up the text. However, there are 
> other ways to specify the text, one of which is to include an "xreflable" 
> attribute. I have tried that and it allows one to keep the "emphasis" without 
> generating the error messages. I plan to make the changes shortly so the 
> original look will be preserved and the ??? will be eliminated. Any 
> objections?
> 
> Gil
> On 3/31/2020 4:48 PM, Gil Barmwater wrote:
>> Well done! I never would have thought to try that since the documentation 
>> would lead one to believe it was legal. Thanks Rony!
>> 
>> Gil
>> On 3/31/2020 2:52 PM, Rony G. Flatscher wrote:
>>> Found the cause: there are term elements which have their text embedded in 
>>> emphasis tags causing the error messages:
>>> 
>>> Don't know what gentext to create for xref to: "emphasis"
>>> Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd 
>>> successfully, therefore committed with [r12032].
>>> 
>>> ---rony
>>> 
>>> On 31.03.2020 17:41, Gil Barmwater wrote:
 There appears to be two issues based on the messages generated by the 
 transform step. The first - Warning: multiple "IDs" for constraint 
 linkend: - occurs 7 times for 3 different values: clsWindowObject, 
 childatpositionwo, and windowatpositionwm. These might be simple typos(?).
 
 The second - Don't know what gentext to create for xref to: "emphasis" - 
 occurs 32 times and seems to correspond with the ??? that appears 32 times 
 in the PDF generated by Publican. Finding the XML for that area seems to 
 show a "linkend=" but the value does not get substituted.
 
 The second issue seems to be confined to the WindowsEventLogClass chapter.
 
 That's as far as I have gotten. Hope it is enough to determine the fix 
 needed.
 
 Gil
 On 3/31/2020 11:20 AM, Rick McGuire wrote:
> 
> 
> On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater  > wrote:
> Well, as I mentioned, this was a problem with the PDF builds as well. So 
> I looked in the PDF.xsl for where the "No adjustColumnWidths function 
> available" message was generated and found that there was a parameter - 
> tablecolumns.extension - that controlled that function. Since we don't 
> use Perl and don't have the Perl function anyway, I decided to try 
> disabling the function by changing the parameter expecting this would 
> cause other side effects. Luckily, it didn't. So when this surfaced in 
> the HTML generation, I found the same parameter in the xhtml-common.xsl 
> file and changed it there too.
> 
> The problems with winextensions are not not related but are due to "bad" 
> Docbook code. I know where they are coming from but need to understand 
> what the author was attempting to do and then determine how to do it 
> "right".
> 
> Please explain what the issue it so we can help to decide now to fix it. 
> 
> Rick
> 
>  
> Gil
> On 3/31/2020 10:26 AM, P.O. Jonsson wrote:
>> Ok, missed that part :-(
>> 
>> I have replaced xhtml-common.xsl now and winextensions build as it 
>> should, so this was probably the problem. This tiniest change cased the 
>> problem thus:
>> 
>> 1
>> 
>> changed into
>> 
>> 0 > Gil Barmwater
>> 
>> 
>> 
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

This inspired me to do some digging into the problem now that Rony has 
determined the cause. It appears that the  tag confuses the 
stlyesheet which would have otherwise picked up the text. However, there 
are other ways to specify the text, one of which is to include an 
"xreflable" attribute. I have tried that and it allows one to keep the 
"emphasis" without generating the error messages. I plan to make the 
changes shortly so the original look will be preserved and the ??? will 
be eliminated. Any objections?


Gil

On 3/31/2020 4:48 PM, Gil Barmwater wrote:


Well done! I never would have thought to try that since the 
documentation would lead one to believe it was legal. Thanks Rony!


Gil

On 3/31/2020 2:52 PM, Rony G. Flatscher wrote:


Found the cause: there are term elements which have their text 
embedded in emphasis tags causing the error messages:


Don't know what gentext to create for xref to: "emphasis"

Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd 
successfully, therefore committed with [r12032].


---rony


On 31.03.2020 17:41, Gil Barmwater wrote:


There appears to be two issues based on the messages generated by 
the transform step. The first - Warning: multiple "IDs" for 
constraint linkend: - occurs 7 times for 3 different values: 
clsWindowObject, childatpositionwo, and windowatpositionwm. These 
might be simple typos(?).


The second - Don't know what gentext to create for xref to: 
"emphasis" - occurs 32 times and seems to correspond with the ??? 
that appears 32 times in the PDF generated by Publican. Finding the 
XML for that area seems to show a "linkend=" but the value does not 
get substituted.


The second issue seems to be confined to the WindowsEventLogClass 
chapter.


That's as far as I have gotten. Hope it is enough to determine the 
fix needed.


Gil

On 3/31/2020 11:20 AM, Rick McGuire wrote:



On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater 
mailto:gbarmwa...@alum.rpi.edu>> wrote:


Well, as I mentioned, this was a problem with the PDF builds as
well. So I looked in the PDF.xsl for where the "No
adjustColumnWidths function available" message was generated
and found that there was a parameter - tablecolumns.extension -
that controlled that function. Since we don't use Perl and
don't have the Perl function anyway, I decided to try disabling
the function by changing the parameter expecting this would
cause other side effects. Luckily, it didn't. So when this
surfaced in the HTML generation, I found the same parameter in
the xhtml-common.xsl file and changed it there too.

The problems with winextensions are not not related but are due
to "bad" Docbook code. I know where they are coming from but
need to understand what the author was attempting to do and
then determine how to do it "right".

Please explain what the issue it so we can help to decide now to 
fix it.


Rick

Gil

On 3/31/2020 10:26 AM, P.O. Jonsson wrote:

Ok, missed that part :-(

I have replaced xhtml-common.xsl now and winextensions build
as it should, so this was probably the problem. This tiniest
change cased the problem thus:

1

changed into

0 

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

Dear Rony,


> Am 31.03.2020 um 21:55 schrieb Rony G Flatscher :
> 
> Hi P.O.,
> 
> ad rexxpg: I do not get any of these warnings.

You are probably right, I am seeing sign of exhaustion from executing the build 
repetitively (on a machine that is not rebooted to often). This is worrying and 
I have not seen it when building only PDFs. I will do an exhaustion test to see 
if I can find out why it happens.

> 
> Ad logfiles: think not all logged text is correct, sometimes misleading as in 
> the winextensions case.

Ok, I just wanted to mention it. 

> 
> Cheers
> 


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

Well done! I never would have thought to try that since the 
documentation would lead one to believe it was legal. Thanks Rony!


Gil

On 3/31/2020 2:52 PM, Rony G. Flatscher wrote:


Found the cause: there are term elements which have their text 
embedded in emphasis tags causing the error messages:


Don't know what gentext to create for xref to: "emphasis"

Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd 
successfully, therefore committed with [r12032].


---rony


On 31.03.2020 17:41, Gil Barmwater wrote:


There appears to be two issues based on the messages generated by the 
transform step. The first - Warning: multiple "IDs" for constraint 
linkend: - occurs 7 times for 3 different values: clsWindowObject, 
childatpositionwo, and windowatpositionwm. These might be simple 
typos(?).


The second - Don't know what gentext to create for xref to: 
"emphasis" - occurs 32 times and seems to correspond with the ??? 
that appears 32 times in the PDF generated by Publican. Finding the 
XML for that area seems to show a "linkend=" but the value does not 
get substituted.


The second issue seems to be confined to the WindowsEventLogClass 
chapter.


That's as far as I have gotten. Hope it is enough to determine the 
fix needed.


Gil

On 3/31/2020 11:20 AM, Rick McGuire wrote:



On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater 
mailto:gbarmwa...@alum.rpi.edu>> wrote:


Well, as I mentioned, this was a problem with the PDF builds as
well. So I looked in the PDF.xsl for where the "No
adjustColumnWidths function available" message was generated and
found that there was a parameter - tablecolumns.extension - that
controlled that function. Since we don't use Perl and don't have
the Perl function anyway, I decided to try disabling the
function by changing the parameter expecting this would cause
other side effects. Luckily, it didn't. So when this surfaced in
the HTML generation, I found the same parameter in the
xhtml-common.xsl file and changed it there too.

The problems with winextensions are not not related but are due
to "bad" Docbook code. I know where they are coming from but
need to understand what the author was attempting to do and then
determine how to do it "right".

Please explain what the issue it so we can help to decide now to fix 
it.


Rick

Gil

On 3/31/2020 10:26 AM, P.O. Jonsson wrote:

Ok, missed that part :-(

I have replaced xhtml-common.xsl now and winextensions build as
it should, so this was probably the problem. This tiniest
change cased the problem thus:

1

changed into

0 

Re: [Oorexx-devel] Building the documentation

[Rony G Flatscher]

Hi P.O.,

ad rexxpg: I do not get any of these warnings.

Ad logfiles: think not all logged text is correct, sometimes misleading as in 
the winextensions case.

Cheers

—-rony

Rony G. Flatscher (mobil/e)

> Am 31.03.2020 um 21:39 schrieb P.O. Jonsson :
> 
> I have built winextensions.pdf and indeed where it used to be
> 
> Note that if there is an open (???) , the server argument is ignored.
> 
> There is now
> 
> Note that if there is an open (Opened event log) , the server argument is 
> ignored.
> 
> Or similar. Great.
> 
> I have number of further items, the first one is in rexxpg.xml so for you 
> Rony:
> 
> Starting to build fo file for rexxpg: 17:54:10.53
> 17:54:10 - Transforming ooRexxDocSVN\rexxpg\en-US\rexxpg.xml into 
> HTML_folders\rexxpg\
> This may take up to 10+ minutes for the largest documents!
> http://www.oasis-open.org/docbook/xml/4.5/dbcentx.mod:373: parser error : 
> Entity value required
> ]]>
> ^
> http://www.oasis-open.org/docbook/xml/4.5/dbcentx.mod:373: parser error : 
> Space required before 'NDATA'
> ]]>
> ^
> http://www.oasis-open.org/docbook/xml/4.5/dbcentx.mod:373: parser error : 
> xmlParseEntityDecl: entity num not terminated
> ]]>
> ^
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:132: parser warning : 
> PEReference: %dbpool.module; not found
> ^
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:132: parser error : 
> conditional section INCLUDE or IGNORE keyword expected
>  ^
> http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:132: parser error : 
> Content error in the external subset
>   ^
> ooRexxDocSVN/rexxpg/en-US/rexxpg.xml:47: element include: XInclude error : 
> could not load ooRexxDocSVN/rexxpg/en-US/Book_Info.xml, and no fallback was 
> found
> Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in 
> book, but no template matches.
> 18:07:44 - 201 HTML files were created
> Build finished for rexxpg: 18:07:44.36
> 
> Then these warnings (or similar) arise in the end of several books (have not 
> checked all yet) si I guess in a part common to all books (I think Gil 
> already mentioned these):
> 
> WARNING: Destination: Unresolved ID reference "book-oorexx-ooconsole" found.
> WARNING: Destination: Unresolved ID reference "notices.title" found.
> WARNING: Destination: Unresolved ID reference "cplv10.title" found.
> 
> In oodguide I found these on page 106 and 107 (while executing doc2html), I 
> guess there are typos
> 
> oodguide.log
> INFO: Rendered page #105.
> WARNING: Destination: Unresolved ID reference "book-oorexx-oodguide" found.
> WARNING: Destination: Unresolved ID reference "reduce-cplg" found.
> WARNING: Destination: Unresolved ID reference "chap05-dlgcontrols" found.
> WARNING: Destination: Unresolved ID reference "defimage.title" found.
> WARNING: Destination: Unresolved ID reference "chap05-dlgdesign" found.
> WARNING: Destination: Unresolved ID reference "chap05-cancel.title" found.
> WARNING: Destination: Unresolved ID reference "progstruc.title" found.
> WARNING: Destination: Unresolved ID reference "popups.title" found.
> WARNING: Destination: Unresolved ID reference "offsetting.title" found.
> WARNING: Destination: Unresolved ID reference "interpret.title" found.
> WARNING: Destination: Unresolved ID reference "lviews.title" found.
> WARNING: Destination: Unresolved ID reference "resize.title" found.
> WARNING: Destination: Unresolved ID reference "icons.title" found.
> WARNING: Destination: Unresolved ID reference "utildlgs.title" found.
> WARNING: Destination: Unresolved ID reference "ch7-mvf.title" found.
> WARNING: Destination: Unresolved ID reference "ch7-mvf-obj.title" found.
> WARNING: Destination: Unresolved ID reference "ch7-mvf-oview.title" found.
> WARNING: Destination: Unresolved ID reference "ch7-mvf-oview-person.title" 
> found.
> WARNING: Destination: Unresolved ID reference "ch7-mvf-classes.title" found.
> WARNING: Destination: Unresolved ID reference "ch7-mvf-classeso-objmgr.title" 
> found.
> WARNING: Destination: Unresolved ID reference "ch7-cmpntdata.title" found.
> WARNING: Destination: Unresolved ID reference "ch7-cmpntdata-kinds.title" 
> found.
> WARNING: Destination: Unresolved ID reference "ch7-cmpntdata-data.title" 
> found.
> WARNING: 

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

I have built winextensions.pdf and indeed where it used to be

Note that if there is an open (???) , the server argument is ignored.

There is now

Note that if there is an open (Opened event log) , the server argument is 
ignored.

Or similar. Great.

I have number of further items, the first one is in rexxpg.xml so for you Rony:

Starting to build fo file for rexxpg: 17:54:10.53
17:54:10 - Transforming ooRexxDocSVN\rexxpg\en-US\rexxpg.xml into 
HTML_folders\rexxpg\
This may take up to 10+ minutes for the largest documents!
http://www.oasis-open.org/docbook/xml/4.5/dbcentx.mod:373: parser error : 
Entity value required
]]>
^
http://www.oasis-open.org/docbook/xml/4.5/dbcentx.mod:373: parser error : Space 
required before 'NDATA'
]]>
^
http://www.oasis-open.org/docbook/xml/4.5/dbcentx.mod:373: parser error : 
xmlParseEntityDecl: entity num not terminated
]]>
^
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:132: parser warning : 
PEReference: %dbpool.module; not found
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:132: parser error : 
conditional section INCLUDE or IGNORE keyword expected
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:132: parser error : 
Content error in the external subset
http://www.w3.org/2001/XInclude' encountered in 
book, but no template matches.
18:07:44 - 201 HTML files were created
Build finished for rexxpg: 18:07:44.36

Then these warnings (or similar) arise in the end of several books (have not 
checked all yet) si I guess in a part common to all books (I think Gil already 
mentioned these):

WARNING: Destination: Unresolved ID reference "book-oorexx-ooconsole" found.
WARNING: Destination: Unresolved ID reference "notices.title" found.
WARNING: Destination: Unresolved ID reference "cplv10.title" found.

In oodguide I found these on page 106 and 107 (while executing doc2html), I 
guess there are typos

oodguide.log
INFO: Rendered page #105.
WARNING: Destination: Unresolved ID reference "book-oorexx-oodguide" found.
WARNING: Destination: Unresolved ID reference "reduce-cplg" found.
WARNING: Destination: Unresolved ID reference "chap05-dlgcontrols" found.
WARNING: Destination: Unresolved ID reference "defimage.title" found.
WARNING: Destination: Unresolved ID reference "chap05-dlgdesign" found.
WARNING: Destination: Unresolved ID reference "chap05-cancel.title" found.
WARNING: Destination: Unresolved ID reference "progstruc.title" found.
WARNING: Destination: Unresolved ID reference "popups.title" found.
WARNING: Destination: Unresolved ID reference "offsetting.title" found.
WARNING: Destination: Unresolved ID reference "interpret.title" found.
WARNING: Destination: Unresolved ID reference "lviews.title" found.
WARNING: Destination: Unresolved ID reference "resize.title" found.
WARNING: Destination: Unresolved ID reference "icons.title" found.
WARNING: Destination: Unresolved ID reference "utildlgs.title" found.
WARNING: Destination: Unresolved ID reference "ch7-mvf.title" found.
WARNING: Destination: Unresolved ID reference "ch7-mvf-obj.title" found.
WARNING: Destination: Unresolved ID reference "ch7-mvf-oview.title" found.
WARNING: Destination: Unresolved ID reference "ch7-mvf-oview-person.title" 
found.
WARNING: Destination: Unresolved ID reference "ch7-mvf-classes.title" found.
WARNING: Destination: Unresolved ID reference "ch7-mvf-classeso-objmgr.title" 
found.
WARNING: Destination: Unresolved ID reference "ch7-cmpntdata.title" found.
WARNING: Destination: Unresolved ID reference "ch7-cmpntdata-kinds.title" found.
WARNING: Destination: Unresolved ID reference "ch7-cmpntdata-data.title" found.
WARNING: Destination: Unresolved ID reference 
"cmpntdata-cmpntdata-compdata.title" found.
WARNING: Destination: Unresolved ID reference "ch7-msgsender.title" found.
WARNING: Destination: Unresolved ID reference "ch7-ordermgr.title" found.
WARNING: Destination: Unresolved ID reference "ch7-orderform.title" found.
WARNING: Destination: Unresolved ID reference "ch7-next" found.
WARNING: Destination: Unresolved ID reference "dlgdata.title" found.
WARNING: Destination: 

Re: [Oorexx-devel] Building the documentation

[Rony G. Flatscher]

Found the cause: there are term elements which have their text embedded in 
emphasis tags causing the
error messages:

Don't know what gentext to create for xref to: "emphasis"

Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd successfully, 
therefore committed
with [r12032].

---rony


On 31.03.2020 17:41, Gil Barmwater wrote:
>
> There appears to be two issues based on the messages generated by the 
> transform step. The first -
> Warning: multiple "IDs" for constraint linkend: - occurs 7 times for 3 
> different values:
> clsWindowObject, childatpositionwo, and windowatpositionwm. These might be 
> simple typos(?).
>
> The second - Don't know what gentext to create for xref to: "emphasis" - 
> occurs 32 times and seems
> to correspond with the ??? that appears 32 times in the PDF generated by 
> Publican. Finding the XML
> for that area seems to show a "linkend=" but the value does not get 
> substituted.
>
> The second issue seems to be confined to the WindowsEventLogClass chapter.
>
> That's as far as I have gotten. Hope it is enough to determine the fix needed.
>
> Gil
>
> On 3/31/2020 11:20 AM, Rick McGuire wrote:
>>
>>
>> On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater > > wrote:
>>
>> Well, as I mentioned, this was a problem with the PDF builds as well. So 
>> I looked in the
>> PDF.xsl for where the "No adjustColumnWidths function available" message 
>> was generated and
>> found that there was a parameter - tablecolumns.extension - that 
>> controlled that function.
>> Since we don't use Perl and don't have the Perl function anyway, I 
>> decided to try disabling
>> the function by changing the parameter expecting this would cause other 
>> side effects.
>> Luckily, it didn't. So when this surfaced in the HTML generation, I 
>> found the same parameter
>> in the xhtml-common.xsl file and changed it there too.
>>
>> The problems with winextensions are not not related but are due to "bad" 
>> Docbook code. I know
>> where they are coming from but need to understand what the author was 
>> attempting to do and
>> then determine how to do it "right".
>>
>> Please explain what the issue it so we can help to decide now to fix it. 
>>
>> Rick
>>
>>  
>>
>> Gil
>>
>> On 3/31/2020 10:26 AM, P.O. Jonsson wrote:
>>> Ok, missed that part :-(
>>>
>>> I have replaced xhtml-common.xsl now and winextensions build as it 
>>> should, so this was
>>> probably the problem. This tiniest change cased the problem thus:
>>>
>>> 1
>>>
>>> changed into
>>>
>>> 0 

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

There appears to be two issues based on the messages generated by the 
transform step. The first - Warning: multiple "IDs" for constraint 
linkend: - occurs 7 times for 3 different values: clsWindowObject, 
childatpositionwo, and windowatpositionwm. These might be simple typos(?).


The second - Don't know what gentext to create for xref to: "emphasis" - 
occurs 32 times and seems to correspond with the ??? that appears 32 
times in the PDF generated by Publican. Finding the XML for that area 
seems to show a "linkend=" but the value does not get substituted.


The second issue seems to be confined to the WindowsEventLogClass chapter.

That's as far as I have gotten. Hope it is enough to determine the fix 
needed.


Gil

On 3/31/2020 11:20 AM, Rick McGuire wrote:



On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater 
mailto:gbarmwa...@alum.rpi.edu>> wrote:


Well, as I mentioned, this was a problem with the PDF builds as
well. So I looked in the PDF.xsl for where the "No
adjustColumnWidths function available" message was generated and
found that there was a parameter - tablecolumns.extension - that
controlled that function. Since we don't use Perl and don't have
the Perl function anyway, I decided to try disabling the function
by changing the parameter expecting this would cause other side
effects. Luckily, it didn't. So when this surfaced in the HTML
generation, I found the same parameter in the xhtml-common.xsl
file and changed it there too.

The problems with winextensions are not not related but are due to
"bad" Docbook code. I know where they are coming from but need to
understand what the author was attempting to do and then determine
how to do it "right".

Please explain what the issue it so we can help to decide now to fix it.

Rick

Gil

On 3/31/2020 10:26 AM, P.O. Jonsson wrote:

Ok, missed that part :-(

I have replaced xhtml-common.xsl now and winextensions build as
it should, so this was probably the problem. This tiniest change
cased the problem thus:

1

changed into

0 

Re: [Oorexx-devel] Building the documentation

[Rick McGuire]

On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater 
wrote:

> Well, as I mentioned, this was a problem with the PDF builds as well. So I
> looked in the PDF.xsl for where the "No adjustColumnWidths function
> available" message was generated and found that there was a parameter -
> tablecolumns.extension - that controlled that function. Since we don't use
> Perl and don't have the Perl function anyway, I decided to try disabling
> the function by changing the parameter expecting this would cause other
> side effects. Luckily, it didn't. So when this surfaced in the HTML
> generation, I found the same parameter in the xhtml-common.xsl file and
> changed it there too.
>
> The problems with winextensions are not not related but are due to "bad"
> Docbook code. I know where they are coming from but need to understand what
> the author was attempting to do and then determine how to do it "right".
>
Please explain what the issue it so we can help to decide now to fix it.

Rick



> Gil
> On 3/31/2020 10:26 AM, P.O. Jonsson wrote:
>
> Ok, missed that part :-(
>
> I have replaced xhtml-common.xsl now and winextensions build as it should,
> so this was probably the problem. This tiniest change cased the problem
> thus:
>
> 1
>
> changed into
>
> 0  Gil Barmwater
>
>
>
> ___
> Oorexx-devel mailing 
> listOorexx-devel@lists.sourceforge.nethttps://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
>
>
>
>
> ___
> Oorexx-devel mailing 
> listOorexx-devel@lists.sourceforge.nethttps://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
>
>
>
>
> ___
> Oorexx-devel mailing 
> listOorexx-devel@lists.sourceforge.nethttps://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
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[P. O. Jonsson]

Ok now I understand. Publican is written in Perl so this is where it comes from 
I guess. 

Von meinem iPhone gesendet

> Am 31.03.2020 um 17:04 schrieb Gil Barmwater :
> 
> 
> Well, as I mentioned, this was a problem with the PDF builds as well. So I 
> looked in the PDF.xsl for where the "No adjustColumnWidths function 
> available" message was generated and found that there was a parameter - 
> tablecolumns.extension - that controlled that function. Since we don't use 
> Perl and don't have the Perl function anyway, I decided to try disabling the 
> function by changing the parameter expecting this would cause other side 
> effects. Luckily, it didn't. So when this surfaced in the HTML generation, I 
> found the same parameter in the xhtml-common.xsl file and changed it there 
> too.
> 
> The problems with winextensions are not not related but are due to "bad" 
> Docbook code. I know where they are coming from but need to understand what 
> the author was attempting to do and then determine how to do it "right".
> 
> Gil
> 
> On 3/31/2020 10:26 AM, P.O. Jonsson wrote:
>> Ok, missed that part :-(
>> 
>> I have replaced xhtml-common.xsl now and winextensions build as it should, 
>> so this was probably the problem. This tiniest change cased the problem thus:
>> 
>> 1
>> 
>> changed into
>> 
>> 0 > Gil Barmwater
>> 
>> 
>> 
>> ___
>> 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
 
 
 
 
 ___
 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
>> 
>> 
>> 
>> 
>> ___
>> 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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

Well, as I mentioned, this was a problem with the PDF builds as well. So 
I looked in the PDF.xsl for where the "No adjustColumnWidths function 
available" message was generated and found that there was a parameter - 
tablecolumns.extension - that controlled that function. Since we don't 
use Perl and don't have the Perl function anyway, I decided to try 
disabling the function by changing the parameter expecting this would 
cause other side effects. Luckily, it didn't. So when this surfaced in 
the HTML generation, I found the same parameter in the xhtml-common.xsl 
file and changed it there too.


The problems with winextensions are not not related but are due to "bad" 
Docbook code. I know where they are coming from but need to understand 
what the author was attempting to do and then determine how to do it 
"right".


Gil

On 3/31/2020 10:26 AM, P.O. Jonsson wrote:

Ok, missed that part :-(

I have replaced xhtml-common.xsl now and winextensions build as it 
should, so this was probably the problem. This tiniest change cased 
the problem thus:


1

changed into

0 

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

Ok, missed that part :-(

I have replaced xhtml-common.xsl now and winextensions build as it should, so 
this was probably the problem. This tiniest change cased the problem thus:

1

changed into

0 >>> Gil Barmwater
 
 
 
 ___
 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 
>>> 
>> 
>> 
>> 
>> 
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

I replaced it in the delta folder and the "package" zip file in my 
Dropbox. Here 
 
is a link to the delta folder.


Gil

On 3/31/2020 9:33 AM, P.O. Jonsson wrote:
I saw that message as well but did not see that you had sent us a new 
stylesheet? Where do I get it?


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 



Am 31.03.2020 um 15:31 schrieb Gil Barmwater >:


OK, I've had a look at the log (whew!) and found what I was expecting 
- the same message Rony ran into about "No adjustColumnWidths 
function available". You must have missed the message I sent about it:


"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."


So please replace the file xhtml-common.xsl with the corrected one in 
the delta (or the package). This should allow the DOC2HTML process to 
complete on all the books with missing parts. Thanks.


Gil

On 3/30/2020 7:37 PM, Gil Barmwater wrote:


I'll take a look at the log in the morning, thanks!

Gil

On 3/30/2020 5:47 PM, P.O. Jonsson wrote:

Dear Gil,

I can still not build rexxextensions, it seems the process breaks 
somewhere halfway, index.html is always missing


I have added the parameter --verbose to xslt and saved the output 
to a file, you can look at it in my dropbox.


To be sure we are talking the same language here some info about my 
machine.


Microsoft Windows 10 PRO 64 bit
Version 1909
OS build 1863.720
Version 10.0.18363.720

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)

Please note that I have 64 bit and some of the tools are 32 bit

Please let me know what I can do further to iron this out. Before I 
have the same result as you can provide I will not move it to Jenkins


I have not found a place where I can increase the Java Heap?

Signing off for tonight.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 





___
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

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


--
Gil Barmwater

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

Dear Rony,

The Win 10 machine is a physical machine with i7 Processor and 16 GB memory so 
I do not think this is the problem. I think Gil just gave us the explanation :-)

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 31.03.2020 um 15:18 schrieb Rony G. Flatscher :
> 
> Hi P.O.,
> 
> was able to create the HTML renderings for rexxref and rexxpg without doing 
> anything special on a Windows 10 machine with 24 GB memory. If you are 
> running Win 10 in a virtual machine maybe you can try increasing its memory?
> 
> Here the last paragraph in Gil's read1st.txt which shows how to increase the 
> maximum Java heap size (-Xmx2048M):
> 
> Optional Parameters
> ---
> 
> It may be desirable at times to specify additional parameters for the 
> transform
> step and/or the step that creates the PDF/HTML files.  This can be done 
> without
> modifying the command files by setting the appropriate environment variables.
> For example issuing the command "set xslt_opts=--param toc.max.depth 4" before
> running the doc2fo command file would result in the Table Of Contents having
> four levels rather than the default of three and "set xslt_opts=--timing" 
> would
> cause timing messages for each of the steps in the transform process to be
> displayed.  The PDF creation step uses a Java program named FOP and parameters
> for Java can be specified using the fop_opts environment variable.  An example
> might be to increase the Java heap space to 2GB by issuing the command
> "set fop_opts=-Xmx2048M".  You might need to do this if you are building the
> largest of the ooRexx documents.
> 
> Any questions, comments or suggestions for improvement should be sent to me 
> at:
> gbarmwa...@alum.rpi.edu 
> 
> Gil Barmwater
> version 2.0
> To get Java's non-standard startup-switches just enter "java -X" on the 
> command line and you get an extensive list of additional switches that 
> control the JVM.
> ---rony
> 
> 
> On 31.03.2020 08:56, P.O. Jonsson wrote:
>> Thanks for checking. From what I have seen the rendering is great, no 
>> oversized boxes or anything, now we just have to figure out why I cannot 
>> render all books using your tools.
>> 
>> Here is some further info:
>> 
>> These books are working and appear complete, I have tried to navigate them 
>> and could not find any problems
>> orxncurses
>> readme
>> rexxextensions
>> rxftp
>> rxmath
>> unixextensions
>> 
>> These books are incomplete, at least index.html missing, in many cases only 
>> a few chapters are rendered
>> ooconsole
>> oodguide
>> oodialog
>> oosqlite
>> ootest
>> rexxapi
>> rexxgtk
>> rexxpg
>> rexxref
>> rxsock
>> winextensions
>> 
>> This book is not considered
>> buildmachine (this book is referred to as oorexxbuild internally and build 
>> if the buildmachine folder in SVN is renamed to oorexxbuild)
>> 
>> The feeling I get is that the processing just stops somewhere in the middle 
>> of the processing, so it might be an illegal command that triggers this? 
>> Just guessing
>> 
>> Then I have a general question: after/during the processing there are no 
>> documents at all in the fo_files and log_files directories - how come?
>> 
>> -- 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>>> Am 31.03.2020 um 01:37 schrieb Gil Barmwater >> >:
>>> 
>>> I'll take a look at the log in the morning, thanks!
>>> 
>>> Gil
>>> On 3/30/2020 5:47 PM, P.O. Jonsson wrote:
 Dear Gil,
 
 I can still not build rexxextensions, it seems the process breaks 
 somewhere halfway, index.html is always missing
 
 I have added the parameter --verbose to xslt and saved the output to a 
 file, you can look at it in my dropbox.
 
 To be sure we are talking the same language here some info about my 
 machine.
 
 Microsoft Windows 10 PRO 64 bit
 Version 1909
 OS build 1863.720
 Version 10.0.18363.720
 
 java version "1.8.0_241"
 Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
 Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)
 
 Please note that I have 64 bit and some of the tools are 32 bit
 
 Please let me know what I can do further to iron this out. Before I have 
 the same result as you can provide I will not move it to Jenkins
 
 I have not found a place where I can increase the Java Heap?
 
 Signing off for tonight.
 
 Hälsningar/Regards/Grüsse,
 P.O. Jonsson
 oor...@jonases.se 
 
 
> 
> ___
> 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

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

The DOC2HTML process is only a one-step one so we go from Docbook-XML 
directly to HTML. There is no "intermediate" .fo file created as a 
result. The log file is produced by FOP which is not needed or run in 
this case. So that is why those folders are empty when we create HTML files.


Gil

On 3/31/2020 2:56 AM, P.O. Jonsson wrote:


Then I have a general question: after/during the processing there are 
no documents at all in the fo_files and log_files directories - how come?


--
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 



Am 31.03.2020 um 01:37 schrieb Gil Barmwater >:


I'll take a look at the log in the morning, thanks!

Gil

On 3/30/2020 5:47 PM, P.O. Jonsson wrote:

Dear Gil,

I can still not build rexxextensions, it seems the process breaks 
somewhere halfway, index.html is always missing


I have added the parameter --verbose to xslt and saved the output to 
a file, you can look at it in my dropbox.


To be sure we are talking the same language here some info about my 
machine.


Microsoft Windows 10 PRO 64 bit
Version 1909
OS build 1863.720
Version 10.0.18363.720

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)

Please note that I have 64 bit and some of the tools are 32 bit

Please let me know what I can do further to iron this out. Before I 
have the same result as you can provide I will not move it to Jenkins


I have not found a place where I can increase the Java Heap?

Signing off for tonight.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 





___
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




___
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

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

I saw that message as well but did not see that you had sent us a new 
stylesheet? Where do I get it?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 31.03.2020 um 15:31 schrieb Gil Barmwater :
> 
> OK, I've had a look at the log (whew!) and found what I was expecting - the 
> same message Rony ran into about "No adjustColumnWidths function available". 
> You must have missed the message I sent about it:
> 
> "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."
> 
> So please replace the file xhtml-common.xsl with the corrected one in the 
> delta (or the package). This should allow the DOC2HTML process to complete on 
> all the books with missing parts. Thanks.
> 
> Gil
> On 3/30/2020 7:37 PM, Gil Barmwater wrote:
>> I'll take a look at the log in the morning, thanks!
>> 
>> Gil
>> On 3/30/2020 5:47 PM, P.O. Jonsson wrote:
>>> Dear Gil,
>>> 
>>> I can still not build rexxextensions, it seems the process breaks somewhere 
>>> halfway, index.html is always missing
>>> 
>>> I have added the parameter --verbose to xslt and saved the output to a 
>>> file, you can look at it in my dropbox.
>>> 
>>> To be sure we are talking the same language here some info about my machine.
>>> 
>>> Microsoft Windows 10 PRO 64 bit
>>> Version 1909
>>> OS build 1863.720
>>> Version 10.0.18363.720
>>> 
>>> java version "1.8.0_241"
>>> Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
>>> Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)
>>> 
>>> Please note that I have 64 bit and some of the tools are 32 bit
>>> 
>>> Please let me know what I can do further to iron this out. Before I have 
>>> the same result as you can provide I will not move it to Jenkins
>>> 
>>> I have not found a place where I can increase the Java Heap?
>>> 
>>> Signing off for tonight.
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> 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 
>> 
> -- 
> 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

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

OK, I've had a look at the log (whew!) and found what I was expecting - 
the same message Rony ran into about "No adjustColumnWidths function 
available". You must have missed the message I sent about it:


"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."


So please replace the file xhtml-common.xsl with the corrected one in 
the delta (or the package). This should allow the DOC2HTML process to 
complete on all the books with missing parts. Thanks.


Gil

On 3/30/2020 7:37 PM, Gil Barmwater wrote:


I'll take a look at the log in the morning, thanks!

Gil

On 3/30/2020 5:47 PM, P.O. Jonsson wrote:

Dear Gil,

I can still not build rexxextensions, it seems the process breaks 
somewhere halfway, index.html is always missing


I have added the parameter --verbose to xslt and saved the output to 
a file, you can look at it in my dropbox.


To be sure we are talking the same language here some info about my 
machine.


Microsoft Windows 10 PRO 64 bit
Version 1909
OS build 1863.720
Version 10.0.18363.720

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)

Please note that I have 64 bit and some of the tools are 32 bit

Please let me know what I can do further to iron this out. Before I 
have the same result as you can provide I will not move it to Jenkins


I have not found a place where I can increase the Java Heap?

Signing off for tonight.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 





___
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


--
Gil Barmwater

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Rony G. Flatscher]

Hi P.O.,

was able to create the HTML renderings for rexxref and rexxpg without doing 
anything special on a
Windows 10 machine with 24 GB memory. If you are running Win 10 in a virtual 
machine maybe you can
try increasing its memory?

Here the last paragraph in Gil's read1st.txt which shows how to increase the 
maximum Java heap size
(-Xmx2048M):

Optional Parameters
---

It may be desirable at times to specify additional parameters for the 
transform
step and/or the step that creates the PDF/HTML files.  This can be done 
without
modifying the command files by setting the appropriate environment 
variables.
For example issuing the command "set xslt_opts=--param toc.max.depth 4" 
before
running the doc2fo command file would result in the Table Of Contents having
four levels rather than the default of three and "set xslt_opts=--timing" 
would
cause timing messages for each of the steps in the transform process to be
displayed.  The PDF creation step uses a Java program named FOP and 
parameters
for Java can be specified using the fop_opts environment variable.  An 
example
might be to increase the Java heap space to 2GB by issuing the command
"*set fop_opts=-Xmx2048M*".  You might need to do this if you are building 
the
largest of the ooRexx documents.

Any questions, comments or suggestions for improvement should be sent to me 
at:
gbarmwa...@alum.rpi.edu

Gil Barmwater
version 2.0

To get Java's non-standard startup-switches just enter "java -X" on the command 
line and you get an
extensive list of additional switches that control the JVM.

---rony



On 31.03.2020 08:56, P.O. Jonsson wrote:
> Thanks for checking. From what I have seen the rendering is great, no 
> oversized boxes or anything,
> now we just have to figure out why I cannot render all books using your tools.
>
> Here is some further info:
>
> These books are working and appear complete, I have tried to navigate them 
> and could not find any
> problems
> orxncurses
> readme
> rexxextensions
> rxftp
> rxmath
> unixextensions
>
> These books are incomplete, at least index.html missing, in many cases only a 
> few chapters are
> rendered
> ooconsole
> oodguide
> oodialog
> oosqlite
> ootest
> rexxapi
> rexxgtk
> rexxpg
> rexxref
> rxsock
> winextensions
>
> This book is not considered
> buildmachine (this book is referred to as oorexxbuild internally and build if 
> the buildmachine
> folder in SVN is renamed to oorexxbuild)
>
> The feeling I get is that the processing just stops somewhere in the middle 
> of the processing, so
> it might be an illegal command that triggers this? Just guessing
>
> Then I have a general question: after/during the processing there are no 
> documents at all in the
> fo_files and log_files directories - how come?
>
> -- 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
>
>
>
>> Am 31.03.2020 um 01:37 schrieb Gil Barmwater > >:
>>
>> I'll take a look at the log in the morning, thanks!
>>
>> Gil
>>
>> On 3/30/2020 5:47 PM, P.O. Jonsson wrote:
>>> Dear Gil,
>>>
>>> I can still not build rexxextensions, it seems the process breaks somewhere 
>>> halfway, index.html
>>> is always missing
>>>
>>> I have added the parameter --verbose to xslt and saved the output to a 
>>> file, you can look at it
>>> in my dropbox.
>>>
>>> To be sure we are talking the same language here some info about my machine.
>>>
>>> Microsoft Windows 10 PRO 64 bit
>>> Version 1909
>>> OS build 1863.720
>>> Version 10.0.18363.720
>>>
>>> java version "1.8.0_241"
>>> Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
>>> Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)
>>>
>>> Please note that I have 64 bit and some of the tools are 32 bit
>>>
>>> Please let me know what I can do further to iron this out. Before I have 
>>> the same result as you
>>> can provide I will not move it to Jenkins
>>>
>>> I have not found a place where I can increase the Java Heap?
>>>
>>> Signing off for tonight.
>>>
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>>
>>>

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

Thanks for checking. From what I have seen the rendering is great, no oversized 
boxes or anything, now we just have to figure out why I cannot render all books 
using your tools.

Here is some further info:

These books are working and appear complete, I have tried to navigate them and 
could not find any problems
orxncurses
readme
rexxextensions
rxftp
rxmath
unixextensions

These books are incomplete, at least index.html missing, in many cases only a 
few chapters are rendered
ooconsole
oodguide
oodialog
oosqlite
ootest
rexxapi
rexxgtk
rexxpg
rexxref
rxsock
winextensions

This book is not considered
buildmachine (this book is referred to as oorexxbuild internally and build if 
the buildmachine folder in SVN is renamed to oorexxbuild)

The feeling I get is that the processing just stops somewhere in the middle of 
the processing, so it might be an illegal command that triggers this? Just 
guessing

Then I have a general question: after/during the processing there are no 
documents at all in the fo_files and log_files directories - how come?

-- 
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 31.03.2020 um 01:37 schrieb Gil Barmwater :
> 
> I'll take a look at the log in the morning, thanks!
> 
> Gil
> On 3/30/2020 5:47 PM, P.O. Jonsson wrote:
>> Dear Gil,
>> 
>> I can still not build rexxextensions, it seems the process breaks somewhere 
>> halfway, index.html is always missing
>> 
>> I have added the parameter --verbose to xslt and saved the output to a file, 
>> you can look at it in my dropbox.
>> 
>> To be sure we are talking the same language here some info about my machine.
>> 
>> Microsoft Windows 10 PRO 64 bit
>> Version 1909
>> OS build 1863.720
>> Version 10.0.18363.720
>> 
>> java version "1.8.0_241"
>> Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
>> Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)
>> 
>> Please note that I have 64 bit and some of the tools are 32 bit
>> 
>> Please let me know what I can do further to iron this out. Before I have the 
>> same result as you can provide I will not move it to Jenkins
>> 
>> I have not found a place where I can increase the Java Heap?
>> 
>> Signing off for tonight.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> 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

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

I'll take a look at the log in the morning, thanks!

Gil

On 3/30/2020 5:47 PM, P.O. Jonsson wrote:

Dear Gil,

I can still not build rexxextensions, it seems the process breaks 
somewhere halfway, index.html is always missing


I have added the parameter --verbose to xslt and saved the output to a 
file, you can look at it in my dropbox.


To be sure we are talking the same language here some info about my 
machine.


Microsoft Windows 10 PRO 64 bit
Version 1909
OS build 1863.720
Version 10.0.18363.720

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)

Please note that I have 64 bit and some of the tools are 32 bit

Please let me know what I can do further to iron this out. Before I 
have the same result as you can provide I will not move it to Jenkins


I have not found a place where I can increase the Java Heap?

Signing off for tonight.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se 





___
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