> Now that asciidoctor includes support for DocBook 5, it seems close to something we can use.
> One thing I do not see is support for olink
Asciidoctor introduces a syntax to address cross-document references. We could wire this to olink in the DocBook backend. If necessary, we can enhance the feature if necessary to cover all the requirements.
The first thing to look at it is whether the AsciiDoc syntax is capable of capturing all the necessary information. Changing the output of the converter to emit olink is a separate and very trivial task.
On Tue, Dec 30, 2014 at 9:11 AM, MJang [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Now that asciidoctor includes support for DocBook 5, it seems close to something we can use.
We can definitely support this. The converter knows when it is handling an inter-document cross reference, so we can simply add the necessary attribute in this case to ensure it opens in a new tab. Let's graduate this to an issue report and I'll schedule it for 1.5.3.
On Mon, Jan 5, 2015 at 10:50 AM, MJang [via Asciidoctor :: Discussion] <[hidden email]> wrote:
I've checked your syntax doc on cross-document references, and I can see that it's close. What I'm hoping for is to "drop in" processed adoc -> Docbook XML files into our doc trunk.