For the record: I don't strongly prefer either, only that I only touched
few things in AsciiDoc, and:
1) certain constructs are quite less readable -> editable in the
source text (e.g. links)
2) the render results are not satisfactory - things like a bold text
in a lists are not properly implemented on whatever GitHub uses.
Ondra
On 9.9.2014 01:17, Sande Gilda wrote:
Hi all,
Ondra asked me about the advantages of AsciiDoc over Markdown. I
really don't know, but I do remember Pete saying AsciiDoc would be
better for the quickstart README files long ago. And I believe Drupal,
the new host for documentation, supports AsciiDoc.
TBH, I don't feel strongly about sticking with AsciiDoc. If no one can
come up with a good reason for sticking with it, I'm fine with going
back to Markdown if it's easier for everyone.
So, AsciiDoc advocates, please speak up now.
Thanks,
Sande
On 09/08/2014 06:29 PM, Sande Gilda wrote:
> Hi Ondra,
>
> You're asking me? ;-)
>
> I'm totally new to asciidoc. I'll research it and see what I can find
> out.
>
> Thanks,
> Sande
>
> On 09/08/2014 06:13 PM, Ondrej Zizka wrote:
>> Hi Sande,
>>
>> is there any way to prevent asciidoc put <p> to each <li>? Makes the
>> list tall and breaks the whole page layout.
>>
>> Thanks,
>> Ondra
>