Xavier Coulon

yes, reusing the Asciidoctor CSS would be an option, but I thought we could have something a little more modern, and to be honest I also opened this issue to...

yes, as I said in https://github.com/bytesparadise/libasciidoc/issues/635#issuecomment-648388621, support for table is pretty basic for now :(

This request is more or less related to the support for custom substitutions. One of them is "special characters" and it's supposed to convert characters such as `` and `&`...

> So, I really think the parsed document structure should contain literal values -- not entities. For example, we can use " for a quote. The fact that " needs...

> And yes, I think we should consider using html/template in the backend. I can start looking more closely at that if you agree. We used to use them to...

well, anyways, given that we have the parser on the one hand and multiple renderers on the other hand, it's likely that we can't (and should not) perform the "special...

> I hope what you mean is that we convert things like '>' to entities in the _rendering_ stage, and leave them unmolested during parsing. yes, that's what I meant,...

@gdamore I believe that #734 fixes this issue.

One thing to keep in mind is that Asciidoctor renders the callouts in such a way that a reader can copy/paste an entire block of code _without_ the callout references...

hello @gdamore 👋 This is awesome news if you want to work on an epub3 renderer! And I appreciate very much your feedback about the library, although, I think there...