Hi Gil, Looks good to me, but I'm not sure what to look for. Any chance of a doc with railroad diagrams?
Jon On Wed, 11 Dec 2019, 19:00 Gil Barmwater, <[email protected]> wrote: > Thanks for the feedback Rony. Anyone else have any comments? If not, I > will start posting comments on the issues I have found shortly. My goal is > to develop a package containing the tools that anyone can download and > install that will allow them to build our docs on Windows 10 from a fresh > checkout from SourceForge with minimal changes to those files. > On 12/10/2019 12:45 PM, Rony G. Flatscher wrote: > > 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 and become able > to build the ooRexx documentation in the near future and in a future-safe > way)! > > Kudos! > > ---rony > > On 10.12.2019 18:17, Gil Barmwater wrote: > > I know it has been over a month since I posted the note below but I now > have a lot of progress to report! I have obtained the tools needed to build > our docs - they are open source and seem well supported - and have > successfully built one document using them on Windows 10. There are no > dependencies on Publican other than three files I chose to retain to > simplify the transition. Installing and using the tools was pretty painless > but in doing so I uncovered a number of issues with our documents, most of > which are due to our use of Publican and what it does "under the covers". > Rather than turning this email into a "book", I will send separate notes on > each issue and the changes needed in order to use the new tools. In the > meantime, here <https://www.dropbox.com/s/n7p09b6zm0vghqc/readme.pdf?dl=0> > is a link to a file in my Dropbox for the readme.pdf that I built. Once the > link opens in your browser, you can click on the ... icon on the right > which will open a menu that will allow you to download the file. If you > then compare it to the readme.pdf that is in the docs folder of your 5.0.0 > ooRexx installation or the Files section on SourceForge, you will see it is > (almost) identical. The differences are 1) the text has been updated in > section 2.2, 2) the Copyright dates on the first page now show -2019, 3) > the flow of the text in some sections is slightly different, in some cases > causing text to flow to the next page, and 4) the Table of Contents has > more levels listed. I did not feel that either of the last two items were > worth pursuing. Let me know what you think after you've had a look. > > Gil B. > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > Just so everyone doesn't think I've abandoned this effort, I am pursuing > another approach to building the docs. You can expect an update when I've > made some more progress. > > On 11/4/2019 4:16 PM, Gil Barmwater wrote: > > ?I will go back to docbook.org and do some more reading before proceeding > any further with Pandoc. > > -- > Gil Barmwater > > > > > _______________________________________________ > Oorexx-devel mailing > [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 >
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
