I posted it to AsciiDoc. But they don't share my opinion that <p> in
<li> is a wrong idea.
https://groups.google.com/forum/#!topic/asciidoc/BF9HlACuNjE
They have an unfortunate mix of "DocBook legacy" and forward compatibility.
But it's a bit configurable. Dan wrote:
It's also pretty each to change by hacking the html5.conf file:
----
[paragraph]
{title?<div class="title">{title}</div>}
<p class="paragraph{role? {role}}{unbreakable-option? unbreakable}"{id?
id="{id}"}>
|
</p>
----
We could ask GitHub to change that for li I guess.
Or, as I suggested earlier, find out if GitHub allows to apply
per-project CSS.
Ondra
On 11.9.2014 22:23, Sande Gilda wrote:
This is interesting. GitHub uses Asciidoctor to render the asciidoc
files!
Ondra, where did you report this issue? If you didn't report it to
Asciidoctor, I will.
-------- Original Message --------
Subject: Re: GitHub problem rendering AsciiDoc lists
Date: Thu, 11 Sep 2014 10:08:00 -0700
From: Jess Hosman (GitHub Staff) <support(a)github.com>
To: Sande Gilda <sgilda(a)redhat.com>
Hi Sande,
Thanks for your patience. After some digging, it looks like we use the third party tool
Asciidoctor [1] for the conversion, which is where the extra `<p>` tags are coming
from. I'd recommend opening an issue in the Asciidoctor repo about this. Once changes
are made there, we should be able to pull them into GitHub.
Cheers,
Jess
[
1]:https://github.com/asciidoctor/asciidoctor
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev