I wonder how we could get the full expressiveness of Mediawiki (MW) markup out the back end, when haddock parses the input according to a less expressive markup language.  Hm.  Maybe just let it pass lots of markup through without realizing that it's markup.  Then a MW back end would unparse a few things (italics, hyperlinks) back into markup.  Of course, MW markup differs from Haddock markup, so we'd probably want to turn off some of Haddock's parsing (italics, at least).  I don't see how to do that in a non-intrusive way.  
<br><br>Perhaps Haddock could be refactored and exposed as a library, to give it some more flexibility.&nbsp; Some refactoring is intended anyway, to sync up with ghc language changes.&nbsp; In the process, its core functionality could be extracted as a library and hooked up to various front-ends as well as back-ends and maybe other processing as well.
<br><br>Cheers,&nbsp; - Conal<br><br><div><span class="gmail_quote">On 1/10/07, <b class="gmail_sendername">Duncan Coutts</b> &lt;<a href="mailto:duncan.coutts@worc.ox.ac.uk">duncan.coutts@worc.ox.ac.uk</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 2007-01-09 at 21:58 -0800, Conal Elliott wrote:<br>&gt; Suppose Haddock&#39;s documentation language (&quot;-- | ...&quot;) were an extended<br>&gt; form of a common wiki markup language, and specifically Wikimedia&#39;s,
<br>&gt; because the Haskell wiki uses it. Instead of converting to HTML,<br>&gt; Haddock could then pass through most markup unchanged and make wiki<br>&gt; links out of its current link markup (modules &amp; entities).<br>
<br>Haddock is designed to be able to produce various different output<br>formats. It&#39;d be perfectly reasonable to add a wkik markup backend.<br>There&#39;s nothing that special about the html backend, it&#39;s just the most
<br>mature and most used.<br><br>Duncan<br><br></blockquote></div><br>