George,
Welcome!
I'm happy to say that we have the first part, parsing AsciiDoc into an AST. However, we don't yet have the second part, which is writing the result back to disk.
Although we don't have that yet, there are partial pathways to get there. For instance, Schalk has been working on creating a converter for Leanpub, which transforms AsciiDoc into Leanpub Markdown {1}. You can imagine that creating a converter to generate AsciiDoc output isn't much more of a stretch.
We've also been talking about a document builder API as part of AsciidoctorJ. Robert Winkler originally brought it up since he needed something similar for his swagger2markup project {2}. For now, he has created that builder in that project, so there is a starting point for generating AsciiDoc content.
Eventually, I think we want Asciidoctor core to provide a built-in converter for AsciiDoc {3}. This would allow Asciidoctor to parse AsciiDoc and write it back out again. That allows you to use any of the extension mechanism, including a Treeprocessor, to manipulate the document content in between.
The short answer is, we want to be able to do it, but right now we only have “lines in the water”.
-Dan
Locked
Jun 18, 2015; 7:44pm
