Re: [Oorexx-devel] New Process for Building the ooRexx Documentation, version 2

Hi Gil, On 28.03.2020 18:25, Gil Barmwater wrote: > Thanks for trying the new version of the package and I am happy that I > haven't broken the PDF > generation :-). One observation I forgot to mention: I created the pdf book in the old directory (version 1.2) after copying the delta-zip files

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12016] main/trunk

Dear P.O., for unknown reasons I do not get your commits via the oorexx-svn e-mail list. E-mails to "oorexx-svn" should be automatically be generated by Sourceforge upon a commit, which also contain the first 100KB of diff text. On 27.03.2020 21:26, P.O. Jonsson wrote: ... cut ... > Here is the

Re: [Oorexx-devel] New Process for Building the ooRexx Documentation, version 2

Dear Gil: sorry for coming back late, currently I am not the master of my time allotted to ooRexx... Since yesterday evening, after reading your e-mail, I was eager to get my hands on your version 2.0 and test it! Thank you also for taking the time and making a delta to 1.2 available for those

[Oorexx-devel] Licenses, tools ( Re: Documentation: using less bold font for some elements ?

FAICS at the moment no single license there would pose a problem on the ooRexx project. So my question is: what about tools that are needed to create the documentation that do not license CPL 1.0, but use licenses that do not infect the ooRexx license, can the be hosted with appropriate attribut

[Oorexx-devel] Ad generating the documentation without copying the common directory

Hi Gil, in the past fourteen days at one point in time I tried to get a book generated without having the "Common_Content" directory. It seemed that I could get it to run partly, but then it turned out it just would not work. In the meantime I had developed a few ideas, assumptions and today, w

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

Forgot to check in my changes that have led to yesterday's rendering of the rexxpg book, checked in with r12003. ---rony On 23.03.2020 19:09, Rony G. Flatscher wrote: > > Hi Gil, > > On 20.03.2020 19:07, Gil Barmwater wrote: >> I finally have had an opportunity to

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

Hi Erich, On 22.03.2020 11:56, Erich Steinböck wrote: > I agree with Gil.  Let's stay with our current coding/tagging style and the > typographic conventions. I concur as well, see my follow-up to Gil's mail. > Also, rgf_util2.rex is unacceptable for inclusion in our svn.  Please fix the > copyr

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

e same as method names. Please take a look at that and please give feedback ASAP whether that is o.k.? If it is o.k. the "Document Conventions" need to be changed accordingly as well. > > On 3/20/2020 9:15 AM, Rony G. Flatscher wrote: >> On 19.03.2020 14:31, Gil Barmwater wrot

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

On 20.03.2020 14:23, René Jansen wrote: > just want to correct one terminology issue: a monotype font is a font from a > specific foundry, a monospaced (or non-proportional) font is what you mean. Ah, yes, thank you René, also: . ---rony __

Re: [Oorexx-devel] Ad semcls.cls in rexxref (Re: Samples take 3

On 20.03.2020 14:14, Rick McGuire wrote: > > On Fri, Mar 20, 2020 at 9:13 AM Rony G. Flatscher <mailto:rony.flatsc...@wu.ac.at>> wrote: > > On 19.03.2020 12:21, Rick McGuire wrote: > > the sem.cls example is not intended to show how to use semaphores, but

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

On 19.03.2020 14:31, Gil Barmwater wrote: > > Having spent some time looking at the documentation while developing the > system to build the > books, I found that we actually have a set of conventions on how things are > displayed. This is > part of every document, under the title "Typographic Co

Re: [Oorexx-devel] Ad semcls.cls in rexxref (Re: Samples take 3

On 19.03.2020 12:21, Rick McGuire wrote: > the sem.cls example is not intended to show how to use semaphores, but rather > an example for how > to use guard. I think the example needs to be kept, but have no objections to > including a link to > the new classes. Thanks, have added the links loca

Re: [Oorexx-devel] Samples, take 1, changes to the readme in /samples

n 19.03.2020 11:47, P.O. Jonsson wrote: > I have provided the patch and will wait with the next step until that is in > the system. applied your patch with r12001, thank you! ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net h

Re: [Oorexx-devel] rexxpg book, a few things to be done

the winsystem and/or oodialog support would be able to fix it. ---rony On 16.03.2020 20:51, Rony G. Flatscher wrote: > > Overhauled the rexxpg book once more concluding my work on it as long as > nothing new pops up, > including any kind of errors. Checked the changes into trunk,

[Oorexx-devel] Documentation: using less bold font for some elements ?

While working on the documentation I learned the following elements being typeset in monotype font, however all are using the boldest version of the font which in the case of rexxpg makes some elements stand out far too strong. So the question would be whether it was possible to format the monot

Re: [Oorexx-devel] Samples, take 1, changes to the readme in /samples

Dear P.O., updating the readme should be o.k. in any case as it is a documentation improvement. Cheers ---rony On 16.03.2020 21:41, P.O. Jonsson wrote: > Dear Rony, > > Re >> Am 16.03.2020 um 20:18 schrieb Rony G. Flatscher > <mailto:rony.flatsc...@wu.ac.at>>: &g

[Oorexx-devel] Ad semcls.cls in rexxref (Re: Samples take 3

On 18.03.2020 08:14, P.O. Jonsson wrote: > > Among the samples there is a class *semcls.cls* that implements a semaphore > mechanism. > *Semcls.cls* is mentioned in the readme, but the corresponding *usessem.rex* > is missing so one > does not really know how to use the class. All other classes i

Re: [Oorexx-devel] rexxpg book, a few things to be done

Am 16.03.2020 um 21:53 schrieb Rick McGuire : > >  > Dis BIF center is noch in ooRexx. Warum sagst du das? 8-)) LOL! > >> On Mon, Mar 16, 2020 at 4:32 PM WalterPachl wrote: >> vii unten >> >> "Returns a string of length length with string centered in it and with pad >> characters >> added a

Re: [Oorexx-devel] rexxpg book, a few things to be done

mark below. If they can be fixed then they should go into rexxpg, hence requesting help for these Windows related scripts and feedback that I could/should use for an update of the book. ---rony On 15.03.2020 21:27, Rony G. Flatscher wrote: > > Not sure whether I get locked out of the

Re: [Oorexx-devel] Samples, take 1, changes to the readme in /samples

Dear P.O., On 16.03.2020 09:57, P.O. Jonsson wrote: > I have looked at the file readme in the samples subdirectory and compared it > to what is actually > present after installation on the Mac. I found a number of files present in > the samples subdir > that are not in the readme: > > arithmetic

[Oorexx-devel] rexxpg book, a few things to be done

Not sure whether I get locked out of the University hence committing the rexxpg work. The OS/2 remainders of CMD-files and all upercase filenames should be gone and match what is in "samples" e.g. A lot of work went into formatting (emphasizing, code/literal/filename). One area needs updating,

Re: [Oorexx-devel] Question ad .rexxinfo and CLS-samples ...

On 14.03.2020 21:51, Enrico Sorichetti via Oorexx-devel wrote: > There is a clash in the  nomenclature used by IBM software development  > And the one used in the *ix word  > > The IBM terminology is explained here > https://www.ibm.com/support/pages/vrmf-maintenance-stream-delivery-vehicle-termin

[Oorexx-devel] Question ad .rexxinfo and CLS-samples ...

Around here things have become a little bit crazy due to the Corona virus. Nevertheless could look into a few corners from time to time. --- ad .rexxinfo: one thing that I have stumbled over has to do with the namings of some information methods in .rexxinfo, which is a new class that gets intr

Re: [Oorexx-devel] RFB: rexxpg book: edited samples appendix, please proof read

: expected output against actual > output and the other way > around, so getting to much or to little output would be captured. Thank you for all of your efforts! Best regards ---rony >> Am 10.03.2020 um 19:34 schrieb Rony G. Flatscher > <mailto:rony.flatsc...@wu.ac.at>>

Re: [Oorexx-devel] RFB: rexxpg book: edited samples appendix, please proof read

In order not to start with editing the class tree section ("Chapter 4. The Basics of Classes") before some time has gone by to be able to object about the planned content, I turned to the samples section ("Appendix B. Sample Rexx Programs") which took quite some work to iron it out (obsolete scr

Re: [Oorexx-devel] Three questions (New questions (Re: Questions ad class hierarchy for rexxpg book

On 10.03.2020 14:24, Rick McGuire wrote: > > On Tue, Mar 10, 2020 at 9:12 AM Rony G. Flatscher <mailto:rony.flatsc...@wu.ac.at>> wrote: > > Thank you for your feedback, Rick. As a result the current rexxpg book at > > <https://www.dropbox.com/sh/gxvvgskb04g

[Oorexx-devel] Three questions (New questions (Re: Questions ad class hierarchy for rexxpg book

Thank you for your feedback, Rick. As a result the current rexxpg book at reflects the changed hierarchy tree (created from a script). There would be two questions still: * the original book documents the "RegularExpre

[Oorexx-devel] A more compact, yet complete class hierarchy listing (Re: Questions ad class hierarchy for rexxpg book

ompact, yet complete" class hierarchy be used? ---rony On 09.03.2020 18:11, Rony G. Flatscher wrote: > > The rexxpg book lists in "Chapter 4. The Basics of Classes" all ooRexx > classes. The listing is not > correctly indented as the root class Object is not shown as the

[Oorexx-devel] Questions ad class hierarchy for rexxpg book

The rexxpg book lists in "Chapter 4. The Basics of Classes" all ooRexx classes. The listing is not correctly indented as the root class Object is not shown as the topmost class. Before correcting anything I also created a little program that would create the ooRexx class tree automatically. Whi

Re: [Oorexx-devel] Another successful run on creating the rxmath.html documentation!

On 08.03.2020 21:51, Gil Barmwater wrote: > > Newest version of rxmath HTML files/folders is here > . I believe I've > gotten the majority of > the issues handled so please have another look. > Gil, I think you have solved the image proble

Re: [Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

On 08.03.2020 23:07, Jon Wolfers wrote: > Thanks Rick  > > I've got it now.  That is how one would want it to work. > Not sure what should go in the rexxpg but will sleep on it. :) Will wait for an explanation that is easy to understand, in excellent English and correct! ;-) ---rony P.S.: The

Re: [Oorexx-devel] (off topic) RFB: rexxpg book: changed rexxc documentation

eur Radio Station WB4ALM To:     Rony G. Flatscher Rony,  the revised wording read "okay" but somewhere, my mind stumbled a little -- I had a student of mine read it, and they thought the word "the" should be added as we did in the following example (in gree

Re: [Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

s it even more and thereby making it clearer it seems! Not being a native English speaker I leave it for others to judge whether the phrase "the interpreter ..." should remain or not. The rexxpg book now reflects Chip's suggestion without the phrase. ---rony > > On

Re: [Oorexx-devel] Inconsistent names in .rexxinfo and .file classes for the operating system dependent separator characters

On 08.03.2020 20:00, Erich Steinböck wrote: > No. > RexxInfo and File both use "pathSeparator". Ah, I missed the File one, sorry. > For the directory separator, File is using separator, but for the new > RexxInfo a decision was made > to use directorySeparator. They should use the same name suc

[Oorexx-devel] Inconsistent names in .rexxinfo and .file classes for the operating system dependent separator characters

The new RexxInfo class uses the name "directorySeparator" whereas the File class uses the name "pathSeparator" (';' or ':'). The new RexxInfo class uses the name "separator" whereas the File class uses the name "fileSeparator" ('/' or '\'): It would be benefitial if both names would be the same

Re: [Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

anguage level in the compiled image is > tied to the features > being used, not to the level of interpreter used to compile it. Of course > currently, the only > language level is that used by 5.0, but the mechanism is in place to maintain > that compatibility.  > > Rick >

Re: [Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

Incorporated Jon's feedback, removed the last paragraph, introduced a note with the text draft, cf. current "rexxpg.pdf" from  <https://www.dropbox.com/sh/gxvvgskb04gdsqf/AACRo_ZLeFOdoBXUHroPY_-Ca?dl=0>. ---rony On 08.03.2020 17:12, Rony G. Flatscher wrote: > Hi Jon,

Re: [Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

s to be similar to > and should render > in a monotype font. Just a suggestion :-) !  Gil > > On 3/8/2020 11:51 AM, Rony G. Flatscher wrote: >> >> "RFB" is meant to mean "request for feedback"! >> >> Changed the rexxpg book in the section "App

Re: [Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

or each time you switch the bitness of the Rexx interpreter you need to run rexxc again. How does that sound? ---rony > On Sun, 8 Mar 2020 at 15:53, Rony G. Flatscher <mailto:rony.flatsc...@wu.ac.at>> wrote: > > "RFB" is meant to mean "request f

[Oorexx-devel] RFB: rexxpg book: changed rexxc documentation

"RFB" is meant to mean "request for feedback"! Changed the rexxpg book in the section "Appendix A. Distributing Programs without Source" (i.e. "rexxc") to reflect changes that have occurred: * It would be great to get brief feedback whether this is understandable the way it is now. * Also,

Re: [Oorexx-devel] A first (successful) run on creating the rxmath.html documentation!

On 07.03.2020 20:52, Gil Barmwater wrote: > > I've made more progress here and now have a set of HTML files, etc. for the > rxmath book. In spite > of the fact that the source is essentially the same and the stylesheets are > as well, the output > appears different in a number of ways. I can only

Re: [Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

On 07.03.2020 19:43, P.O. Jonsson wrote: > You looked in the wrong subdirectory, the Publican work is in > ooRexxDocs/oorexxDocs_11982_Publican/HTM Well, this helps a lot! :) > ALL books are there. I will give your RW to the folder for easier browsing. That's fine as it is! The HTML renderings l

Re: [Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

On 07.03.2020 17:55, P.O. Jonsson wrote: > To get an idea of how the HTML looks like from building with Publican have a > look in my Dropbox >   > in the > subfolder ooRexxDocs/oorexxDocs_11982_Publican/HTML, this was the

Re: [Oorexx-devel] Question ad centering images

ybe > not. > > Nit .. some odd white space in the 2.9 first sentence. > > Mike > >> -Original Message- >> From: Rony G. Flatscher [mailto:rony.flatsc...@wu.ac.at] >> Sent: 07 March 2020 16:15 >> To: oorexx-devel@lists.sourceforge.net >> S

[Oorexx-devel] Question ad centering images

While working on the rexxpg book I noticed that all figures (actually the images) get left adjusted. It seems that centering the image data may slightly improve its appearence. To see the difference I created a version of rexxpg that centers all images, named "rexxpg-centered-figures.pdf" which

Re: [Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

Hi Erich, On 06.03.2020 21:21, Erich Steinböck wrote: > Rony, the SVG images work fine when building for PDF, but last time I tried > building for HTML, I > found that they displayed much worse than PNG. That is indeed quite strange. Maybe the transformation to html created replacement bitmaps i

Re: [Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

program if deemed necessary) and add the svg renderings. Best regards ---rony > > >> Am 06.03.2020 um 20:04 schrieb Rony G. Flatscher > <mailto:rony.flatsc...@wu.ac.at>>: >> >> Dear P.O., >> >> On 06.03.2020 19:50, P.O. Jonsson wrote: >>>

Re: [Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

On 06.03.2020 19:59, Jon Wolfers wrote: > IIRC I created those images - I can't remember why - I think the source was > unavailable or the > previous lot were unusable. There are also pdf-renderings of the graphics which do not get used AFAICS, therefore I would plan to delete them, if no one obj

Re: [Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

yes, all books are generated with Gil's toolset (I would not be able to do that without it)! Cheers ---rony > >> Am 06.03.2020 um 18:57 schrieb Rony G. Flatscher > <mailto:rony.flatsc...@wu.ac.at>>: >> >> The "Programming Guide" (rexxpg.pdf) uses png-

[Oorexx-devel] rexxpg.pdf: using svg instead of png graphics?

The "Programming Guide" (rexxpg.pdf) uses png-bitmaps created from OpenOffice odg graphics that look somewhat faint making the book look somehow unfinished, like a draft. After experimenting with different formats the best results seem to be with svg (scalable vector graphics) graphics. To see

Re: [Oorexx-devel] Question ad using "accepted" instead of "pending" ?

ticket. It remains in > the Pending state until it actually ships in a release and will be moved to > Closed at that time. > Accepted means that a ticket has been accepted for inclusion, but not all > work items are completed > yet on the item.  > > Rick > > On We

[Oorexx-devel] One todo item left (Re: About experimentally splitting 'rexxpg.pdf' into 'rexxprimer.pdf' and into 'rexxapi.pdf'

i.pdf ${DOC_SOURCE_DIR}/rexxpg.pdf ${DOC_SOURCE_DIR}/rexxref.pdf ${DOC_SOURCE_DIR}/rxmath.pdf Would anyone object if I added it to CMakeLists.txt ? ---rony On 03.03.2020 17:54, Rony G. Flatscher wrote: > > Enter

[Oorexx-devel] Question ad using "accepted" instead of "pending" ?

Just saw that when an RFE was worked upon the status was set to "accepted" (e.g. ) which makes the RFE still be listed and also the "Pending work items" column displays "doc+test". Now I would be wondering about two things: * Is it o.k. t

Re: [Oorexx-devel] About experimentally splitting 'rexxpg.pdf' into 'rexxprimer.pdf' and into 'rexxapi.pdf'

Entered an RFE [1] to this effect and supplied the sources for the two split books with it. ---rony [1] RFE "#773 Split 'rexxpg' into two books ... ": <https://sourceforge.net/p/oorexx/feature-requests/773/> On 03.03.2020 14:52, Rony G. Flatscher wrote: > > D

Re: [Oorexx-devel] About experimentally splitting 'rexxpg.pdf' into 'rexxprimer.pdf' and into 'rexxapi.pdf'

ght be better to retain the name rexxpg for the primer, in > line with traditional > language doco. > > Harmander Singh   > > On Tue, 3 Mar 2020 at 08:26, Jon Wolfers <mailto:sahana...@gmail.com>> wrote: > > +1 > > This makes sense to me. >

[Oorexx-devel] How to "forward" a call to a routine with all its arguments to a different routine in a single statement?

In method routines one can use the FORWARD keyword instruction to forward the message to a different method. To do so is quite simple and versatile from method routines. In the context of event attribute routines it is many times necessary to call another routine and supply it all the received a

Re: [Oorexx-devel] Fwd: CentOS 2 Failures in build

P.O., maybe it would be also a good idea to create a bug ticket [1] with this and supply your data there as well. This will make this bug trackable and once it has been solved, can be closed in the bug tracking system. Cheers ---rony [1] ooRexx Bug Tickte:

Re: [Oorexx-devel] ooRexx-docs: howto create rail-diagrams

Well, there is already a Wiki about creating rail-diagrams at <https://sourceforge.net/p/oorexx/wiki/how-to-change-oorexx-docs/>! The ooRexx Wiki home is at: <https://sourceforge.net/p/oorexx/wiki/Home/>. ---rony On 01.03.2020 19:39, Rony G. Flatscher wrote: > > While

[Oorexx-devel] About experimentally splitting 'rexxpg.pdf' into 'rexxprimer.pdf' and into 'rexxapi.pdf'

For almost decades it has irritated me that the "rexxpg.pdf" book would contain a primer to ooRexx and the native APIs. The former would be helfpul for anyone who wants to learn ooRexx, the latter is only helpful for people who have expert knowledge on C++ (and ooRexx) and C. So I tried to split

Re: [Oorexx-devel] Fwd: Segmentation fault

Hi P.O., the ooRexx developer wiki has the explanation of how to debug this: and get at all the necessary information. HTH ---rony On 02.03.2020 17:24, P.O. Jonsson wrote: > Dear developers, > > While updating some Linuxbuilds today

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

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

Re: [Oorexx-devel] Automated ooRexx documentation builds

On 02.03.2020 13:52, P.O. Jonsson wrote: > This is just to say that we can now reliably build the pdf documentation > using Jenkins thanks to > Gil´s initiative > > Starting to launch documentation builds: 12:11:37,47 > ... > 13:27:29 - PDF created Finished building documentation: 13:27:29,08 Arch

[Oorexx-devel] ooRexx-docs: howto create rail-diagrams

While incorporating the documentation for EventSemaphore and MutexSemaphore I had a need to create some rail-diagrams for the methods. It may be the case that others may have a need for that earlier or later, therefore this posting. Remembering that Erich once posted the information that he woul

[Oorexx-devel] Patch to update rexxref with the new utility classes EventSemaphore and MutexSemaphore

Thanks to the new ability to create the rexx documentation on my own without having a need to first learn Publican, but just use Gil's "fool-proof" tool chain, I have become able to incorporate my documentations about EventSemaphore and MutexSemaphore and just posted the patch for applying it fr

Re: [Oorexx-devel] Docs: question ad "howtos" when adding documentation ...

On 29.02.2020 20:50, Rony G. Flatscher wrote: > On 26.02.2020 17:35, Rony G. Flatscher wrote: >> >> While peeking around the xml documentation for rexxref I stumbled over >> comments that read like >> >> rexxref/en-US/alarmnotificationclass

Re: [Oorexx-devel] Docs: question ad "howtos" when adding documentation ...

On 26.02.2020 17:35, Rony G. Flatscher wrote: > > While peeking around the xml documentation for rexxref I stumbled over > comments that read like > > rexxref/en-US/alarmnotificationclassmethods.xml: > rexxref/en-US/alarmnotificationclassmethods.xml: > > ... cut

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

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

Re: [Oorexx-devel] Ad svn revision number in rexxref (Re: A first (successful) run on creating the rexxref.pdf documentation! ...

Dear P.O., On 29.02.2020 16:54, P.O. Jonsson wrote: > Am 29.02.2020 um 16:47 schrieb Rony G. Flatscher <mailto:rony.flatsc...@wu.ac.at>>: >> >> Looked into the svn revision issue.  > > It is my understanding that the books will have the versions and revision as >

[Oorexx-devel] Ad svn revision number in rexxref (Re: A first (successful) run on creating the rexxref.pdf documentation! ...

Looked into the svn revision issue. There exists a file "rexxref\en-US\rexxref.ent" (dated February 25th) that contains among other things the revision number: F:\work\svn\oorexx\docs\trunk>type rexxref\en-US\rexxref.ent ** .nil"> .true"> .

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

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

[Oorexx-devel] Docs: question ad "howtos" when adding documentation ...

While peeking around the xml documentation for rexxref I stumbled over comments that read like rexxref/en-US/alarmnotificationclassmethods.xml: rexxref/en-US/alarmnotificationclassmethods.xml: Here a list of xml files that seem to contain such generated text ("GENERATED" in uppercase):

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

Dear Gil, On 25.02.2020 15:31, Gil Barmwater wrote: > Thanks so much for the feedback! I was unaware of the "timing " switch so > will consider adding > that to my package in order to give the user some indication that things are > still running. On my > laptop the transform step also takes >5 m

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

Pelican, yet being able to create the same formatted documentation! This is just *great*! Also it means that more people become able to work with the documentation! Thank you very much for all of your efforts so far, kudos to you! ---rony On 25.02.2020 12:57, Rony G. Flatscher wrote: > >

Re: [Oorexx-devel] Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear Gil, this is super, thank you *very* much!! On 24.02.2020 19:48, Gil Barmwater wrote: > > It is time to make the package available to this group! I have updated the > package, zipped it up, > transferred it to another system, installed it and successfully built the > rexxref, rxmath and >

Re: [Oorexx-devel] Ad empty line problem (Re: New Process for Building the ooRexx Documentation

On 23.02.2020 22:34, P.O. Jonsson wrote: > If the millipoints are Adobe millipoints 77 adobe millipoints = 0.027 mm > > I have also noticed errors/warnings while looking at the builds, I have put a > notice in my Dropbox > if anyone wants to have a look, as Gil points out there seems to be no > v

Re: [Oorexx-devel] Ad empty line problem (Re: New Process for Building the ooRexx Documentation

On 23.02.2020 21:56, Gil Barmwater wrote: > > I have added the templates to the pdf.xsl file I have been using and deleted > the call to > fop-preprocess.rex. When I run the doc2fo and the fo2pdf steps I get what > appears to be the same > result as when using the fop-preprocess script! Here >

Re: [Oorexx-devel] Ad empty line problem (Re: New Process for Building the ooRexx Documentation

On 23.02.2020 20:04, Erich Steinböck wrote: > Gil, with your new doc tools build chain, do you still see those (maybe > thousands) of "Content > overflows the viewport of the fo:region-after on page ... in > block-progression direction by 77 > millipoints." (and lots of other) warnings that curre

Re: [Oorexx-devel] CDATA-sections ... (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear P.O., dear Gil: the version below should tackle almost all cases, except of: * if a programlisting element content starts with blanks followed by one or more [CR-]LF then no stripping takes place: it is assumed that the white space is there intentionally * if a programlisting eleme

[Oorexx-devel] CDATA-sections ... (Re: Ad empty line problem (Re: New Process for Building the ooRexx Documentation

Dear P.O., thank you for all of your efforts and work which allowed me to quickly find the reason for spurious additional blank lines! The reason is that there are quite a few programlisting elements with a CDATA-section content which the script has not tackled so far. So here an adjusted vers

[Oorexx-devel] Ad empty line problem (Re: New Process for Building the ooRexx Documentation

On 20.02.2020 23:20, P.O. Jonsson wrote: > This is just to inform that I have managed to inject Erich Rexx script in my > build chain so that > my built documents should now be 100% the same as yours and the ones built by > Erich or Rick. I > could only test it on rexxref.pdf but that is a beast

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

then what I can do about it. If I can get the > rexxref book to > build, I will make the tool package available so we can find any other > problems that may be lurking. > > Gil B. > > On 1/30/2020 10:26 AM, Rony G. Flatscher wrote: >> Dear Gil: >> >> thank you

Re: [Oorexx-devel] recent MacOS 10.15.2 and Xcode 'misses stdlib.h' build error

cOS-BSF4ooRexx installer that includes ooRexx5. So once your installer becomes part of the ooRexx build process for MacOS I will start to test the MacOS BSF4ooRexx installation part again! > > Von meinem iPhone gesendet > >> Am 06.02.2020 um 12:54 schrieb Rony G. Flatscher : &g

Re: [Oorexx-devel] recent MacOS 10.15.2 and Xcode 'misses stdlib.h' build error

On 05.02.2020 17:19, P.O. Jonsson wrote: > Renés question made reconsider; I realized that the Disk Utility (diskutil) > can indeed be scripted > on the Mac, as can most things I needed to make an installer. > > I have prepared a dmg installer that looks pretty much like a „real“ > DragnDrop MacO

Re: [Oorexx-devel] Old Process for Building the ooRexx Documentation (Publican)

On 01.02.2020 19:49, Gil Barmwater wrote: > > I agree that color coding the examples would be nice but I believe that is a > "feature" of DocBook > that may require a different transform program. This link > describes how to > do someth

Re: [Oorexx-devel] Old Process for Building the ooRexx Documentation (Publican)

On 01.02.2020 20:46, Jean Louis Faucher wrote: > The notes and tools in my GitHub repository are for the old format of > documentation, before the > work made by David to switch to Publican. > Nothing you can reuse for the current version. :( Maybe, once the new process of creating the documenta

Re: [Oorexx-devel] Old Process for Building the ooRexx Documentation (Publican)

ely after > the tag solves the problem. There were several examples in the "common" files > which I fixed that > way along with the DTD changes. > Thanks to this description I wrote [1] below. Keep up the great work! Best regards ---rony > On 2/1/2020 8:59 AM, Ron

Re: [Oorexx-devel] Old Process for Building the ooRexx Documentation (Publican)

On 31.01.2020 22:09, P.O. Jonsson wrote: > many thanks for your feedback, I read your thread and I think you gave me > just the hint I needed > to inject Erichs cleaning script in to my build toolchain (it works slightly > different to Erichs > setup). I will let you know if it worked. > > When I

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

ect there will be issues with some of them. E.g. as P.O. noted in a > different thread and > mentioned by Erich as well, the Java heap space needs to be increased for > some of our documents. I > do not know how to do that but it was not necessary for the rxmath > book. Any other iss

Re: [Oorexx-devel] Old Process for Building the ooRexx Documentation (Publican)

Dear P.O., On 29.01.2020 17:20, P.O. Jonsson wrote: > Dear all, > > I am starting a new thread so as not to pollute Gil´s thread. This is just > until we have a > permanent solution. > > I now have a working installation on Windows 7 that can reliably build the > documentation, both as > pdf an

[Oorexx-devel] Ad IPv6 support

In the meantime maybe if there are free resources it would be great if IPv6 support gets added (e.g. ) to ooRexx. Not only has IPv6 become more and more important, some companies like Apple mandate its support in order to be listed in their

Re: [Oorexx-devel] Preparing the release version ...

2007, 2006, 2005). It would be great and assuring, if it was possible to get back to yearly release for ooRexx! On 15.11.2018 15:17, Rony G. Flatscher wrote: > This past year there have been many remarkable changes (performance > improvements from 1.2x to 20x > times, memory managem

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

Hi Gil, any chance for your next posting to get an idea of what you have done and come up to? Maybe with a bird eyes's view how you now would suggest to create the documentation according to your analysis, tests? Also, would you have already suggestions for the software to use, e.g. xsltproc (

Re: [Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

Gil: that is really a *great* achievement, thank you very much for all of your efforts! This is really great for the ooRexx project! Whenever you want "nit-picking" feedback, please let us know, the overall documentation is looking very professional and attractive already! Also, whenever you a

Re: [Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

Wow, that is *fantastic* news!! Also, looking at your readme.pdf it looks terrific IMHO! Very curious what you have come up with to be able to generate the ooRexx 5.0 documentation yourself  (and also about the questions that you will pose in order to learn about the current problems from them

[Oorexx-devel] New beta of BSF4ooRexx "20191126"

Hi there, there is a new version of BSF4ooRexx available at : * the version for Windows and Linux is named: ; after unzipping change into "bsf4rexx/installation/{your-opsys}" and run "install.{cmd|sh} * the MacOSX version

Re: [Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

Hi P.O., great that you are also looking into this! On 03.11.2019 23:22, P.O. Jonsson wrote: > Hi Gil, nice to hear from you. > > I am shadowing your efforts on the Mac, I assume you are on Windows. > > I could install Pandoc and BasicTex (Latex on Mac) using Homebrew and render > the initial te

Re: [Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

On 03.11.2019 18:32, Gil Barmwater wrote: > > Second update: attempted to use Chocolatey to install MikTex but got errors > doing so. I used > Chocolatey to uninstall MikTex and went to the website for the program > instead and downloaded the > package - its big, 201MB. Ran the installer which to

Re: [Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

Good luck!! Rony G. Flatscher (mobil/e) > Am 02.11.2019 um 19:42 schrieb Gil Barmwater : > >  > Update: I've now been able to 1)install Chocolatey, 2)use Chocolatey to > install Pandoc, and 3) test that Pandoc works with basic files (as listed on > their website - htt

Re: [Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

https://docbook.org/ seems to have links to the dtd/xsd definitions, also a link to tools they seem to suggest/endorse. —-rony Rony G. Flatscher (mobil/e) > Am 01.11.2019 um 16:51 schrieb Jeremy Nicoll : > > On Fri, 1 Nov 2019, at 14:00, Gil Barmwater wrote: >> >> Spen

[Oorexx-devel] Questions ad generating the documentation (publican, pandoc)

Following the communication in the past it seems that currently a special publican setup on Windows is necessary. Is there any "cheat-sheet"/"todo-list" documentation available on the Internet (did not find anything on the ooRexx wiki )? Would public

<    4   5   6   7   8   9   10   11   12   13   >