I always use <dl> for FAQs. Typically making the <dt> an anchor for the index of questions to link. edit… I should mention, this is my interpretation of the most semantic approach. As I see it, this is exactly the sort of thing <dl> is meant to mark up. As for CSS, it’s really subjective. … Read more
You probably want to use ”%%here is code%%”. This formats it in monospace (”) and prevents any interpretion of possible wiki markup (%%).
Well the spec seems to allow it, provided that only the <dd> contains nested lists. The spec states that a <dt> is an inline element, so it can’t contain a nested list. A <dd> is a block element, so an inner list inside one of these is fine.
This is an old question, but the following may be helpful. In principle, you can create any attributes you want, though you can’t expect the browser to know what to do with them. This is true both in HTML: <p thing=”whatever” … </p> and in JavaScript // p = some element p.setAttribute(‘thing’,’whatever’); You can expect … Read more
Try: (setq org-hide-emphasis-markers t) or set it via customize: M-xcustomize-variableRETorg-hide-emphasis-markersRET
That Wiki page is outdated. Telegram accepts standard Markdown text formatting: Bold: Double * = **hello world** Italic: Double _ = __hello world__ Monospace: Triple ` = “`hello world“`
Edit: Bugzilla 6.0 will include optional markdown support; it was implemented as a GSoC project in the bug linked in the question. Docs. Before 6.0, the only thing it supports is the > prefix on lines, which makes them purple and not wrap.
I think the most semantically correct would be <dl>, <dt> and <dd>, since what you’re displaying are effectively definitions of first name, age and e-mail. <dl> <dt>First Name</dt> <dd>Dominic</dd> <dt>Age</dt> <dd>24</dd> <dt>E-mail</dt> <dd>foo@bar.com</dd> </dl> However, obviously, the easiest way to display it in a table is using <table>, <th> and <td>. You could hack together … Read more