feat: Generate PDF/HTML on release event with GitHub Actions

[et84121]

this feature will trigger github action to generating book on github released event and the book will be uploaded to release assets

Github Page Setting

repo owner should set repo setting like this pic

[jserv]

Thanks for the patch! I really appreciate that. However, I could not recognize the source code listing (with indention and syntax highlighting) in generated HTML with pandoc. Did you suffer from the same problem?

[jserv]

I could not recognize the source code listing (with indention and syntax highlighting) in generated HTML with pandoc.

The corresponding GitHub Pages I am addressing: https://jserv.github.io/lkmpg/
Check the section "Examples" and no real LKM source code was shown.

[jserv]

The generated PDF was malformed as well. See https://jserv.github.io/lkmpg/lkmpg.pdf

[et84121]

I only use the default setting to generate files.
Maybe pandoc needs more parameters.
I'll check it out.

[et84121]

After investigation, that's because pandoc can't handle latex's external dependencies.
Perhaps another solution is embedding PDF file generated by pdflatex on the website

That's a harmless info message. Pandoc will only try to parse xcolor.sty if it's in the working directory (or --resource-path). That's usually what you want; pandoc usually can't handle the low-level tex in these sty files.
Originally posted by @jgm in jgm/pandoc#5730 (comment)

[et84121]

I also tried to use other tools to generate HTML files, and this tool can successfully handle external dependencies, but it did not work for the "Undefined control sequence" reasons.

• https://github.com/michal-h21/make4ht

[jserv]

I also tried to use other tools to generate HTML files, and this tool can successfully handle external dependencies, but it did not work for the "Undefined control sequence" reasons.

• https://github.com/michal-h21/make4ht

Let's consolidate #20 before working on GitHub Actions/Pages.

[jserv]

Close in favor of #32