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 other parts of the book are modified.
Hmm, could it be that there exist some scripts that would update/generate that
rexxref.ent file? If
so, does anyone happen to know where to look for them? (Definitely there would
be a need for a
checklist for the rexxref book like file to change when something gets edited,
when to run which
scripts if any, and the like.)
BTW it would be possible to determine the revision number for any single book
using "svn log" and
then extract the revision number from there, e.g.:
F:\work\svn\oorexx\docs\trunk>svn log -l 1 rxmath
------------------------------------------------------------------------
r11204 | erich_st | 2017-02-14 21:51:36 +0100 (Tue, 14 Feb 2017) | 1 line
add rxmath Railroad Diagram Generator xhtml file
------------------------------------------------------------------------
F:\work\svn\oorexx\docs\trunk>svn log -l 1 rexxref
------------------------------------------------------------------------
r11985 | erich_st | 2020-02-27 21:24:37 +0100 (Thu, 27 Feb 2020) | 1 line
code fixed, tests added and rexxref updated for [feature-requests:#722] use
.cls in the search order for ::requires loads
------------------------------------------------------------------------
Using the -v (verbose) flag, the latest rexxref log looks like:
F:\work\svn\oorexx\docs\trunk>svn log -l 1 -v rexxref
------------------------------------------------------------------------
r11985 | erich_st | 2020-02-27 21:24:37 +0100 (Thu, 27 Feb 2020) | 1 line
Changed paths:
M /docs/trunk/rexxref/en-US/funct.xml
M /docs/trunk/rexxref/en-US/fundclasses.xml
M /main/trunk/interpreter/classes/PackageClass.cpp
M /main/trunk/interpreter/classes/PackageClass.hpp
M /main/trunk/interpreter/execution/RexxActivation.cpp
M /main/trunk/interpreter/execution/RexxActivation.hpp
M /main/trunk/interpreter/execution/RexxCode.hpp
M /main/trunk/interpreter/instructions/RequiresDirective.cpp
M /test/trunk/ooRexx/base/directives/REQUIRES.testGroup
M /test/trunk/ooRexx/base/keyword/CALL.testGroup
code fixed, tests added and rexxref updated for [feature-requests:#722] use
.cls in the search order for ::requires loads
------------------------------------------------------------------------
Using the xml output mode:
F:\work\svn\oorexx\docs\trunk>svn log -l 1 --xml rxmath
<?xml version="1.0" encoding="UTF-8"?>
<log>
<logentry
revision="11204">
<author>erich_st</author>
<date>2017-02-14T20:51:36.788717Z</date>
<msg>add rxmath Railroad Diagram Generator xhtml file</msg>
</logentry>
</log>
F:\work\svn\oorexx\docs\trunk>svn log -l 1 --xml rexxref
<?xml version="1.0" encoding="UTF-8"?>
<log>
<logentry
revision="11985">
<author>erich_st</author>
<date>2020-02-27T20:24:37.076649Z</date>
<msg>code fixed, tests added and rexxref updated for
[feature-requests:#722] use .cls in the search order for ::requires loads</msg>
</logentry>
</log>
Or maybe one would be even able to extract the revision number via xsl from the
results of just this
output:
F:\work\svn\oorexx\docs\trunk>svn log -l 1 --xml --with-no-revprops rxmath
<?xml version="1.0" encoding="UTF-8"?>
<log>
<logentry
revision="11204">
</logentry>
</log>
F:\work\svn\oorexx\docs\trunk>svn log -l 1 --xml --with-no-revprops rexxref
<?xml version="1.0" encoding="UTF-8"?>
<log>
<logentry
revision="11985">
</logentry>
</log>
O.K., sorry, have been carried away too far. :(
> Assuming ooRexx is installed is pretty safe but it could be verified using
> the "where" command.
> The difficulty in using Rexx scripts however comes from my decision to use
> environment variables
> to hold e.g. docpath and whichdoc. I also wanted the various steps to be able
> to be run
> independently so those variables need to "persist" between steps. Using
> simple "set" commands in a
> Rexx script will not accomplish that as they "go away" when the script ends.
> I believe one could
> use the registry class(?) to make them "permanent" but that then precludes a
> *ix solution.
>
One possible neutral solution in the case of Rexx would be to create a simple
config text file
(maybe even using the ooRexx Properties class for reading, changing and
writing) that serves as
(even some sort of a sticky) input instead of the environment variables.
> I have not done anything with HTML as I am not sure what our Publican process
> does to build them.
> This is surely another work item if we are to completely remove our
> dependency on Publican.
>
> The package does not make use of either the makefile or publican.cfg file
> that appear in the book
> directories. The only Publican-related files that the package uses are the
> two stylesheets -
> pdf.xsl and defaults.xsl which are in the package itself. BTW, the
> sources.txt file in the package
> documents all the pieces and from where they are derived.
>
Oh, thank you very much for pointing at "sources.txt"!!
Cheers
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
