Spent some time trying to get my head around our documentation process and here is where I'm at. We use DocBook for all our documentation which consist of XML which contains the book content and XSL that describes the format.?? I've found the .xml files in the SVN repository but don't know where the .xsl files are. Publican takes the .xml and the .xsl and produces FO output. FOP takes the FO output and creates a PDF. I'm not sure how we get the HTML documents created. It looks like Pandoc takes the .xml and .xsl files and produces TeX output and then converts that to a PDF. For HTML, it appears to be able to go directly from the DocBook files to HTML.

Can someone confirm I understand this correctly and explain where?? the XSL comes from and how we get HTML documents under the current process??? Thanks.

On 10/30/2019 7:48 PM, Gil Barmwater wrote:

OK, did some reading at the suggested link and discovered a recommendation to use Chocolatey to install pandoc since it can also install other packages that pandoc might need like LaTex. That is the path I plan to pursue unless someone raises a red flag. Anyone have any experience with that piece of software?

On 10/30/2019 2:27 PM, Rick McGuire wrote:


On Wed, Oct 30, 2019 at 1:47 PM Gil Barmwater <gbarmwa...@alum.rpi.edu <mailto:gbarmwa...@alum.rpi.edu>> wrote:

    OK, I'm going to show my ignorance here but it seems someone
    should at least explore replacing the unsupported/broken publican
    with pandoc.?? I've done some cursory searching and reading about
    pandoc and it seems to be a "good" tool; i.e. it has many
    conversion options and seems to have a reasonably sized base of
    users.?? So it looks like it can take an input file in DocBook
    format - that is what we are using , right? - and produce both
    HTML and PDF output formats.?? But it looks like the PDF option
    needs another tool, e.g.LaTex.?? Is that what we use or is FOP or
    something else our PDF-maker??? As I said, I'm really ignorant
    here but I'm willing to slog through it if I can get some
    guidance.?? What should be the first step?

We are currently using FOP for our PDF-maker, which is the component that has been locking us in to our current set. What to use really comes down to which converter produces the best output. LaTex appears to be the default, so that's a good starting point. Beyond that, I would suggest starting here: https://pandoc.org/getting-started.html, then see if there are places you can get questions answered. I'm afraid we're all going to be at the same starting point on this.

Rick

    Gil B.

    On 10/30/2019 12:34 PM, Erich Steinb??ck wrote:

        I'm not really that comfortable with relying on an old
        version of tools that don't really have any support any more

    The issue has become even more serious since switching over to
    Windows 10.
    All ooRexx docs still build (with slightly less appealing fonts)
    except for rexxref. Tested on two Win 10 machines, any rexxref
    build fails with a c0000005 exception about 99% of the time, but
    eventually successfully builds in 1 out of a 100 tries.?? A real
    pain.

    Although publican is an exe we still might be able to figure out
    where the crash occurs (and maybe fix it), because publican.exe
    really is a PAR-packed ZIP file of (Strawberry) Perl scripts and
    native libraries.?? The scripts can be extracted with a simple
    unzip and it might be possible to run them in Perl debug mode,
    figure out where it breaks and replace the culprit with a newer
    version (or bring all stuff to the latest Perl version).

    I tried a bunch of things but with no success yet.

    On Wed, Oct 30, 2019 at 1:56 PM Rick McGuire
    <object.r...@gmail.com <mailto:object.r...@gmail.com>> wrote:

        There was a long discussion on how to get this set up that
        took place on this list back in January of this year. The
        net of this discussion was that while it was possible to
        build the docs on linux, the results were not as good as the
        version built on Windows. Getting a working setup on Windows
        required a good bit of manual tweaking and installing very
        specific versions of publican. I believe Erich made a
        snapshot of his build tools available for download on
        Sourceforge.??

        I don't know if anybody has every tried pandoc. I would be
        nice if it did work, since I'm not really that comfortable
        with relying on an old version of tools that don't really
        have any support any more.??

        Rick

        On Wed, Oct 30, 2019 at 8:22 AM Rony G. Flatscher
        <rony.flatsc...@wu.ac.at <mailto:rony.flatsc...@wu.ac.at>>
        wrote:

            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
            <https://sourceforge.net/p/oorexx/wiki/Home/>)?

            Would publican (https://pkgs.org/download/publican) for
            Linux be able to process the ooRexx
            documentation? If not, would anyone know of the reason(s)?

            ---

            Has anyone ever tried to process the ooRexx
            documentation with "pandoc" (https://pandoc.org/), which
            would be available for all major platforms for free?

            ---rony




            _______________________________________________
            Oorexx-devel mailing list
            Oorexx-devel@lists.sourceforge.net
            <mailto:Oorexx-devel@lists.sourceforge.net>
            https://lists.sourceforge.net/lists/listinfo/oorexx-devel

        _______________________________________________
        Oorexx-devel mailing list
        Oorexx-devel@lists.sourceforge.net
        <mailto:Oorexx-devel@lists.sourceforge.net>
        https://lists.sourceforge.net/lists/listinfo/oorexx-devel



    _______________________________________________
    Oorexx-devel mailing list
    Oorexx-devel@lists.sourceforge.net  
<mailto:Oorexx-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/oorexx-devel

-- Gil Barmwater

    _______________________________________________
    Oorexx-devel mailing list
    Oorexx-devel@lists.sourceforge.net
    <mailto:Oorexx-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/oorexx-devel



_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater

--
Gil Barmwater

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to