Thinking that doing HTML first would be easier as it would not involve a
second step - LaTex to PDF with MiKTex - I tried that next.
Unfortunately, I get an error message and an empty document. Reading the
article pointed to by P.O. I found the statement
"Included Files
If you have files that are xincluded in a DocBook file, pandoc will not
include them. You can solve this problem by first processing your XML
file using xmllint." And, looking at the rxmath.xml file, I see (mostly)
statements containing <xi:include. So it would seem that another
step/tool is needed to "combine" the book parts into a single file
before Pandoc can process them. <sigh>
P.O. also reported a problem with getting the "railroad diagrams", i.e.
the .svg files, into the PDF that he created which will require further
investigation. But looking at his results, I note that much more than
the diagrams is missing. This may be due to the "include" problem noted
earlier or something else. The article about using Pandoc with Docbook
is, after all, more than 5 years old so surely Pandoc has evolved in the
meantime.
One more point from the article bears noting. "The DocBook style sheets
do a very good job of transforming DocBook to HTML, PDF, EPUB and other
output formats so DocBook users will principally be interested in
exporting to other formats and in converting other formats to DocBook."
So maybe Pandoc is NOT the tool we should be investigating for
generating our documents. I will go back to docbook.org and do some more
reading before proceeding any further with Pandoc.
As a side note, my editor of choice is SlickEdit which supports docbook
as a document type. When I open the rxmath.xml and tell the editor that
it is a docbook document, I get multiple error messages referencing the
xi:include statements. I don't know if that is due to not having an
editor "project" set up or if the docbook statements are invalid in some
way. More to investigate...
On 11/4/2019 7:39 AM, Rony G. Flatscher wrote:
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 took a few minutes and then
it said it needed to
install updates in the background.
Wow, 201MB for TeX! (Thirty years ago TeX did not need even a whole diskette.)
Eventually I was able to use Pandoc to create a PDF per the tutorial. I also
used Pandoc to
convert a large HTML file I had to a PDF. So the tools appear to be in place
and operational. Next
step is to take a small ooRexx docbook and create an HTML version.
Have you managed to create a HTML rendering? If so, how does it look like
compared to the current
documentation?
---rony
_______________________________________________
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
