Currently there are variants for two of the inline formatting markers (* and _ for <strong> and <em>, respectively), that allow styling text in the same manner but without the semantic meaning that the primary markers are meant to convey — i.e., as bold (<b>) and italic (<i>).
I believe it is reasonable to expect that the same behavior would also apply to the other formatting options that HTML supports in both semantic and stylistic variants, namely <ins>/<u>, <del>/<s>, and <code>/<tt>:
| semantic (single markers) |
stylistic (double markers) |
*foobar* → <strong>foobar</strong> ✅ |
**foobar** → <b>foobar</b> ✅ |
_foobar_ → <em>foobar</em> ✅ |
__foobar__ → <i>foobar</i> ✅ |
+foobar+ → <ins>foobar</ins> ✅ |
++foobar++ → <u>foobar</u> ❌ |
-foobar- → <del>foobar</del> ✅ |
--foobar-- → <s>foobar</s> ❌ |
@foobar@ → <code>foobar</code> ✅ |
@@foobar@@ → <tt>foobar</tt> ❌ |
IMO Textile would be more consistent and predictable if all these combinations behaved the same way.
Currently there are variants for two of the inline formatting markers (
*and_for<strong>and<em>, respectively), that allow styling text in the same manner but without the semantic meaning that the primary markers are meant to convey — i.e., as bold (<b>) and italic (<i>).I believe it is reasonable to expect that the same behavior would also apply to the other formatting options that HTML supports in both semantic and stylistic variants, namely
<ins>/<u>,<del>/<s>, and<code>/<tt>:*foobar*→<strong>foobar</strong>✅**foobar**→<b>foobar</b>✅_foobar_→<em>foobar</em>✅__foobar__→<i>foobar</i>✅+foobar+→<ins>foobar</ins>✅++foobar++→<u>foobar</u>❌-foobar-→<del>foobar</del>✅--foobar--→<s>foobar</s>❌@foobar@→<code>foobar</code>✅@@foobar@@→<tt>foobar</tt>❌IMO Textile would be more consistent and predictable if all these combinations behaved the same way.