<div dir="ltr">I forgot the mention the craziness with the *significant trailing whitespace*.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 5, 2013 at 9:49 PM, <a href="mailto:dag.odenhall@gmail.com">dag.odenhall@gmail.com</a> <span dir="ltr"><<a href="mailto:dag.odenhall@gmail.com" target="_blank">dag.odenhall@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div>Personally I think Markdown sucks, although perhaps less than Haddock markup.<br>
<br></div>Still:<br><br></div>* No document meta data<br></div>* No code block meta data like language for syntax highlighting<br>
</div>* No tables<br></div><div>* No footnotes<br></div>* HTML fallback is insecure<br></div>* Confusing syntax (is it []() or ()[] for links?)<br></div>* Syntax that gets in the way (maybe I don't want *stars* emphasized)<br>
</div>* Above point leads to non-standard dialects like "GitHub Markdown" (no, GitHub doesn't use markdown)<br></div>* Not extensible, leading to even more non-standard hacks and work-arounds (GitHub Markdown, Pandoc Markdown, other Markdown libraries have their own incompatible extensions)<br>
</div><div>* Not well suited for web input (e.g. four-space indentation for code blocks), although not that important for Haddock<br></div><div><br></div>An important thing to note here is that no, Markdown has *not* won because no one is actually using *Markdown*. They're using their own, custom and incompatible dialects.<br>
</div><br></div>Only two of the above points apply to reStructuredText (web input and syntax getting in the way), and those particular points don't apply to Creole. Therefore I tend to advocate Creole for web applications and reStructuredText for documents.<br>
<div><div class="gmail_extra"><br><div class="gmail_quote"><div class="im">On Thu, Apr 4, 2013 at 6:49 PM, Johan Tibell <span dir="ltr"><<a href="mailto:johan.tibell@gmail.com" target="_blank">johan.tibell@gmail.com</a>></span> wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Haddock's current markup language leaves something to be desired once<br>
you want to write more serious documentation (e.g. several paragraphs<br>
of introductory text at the top of the module doc). Several features<br>
are lacking (bold text, links that render as text instead of URLs,<br>
inline HTML).<br>
<br>
I suggest that we implement an alternative haddock syntax that's a<br>
superset of Markdown. It's a superset in the sense that we still want<br>
to support linkifying Haskell identifiers, etc. Modules that want to<br>
use the new syntax (which will probably be incompatible with the<br>
current syntax) can set:<br>
<br>
{-# HADDOCK Markdown #-}<br>
<br>
on top of the source file.<br>
<br>
Ticket: <a href="http://trac.haskell.org/haddock/ticket/244" target="_blank">http://trac.haskell.org/haddock/ticket/244</a><br>
<br>
-- Johan<br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</blockquote></div></div></div><br></div></div></div>
</blockquote></div><br></div>