It's not that inconvenient if you omit unnecessary closing tags:
reply <tr>
<td> first
<td> second
<tr>
<td> what
<td> ever
> if you omit unnecessary closing tags
replyAs someone who had written lots of XHTML in the past, not having closing tags makes my eyes twitch like Scrat in Ice Age. I even occasionally write `<br>` like `<br/>` out of habit.
Fair point, though /DT and /DD are also optional just like /TH, /TD and /TR are. So in effect, def…scription list could structurally save you one TR for each entry and two "BLE"s:
reply <table><tr><th>Term 1<td>Definition 1
<tr><th>Term 2<td>Definition 2
</table>
<dl><dt>Term 1<dd>Definition 1
<dt>Term 2<dd>Definition 2
</dl>Isn't markdown table just a bunch of | ?
replyThat's the problem.
replymost specifically the problem is that markdown tables don't allow breaking the table row in multiple lines
replybut then you can always use HTML tables in markdown and Pandoc transforms it just fine
<br> has worked fine whenever I’ve needed line breaking in markdown tables
replyI think they mean breaking the line in the markup, not the output
replyThey mean in the Markdown code, not in the output.
replyEvery markdown implementation is supposed to allow inline HTML.
replyYou're right, but forcing tables to cosplay as DLs was far from the worst way that tables were abused.
replyAt least <td>s could easily centre things vertically ;)
replyI always thought the DL as a single row of a table.
reply