toastal

Those are definitely good points brought up a lot when these come up. Asciidoctor’s tooling translates these when you render, but it can be jarring to see English in a...

These are all good proposals actually. If it were up to me, I like the idea of supporting both an Unicode symbol and an ANSI/ASCII-compatible option where feasible as there...

@bpj How does configurability help with situations where you can't touch the configuration (as noted: a `README.dj` on a code forge, a social media post, etc.)? The reason I opened...

@bpj then should `>` be removed because you could just make a block with `::: blockquote` and hint that this `` should maybe be rendered as a ``? Personally, I...

If anything, I'd say mobile has an easier time doing emoji as, in my experience, mobile keyboards almost always come with an emoji input--including on Ubuntu Touch. On my Linux...

I would disagree with overloading with definition lists in the same way that I object to Microsoft GitHub-flavored Markdowns overloading of the semantics of the blockquote element which muddies their...

> attributes being in English This goes back to @bpj ’s point of does the syntax need this feature? The more prevalent the feature, the more you want it to...

> epigraph Along this train, an abstract / backstory are common initial units to posts or chapters (both of which appear in the [BlogPosting](https://schema.org/BlogPosting) schema).

What about `U+2713 ✓ CHECK MARK`? Filling with generic ASCII characters is still useful for keyboarding but hardly accurate—those symbols have a lot of other meanings.

This resonates with me. I deeply-nested nix files at work and Flakes in general tend to be quite nest-y. I find these files grueling to read because 2 spaces doesn't...