<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 9 Sep 2014, at 23:19, Ondrej Zizka <<a href="mailto:ozizka@redhat.com">ozizka@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>On 9.9.2014 12:39, Pete Muir wrote:<br><blockquote type="cite">The big advantages of asciidoc are:<br><br>* more comprehensive markup (e.g. tables, definition lists are supported as standard)<br></blockquote>That's nice, but we have 0 tables and just one DL in our docs :)<br></div></blockquote><div><br></div><div>Understood, this is largely about what you need out of your language. For me tables are essential, as are admonitions and callouts.</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite">* generation of pdf and epub is part of the standard toolchain<br><br>Markdown is great for short docs, but I quickly ran in to the limitations when building more complex documents.<br></blockquote>Same as above - will we have more complex docs?<br></div></blockquote><div><br></div><div>I think it’s very likely that we will have what I would class a “complex” document for Windup - yes.</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Will we produce PDF? Will users expect a PDF document?</div></blockquote><div><br></div><div>It’s a very commonly requested item. A sizeable majority tend to prefer this.</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> I don't know<span class="Apple-converted-space"> </span><br>their customs, but personally I never use PDF docs, except when<span class="Apple-converted-space"> </span><br>printing, which I never did for anything except Java EE specs /<span class="Apple-converted-space"> </span><br>tutorials and Spring.<br><br>How about keeping MarkDown for short and simple pages, and AsciiDoc<span class="Apple-converted-space"> </span><br>optionally when needed? One more syntax should not matter.<br></div></blockquote><div><br></div><div>I would use asciidoc for anything that is going to go in to the docs. For other things, such as READMEs use markdown.</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite">GitHub’s support for asciidoc wasn’t great to start with, but I think the fixed it more recently. Before you abandon it, point me at the problems, I can take a quick look.<br><br>I prefer asciidoc links as you just do link:http://<a href="http://redhat.com/">redhat.com</a>[Red Hat’s website]. I find this much easier to remember than the weird []() syntax in markdown.<br></blockquote>How about this nice paragraph<br><br>A<span class="Apple-converted-space"> </span><br>link:https://<a href="http://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12[way]">maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12[way]</a><span class="Apple-converted-space"> </span><br>to<br>link:https://<a href="http://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083[Poland]">www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083[Poland]</a>.<br><br>And now compare with:<br><br>A<span class="Apple-converted-space"> </span><br>"way":<a href="https://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12">https://maps.google.com/maps?saddr=Hn%C4%9Bvkovsk%C3%A9ho%2FRoute+41&daddr=Kr%C3%B3lewska&hl=en&ie=UTF8&sll=52.229692,21.006203&sspn=0.214911,0.385551&geocode=FW5S7gId0qf9AA%3BFYYeHQMdx6BAAQ&t=h&mra=mift&mrsp=1&sz=12&z=12</a><br>to<span class="Apple-converted-space"> </span><br>"Poland":<a href="https://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083">https://www.google.cz/search?q=poland&client=ubuntu&hs=1q&channel=fs&source=lnms&tbm=isch&sa=X&ei=MHwPVM_jLs7EPJfCgbgL&ved=0CAkQ_AUoAg&biw=1504&bih=1083</a><br><br>I personally prefer the first. And the {} attributes syntax doesn't make<span class="Apple-converted-space"> </span><br>things simpler.<br></div></blockquote><div><br></div><div>I prefer the first approach too. So a good argument for AsciiDoc then.</div><div><br></div><div>Note that the markdown syntax you quote is a github extension I think. This is part of the reason I would pick AsciiDoc - all these things are standard, rather than implementation specific extensions.</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>my2c.<br>But as I said - except for this and few other things, AsciiDoc may be<span class="Apple-converted-space"> </span><br>better, potentially.<br><br>Ondra<br><br><blockquote type="cite">On 9 Sep 2014, at 01:23, Sande Gilda <<a href="mailto:sgilda@redhat.com">sgilda@redhat.com</a>> wrote:<br><br><blockquote type="cite">I'll change everything back to Markdown later this week. Ondra, in the<br>meantime, you can work in Markdown.<br><br>On 09/08/2014 08:12 PM, Brad Davis wrote:<br><blockquote type="cite">I personally leveraged Markdown because it worked. Asciidoc a while ago did not. I noticed when things moved to Asciidoc, the images in the docs broke.<br><br>Brad Davis<br>Red Hat Consulting<br>Email: <a href="mailto:bdavis@redhat.com">bdavis@redhat.com</a> | c: 980.226.7865 | <a href="http://www.redhat.com">http://www.redhat.com</a><br><br><br>----- Original Message -----<br>From: "Ondrej Zizka" <<a href="mailto:ozizka@redhat.com">ozizka@redhat.com</a>><br>To: "Sande Gilda" <<a href="mailto:sgilda@redhat.com">sgilda@redhat.com</a>>, "Windup-dev List" <<a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a>><br>Sent: Monday, September 8, 2014 7:58:20 PM<br>Subject: Re: [windup-dev] Asciidoc - lists<br><br>For the record: I don't strongly prefer either, only that I only touched<br>few things in AsciiDoc, and:<br> 1) certain constructs are quite less readable -> editable in the<br>source text (e.g. links)<br> 2) the render results are not satisfactory - things like a bold text<br>in a lists are not properly implemented on whatever GitHub uses.<br><br>Ondra<br><br><br>On 9.9.2014 01:17, Sande Gilda wrote:<br><blockquote type="cite">Hi all,<br><br>Ondra asked me about the advantages of AsciiDoc over Markdown. I<br>really don't know, but I do remember Pete saying AsciiDoc would be<br>better for the quickstart README files long ago. And I believe Drupal,<br>the new host for documentation, supports AsciiDoc.<br><br>TBH, I don't feel strongly about sticking with AsciiDoc. If no one can<br>come up with a good reason for sticking with it, I'm fine with going<br>back to Markdown if it's easier for everyone.<br><br>So, AsciiDoc advocates, please speak up now.<br><br>Thanks,<br>Sande<br><br>On 09/08/2014 06:29 PM, Sande Gilda wrote:<br><blockquote type="cite">Hi Ondra,<br><br>You're asking me? ;-)<br><br>I'm totally new to asciidoc. I'll research it and see what I can find<br>out.<br><br>Thanks,<br>Sande<br><br>On 09/08/2014 06:13 PM, Ondrej Zizka wrote:<br><blockquote type="cite">Hi Sande,<br><br>is there any way to prevent asciidoc put <p> to each <li>? Makes the<br>list tall and breaks the whole page layout.<br><br>Thanks,<br>Ondra<br></blockquote></blockquote></blockquote>_______________________________________________<br>windup-dev mailing list<br><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/windup-dev<br></blockquote>_______________________________________________<br>windup-dev mailing list<br><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/windup-dev<br></blockquote><br>_______________________________________________<br>windup-dev mailing list<br><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/windup-dev">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br></blockquote><br>_______________________________________________<br>windup-dev mailing list<br><a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/windup-dev">https://lists.jboss.org/mailman/listinfo/windup-dev</a></div></blockquote></div><br></body></html>