I mean there isn't a lot of symbols to remember, and between symbols and words, I find symbols better to read when dealing with plaintext while words would get in the way.
I mean there isn't a lot of symbols to remember, and between symbols and words, I find symbols better to read when dealing with plaintext while words would get in the way.
Implementation details still have to be implemented. Someone else might come along and figure that different documents may want to interpret "emphasis" differently, and while we're at it, why not make it composable? They may design a DSL for that, and give it a cool name too, like "cascading style sheets".
From the glorious https://en.wikipedia.org/wiki/DocBook :
<chapter xml:id="chapter_1">
<title>Chapter 1</title>
<para>Hello world!</para>
<para>I hope that your day is proceeding <emphasis>splendidly</emphasis>!</para>
</chapter>Personally - I'm always blindsided by paragraph and newline behaviour - and bullet/numbered lists seem to never work intuitively. I know the internal logic is consistent but it's never made sense to me and I can never recall it.
Dumbdown is designed with future editors in mind that would always have autocomplete. Added that to the FAQ.
https://github.com/treenotation/dumbdown/blob/master/README....