|Re: [asciidoc-lang-dev] Extension hooks in Asciidoc|
We use AsciidoctorJ. Spring is written in Java, so we prefer other things that are written in Java. Part of the team's excitement about the Working Group is that there will be a Java implementation.
That shouldn't matter, though. IMO, the Asciidoc specification should provide extension mechanisms regardless of the language that implements the specification. In other words, I would like the specification to call out extension mechanisms. The XSLT specification does so, for example: https://www.w3.org/TR/xslt-30/#extension (and did so in its previous versions, though each one did it differently).
From: asciidoc-lang-dev <asciidoc-lang-dev-bounces@xxxxxxxxxxx> on behalf of David Jencks <david.a.jencks@xxxxxxxxx>
Sent: Friday, March 12, 2021 3:30 PM
To: AsciiDoc developer discussions <asciidoc-lang-dev@xxxxxxxxxxx>
Subject: Re: [asciidoc-lang-dev] Extension hooks in Asciidoc
Looking at the repo, it appears to be a mix of ruby and java code. Which “dialect(s)” of Asciidoctor are you (Spring) using, called how?
I think it’s possible that there are existing more efficient ways to implement some extensions in current Asciidoctor, such as using the template converter system for your converter extension.
Other than the possible difficulty of implementing string manipulation in java, and relating java extensions to a ruby backend, I’m curious what specifically you would like to be easier.
I always like looking at what people do to extend Asciidoctor :-)
Back to the top