<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br>
<div>
<div>On 22 Aug 2012, at 16:13, Brandon Allbery wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">On Wed, Aug 22, 2012 at 4:37 AM, Philip Holzenspies <span dir="ltr">
<<a href="mailto:pkfh@st-andrews.ac.uk" target="_blank">pkfh@st-andrews.ac.uk</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, there are many things people read in the proposal that I didn't want to put in, but the things I very much do want to include get lost in translation also. I wanted to allow the GHC source itself to be written in markdown.</blockquote>
</div>
<br>
If the existing source tree is using one form of markup, changes and additions should really be consistent with what's already there instead of introducing a new kind of markup. This could actually be *more* disruptive.<br clear="all">
</div>
</blockquote>
<br>
</div>
<div>The point was that quite a bit of the GHC source has markdown-like things in it, using LaTeX-style code-fencing, but LaTeX-incompatible markup (like underlining section with ~~~~~).</div>
<div><br>
</div>
<div>Ph.</div>
<br>
</body>
</html>