[SPEC-CHANGE] lang parameter, minor line type changes, clarifications...

Matthew Graybosch hello at matthewgraybosch.com
Sun Jun 7 23:40:33 BST 2020


On Sun, 07 Jun 2020 21:38:04 +0300
Frank LENORMAND <lenormfml at gmail.com> wrote:

> Writers are no longer ensured by the standard that their text
> surrounded with asterisks will not be decorated by the client, by
> extension.

Writer here, but speaking strictly for myself. I don't see a problem
with this change. Details below.

---

I use asterisks inline for emphasis because that's a habit I've taken
from Markdown. My understanding of the standard was that the
behavior of inline asterisks (as opposed to asterisks at at the
beginning of a line to indicate a list item) is undefined and thus
client-dependent.

If the client uses them to denote *italics* and **bold**, great. If
not, I figure that readers familiar with plain-text email will still
interpret such text accordingly. Either way, as a self-hosting writer,
my job is to make the words and reliably serve them. What happens on
the client side is none of my business.

My understanding of the new changes to the standard is that the
behavior of inline asterisks is *still* client-dependent. That's fine
with me as a writer, TBH. If I wanted the illusion of precise control
over how clients render my documents, I'd go back to HTML/CSS--or
pick up groff again and just post PDFs. :)

-- 
Matthew Graybosch           https://www.matthewgraybosch.com
#include <disclaimer.h>	    gemini://starbreaker.org
Harrisburg,PA	 	    gemini://demifiend.org
"Out of order?! Even in the future nothing works."


More information about the Gemini mailing list