<html>#2523: The trac mailing list could have more useful content
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Gabriele Bozzola</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Other</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Well its in the HTML content… which is of no use to use since you cannot see the HTML in the digest. Currently the HTML looks like this when properly rendered: <a data-is-external-link="true" href="https://ekohaes8.ncsa.illinois.edu/~rhaas/2523.html" rel="nofollow">https://ekohaes8.ncsa.illinois.edu/~rhaas/2523.html</a></p>
<p>The “proper” solution is to generate a “multipart/alternative” email which has both plaintext (for archiving and digest) and HTML (everyone else) content. Due to the way Bitbucket works (and not wanting to enter into the whole mess of creating content preserving plaintext from HTML) the plaintext will be the markdown source which may or may not look nice.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2523/the-trac-mailing-list-could-have-more'>https://bitbucket.org/einsteintoolkit/tickets/issues/2523/the-trac-mailing-list-could-have-more</a></p>
</html>