We crossed cyber paths -
https://github.com/asciidoctor/asciidoclet/issues/90
On Sun, Jul 15, 2018 at 8:34 AM Guillaume Smet
wrote:
> On Sun, Jul 15, 2018 at 3:16 PM Steve Ebersole
> wrote:
>
>> Oh, you mean it does not like HTML markup? Not sure, we should ask Dan
>> and friends what is expec
On Sun, Jul 15, 2018 at 3:16 PM Steve Ebersole wrote:
> Oh, you mean it does not like HTML markup? Not sure, we should ask Dan
> and friends what is expected there from asciidoclet - I'm not sure
>
Yes, exactly.
HTML output is rendered escaped, which is expected if it considers all our
Javadoc
Oh, you mean it does not like HTML markup? Not sure, we should ask Dan and
friends what is expected there from asciidoclet - I'm not sure
On Sun, Jul 15, 2018 at 8:13 AM Guillaume Smet
wrote:
> No I'm talking about all the markup that appears in the output. What I
> pasted is not the source, it
No I'm talking about all the markup that appears in the output. What I
pasted is not the source, it's the output you get in your Javadoc (with the
, the and so on).
The cross references are indeed OK.
On Sun, Jul 15, 2018 at 3:06 PM Steve Ebersole wrote:
> You mean the lack of rendering Javdoc
You mean the lack of rendering Javdoc cross-references ({@link ...})?
Otherwise, I am not sure what exactly you are getting at.
Asciidoclet is supposed to handle Javdoc cross-references - if it is not,
that would be a bug in asciidoclet
On Sun, Jul 15, 2018 at 7:58 AM Guillaume Smet
wrote:
> On
On Sun, Jul 15, 2018 at 2:13 AM Steve Ebersole wrote:
> We have ported things from 6 back to 5.3 so I cannot say definitively that
> absolutely no javadoc in 5.3 uses asciidoc(tor).
>
> But feel free to disable it.
>
I just tried the opposite and enable Asciidoclet for the aggregated javadoc
to
We have ported things from 6 back to 5.3 so I cannot say definitively that
absolutely no javadoc in 5.3 uses asciidoc(tor).
But feel free to disable it.
On Sat, Jul 14, 2018, 1:45 PM Guillaume Smet
wrote:
> Hi,
>
> Are we using Asciidoc javadoc in the current tree (i.e. not 6)?
>
> With JDK 11