On 8/12/2026 6:17 AM, Rony G. Flatscher wrote:
On 12.08.2026 12:11, Josep Maria Blasco wrote:
Thanks, Rony & Gil.
I've just uploaded hldocprep.rex, hldoc2fo.rex, hldoc2pdf.rex and
hldoc2HTML.rex to bldoc_orx. These are highlighter-enabled wrappers
for the usual doc building utilities.
😮
I've also added a bonus step in setup.rex (Windows-only) that
installs a copy of the Rexx Parser in .\rexx-parser\. I've used this
opportunity to change the code that tried to install the Liberation
Fonts from fontsquirrel, as the link that was provided doesn't work
any more; I'm using the copy located in ..\LiberationFonts.
+1
Please note that, currently, the whole of rexxref is
highlighter-enabled, in addition to Conventions.xml.
+1
That is great news (to me) as I had not noticed that the
<programlisting> tags had been updated as part of your earlier work on
that document! But, and there's always a "but", there are other
documents that have examples of ooRexx code in them and they will need
to be "highlighter-enabled".
Gil
Rony's idea of writing a script that automatically updated the
<programlisting> tags sounds like a good idea -- one could use
rxcheck for that. I will work on it as I find some spare time.
Wow, that would be great!
Thank you very much!!
Cheers
---rony
Missatge de Rony G. Flatscher <[email protected]> del dia dc.,
12 d’ag. 2026 a les 9:25:
On 11.08.2026 23:15, Gilbert Barmwater via Oorexx-devel wrote:
Note that making the tools available is only part of the
process; the documents need to have their <programlisting> tags
updated as well. Unless I missed it, that has NOT been done
(except for the Conventions.xml file which is part of the common
content in the oorexx folder). As that change does NOT affect
the current document build process, it can be done regardless of
any work on highlighting our documents. Just a heads-up.
Yes.
One possibility would be to use Josep Maria's great Rexx parser
(parses not only ooRexx, but all major Rexx languages, from
Regina to CMS Rexx), parsing all xml files, testing whether the
programlisting elements without a language attribute would be
valid Rexx code, and if so add the language="Rexx" attribute to
it. There may be false attribuitions, but these would surface
after creating the colored docs.
Given the great utility and importance of Josep Maria's Rexx
parser, I will propose to add it to the ooRexx distribution in a
separate e-mail and RFE.
Currently, for interested readers, the Rexx parser is available
via net-oo-rexx: https://github.com/RexxLA/net-oo-rexx/
---rony
On 8/11/2026 4:53 PM, Rony G. Flatscher wrote:
Dear Josep Maria,
On 03.08.2026 12:12, Josep Maria Blasco wrote:
The current refresh of the Rexx Parser includes a new
hldoc2HTML.rex tool in bin/docbook/. Together with
hldocprep.rex, hldoc2pdf.rex and hldoc2fo.rex, they allow to
transform properly tagged docbook .xml files into nicely
highlighter PDF and HTML files. Tagging is as simple as
substituting
<programlisting>
by
<programlisting language="rexx">
in all listings /that contain a valid ooRexx fragment/ (the
parser cannot highlight an invalid program for obvious reasons).
You can browse a highlighted PDF version of rexxref at
https://rexx.epbcn.com/rexxref/rexxref.pdf; the HTML version
can be found at https://rexx.epbcn.com/rexxref/. You can
choose your highlighting palette by using the upper-right
dropdown menu labeled "Coding style"; your choice is sticky,
and will accompany you while you're in the same web. You can
also add ?style=<style-name> as a query string, as in
https://rexx.epbcn.com/rexxref/keyReply.html?style=tokio-night;
in this case, the palette choice is not sticky, as this allows
the sharing of pages with a particular palette.
You will find the usage notes here:
https://rexx.epbcn.com/rexx-parser/bin/docbook/
That is *great*, thank you very much!
Would it be possible to incorporate your great tools
(hldocprep.rex, hldoc2pdf.rex, hldoc2fo.rex) into
"docs\trunk\tools" such that they are available for building
the docs in color, if your Rexx parser is available? In case
the Rexx parser is not available maybe fall back to
"docprep.rex", "doc2pdf.rex", and "doc2fo.rex"? Assuming that
"fo2pdf.rex" works on the black-and-white- and the
color-version .fo files.
---rony
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
