Prawn::Errors::CannotFiterror I got from
asciidoctor-pdf... and I couldn't stop reading :-) I have a question for you guys: I have just joined a new company and I'm trying to convince them that Asciidoc is the right way to keep all our documentation and knowledge base and it can produce beautiful HTML and PDF from a single source. But after reading this forum (especially remarks from @mojavelinux from mid-2019) I started worrying about the state of the
asciidoctor-pdfproject... So tell me please: should we use it now or there is a more stable (maybe longer) way (via DocBook, LaTex, etc.)? Sorry for such a naive question... Thanks!
pandocto convert a sample document from the .DOCX source to Asciidoc and it needed only a couple of tweaks to look pretty in Asciidoc -> PDF . BTW, one of the tweaks was adding an
abefore table cells that contained images. Thanks again, @mojavelinux -- I found your answer from 2013 on the Asciidoctor forum.
npm, which allows documents to use
bytefieldblocks to render byte field diagrams in a style inspired by the LaTeX bytefield package, but with a more concise, Clojure-based domain specific language. (And it being Clojure, you can build on my offerings with your own definitions and functions.) It’s in the process of being merged into asciidoctor-diagram, but you can also use it independently.
yes, though keep in mind tables have a very quirky model that was designed with conversion in mind. so it reuiqres some patience.
Is there any kind of guide to how Opal works and perhaps why it needs to generate such odd looking code?
(for asciidoctor.js 1.5.9/Antora) In an extension, I can create a cell for an existing table with this code:
const cellClass = Opal.const_get_qualified(table.__proto__.$$class, 'Cell') const cell = cellClass.$new(col, contentText)
This gives an eslint warning about
__proto__. Is there a shorter/better way to do this? Will this be easier with asciidoctor.js 2.x?