Script to build spec pdfs

[joseph-mueller]

The script has in-line documentation. Generates reasonable pdf output with proper links back to github.

For now, presume the script will be used manually, could be incorporated into actions and automated.

[joseph-mueller]

Ultimately, although the content basically works, was unable to get the generated PDF to have the tidy appearance. Things like choosing a good font, getting internal links and external links colored properly etc.

Difficulty seems to be in the capability of the pandoc containers available. Did not want to require the person generating PDF have a full pandoc and LaTex installation, so recommendation is to generate PDF using tools integrated in VS Code for now.

[alejandro5042]

Difficulty seems to be in the capability of the pandoc containers available. Did not want to require the person generating PDF have a full pandoc and LaTex installation, so recommendation is to generate PDF using tools integrated in VS Code for now.

By containers, do you mean Docker containers?

If we were to run the script inside a Docker container with a full install of pandoc/Latex, would that resolve the issue and generate great looking specs?

Is the issue just requiring the user to have a container installed?

(Note: Running containers is a pretty typical SW workflow these days, so I think it would be easy to document.)

[joseph-mueller]

Yes, I was referring to docker containers. None of the available images I found formatted reasonably well. I suppose we need to create a full image with pandoc,pdf stuff,and a pretty full LaTex. But need to get it posted where the build can easily acquire it....

…

-Joe

________________________________ From: Alejandro Barreto ***@***.***> Sent: Thursday, February 27, 2025 2:01:41 AM To: IviFoundation/IviDrivers ***@***.***> Cc: Joe Mueller ***@***.***>; Author ***@***.***> Subject: Re: [IviFoundation/IviDrivers] Script to build spec pdfs (PR #12) Difficulty seems to be in the capability of the pandoc containers available. Did not want to require the person generating PDF have a full pandoc and LaTex installation, so recommendation is to generate PDF using tools integrated in VS Code for now. By containers, do you mean Docker containers? If we were to run the script inside a Docker container with a full install of pandoc/Latex, would that resolve the issue and generate great looking specs? Is the issue just requiring the user to have a container installed? (Note: Running containers is a pretty typical SW workflow these days, so I think it would be easy to document.) — Reply to this email directly, view it on GitHub<#12 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ6LLCLE3ENSZPKWAYEB2PT2R3H7LAVCNFSM6AAAAABWP2DAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBXGMYTKMZRG4>. You are receiving this because you authored the thread.Message ID: ***@***.***> [alejandro5042]alejandro5042 left a comment (IviFoundation/IviDrivers#12)<#12 (comment)> Difficulty seems to be in the capability of the pandoc containers available. Did not want to require the person generating PDF have a full pandoc and LaTex installation, so recommendation is to generate PDF using tools integrated in VS Code for now. By containers, do you mean Docker containers? If we were to run the script inside a Docker container with a full install of pandoc/Latex, would that resolve the issue and generate great looking specs? Is the issue just requiring the user to have a container installed? (Note: Running containers is a pretty typical SW workflow these days, so I think it would be easy to document.) — Reply to this email directly, view it on GitHub<#12 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ6LLCLE3ENSZPKWAYEB2PT2R3H7LAVCNFSM6AAAAABWP2DAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBXGMYTKMZRG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>