From 565ac8d612ce5df79c75798f8418260c86acdae9 Mon Sep 17 00:00:00 2001 From: Atlas Cove Date: Tue, 24 Oct 2023 15:09:07 +0100 Subject: [PATCH] Sequestering content on postext to single branch. --- in/article/perfect-markup.md | 48 ------------------------------------ in/postext/outline.md | 18 -------------- 2 files changed, 66 deletions(-) delete mode 100644 in/article/perfect-markup.md delete mode 100644 in/postext/outline.md diff --git a/in/article/perfect-markup.md b/in/article/perfect-markup.md deleted file mode 100644 index ccca2ea..0000000 --- a/in/article/perfect-markup.md +++ /dev/null @@ -1,48 +0,0 @@ -# Treatise on My Perfect Lightweight Markup Language - -## It would have... -- org-mode style inline syntax. -- with the ease of HTML hackery of textile. -- with the compiled language support that Markdown offers. - -org-mode's inline attributes map nearly 1:1 with how I personally format in plain text, you have `__underscores__` that look like *underlines*, -`//italics//` that look like *italics*, and `**bold**` that actually looks like **bold**. I want a LML that has nearly all the same features that you'd find on -your common or garden word-processor, and with how often I refer to D&D 5e books, I want actual, *implemented* description lists. org-mode is absolutely -perfect for this, but it's nearly entirely confined to the single text editor it was created in. Markdown has amazing support, but as a general shorthand -for HTML, it feels sorely lacking. Textile makes up for it's shortcomings, but it suffers from a lesser problem that also plagues org-mode's development, -and it's syntax can feel woefully clunky at points, that being said, it has the absolute best numbered list syntax out of all of the above mentioned LMLs. - -## Sample - -``` -= Heading 1 -== Heading 2 -=== Heading 3 -====[id] Heading 4 - -- Here -- is -- an -- unordered -- list - -#. Here -#. is -#. an -#. ordered -#. list - -- Here :: is -- a :: single -- description :: list - -! - -And here is **Bold**, //Italic//, __Underline__, ^^Superscript^^, & --Strikethrough-- %{color:red}We also have span support%, %(i)in diffent flavours!% - -[Markdown's](https://en.wikipedia.org/wiki/Markdown) link format works //fine//. - -\`\`\`c -// So do the code blocks. -\`\`\` -``` diff --git a/in/postext/outline.md b/in/postext/outline.md deleted file mode 100644 index a0acd66..0000000 --- a/in/postext/outline.md +++ /dev/null @@ -1,18 +0,0 @@ -# Postext -## Requirement Levels -The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119). -## Pronounciation -"Postext" is a combination of the words "post" and "text", so it's pronounced "pohs-text". -## Definitions -- `EOL` is defined as either **CR** (`0x0D`) or **CRLF** (`0x0D 0x0A`). It is RECCOMENDED you keep to either one of the two forms throughout the written document. -## Design Rules -1. Whatever works best for the other LMLs, we adopt. -2. Unix philosophy is king, postext's one thing well is HTML rendering. -3. We need enough syntax to be hackable without changing the internals. -4. Inline style elements must always be two identical characters together; it's the only way to be sure. -## Features -### Inline -- **Bold**: two (2) `*` (`0x2A`) enclosing text. Converts to `[...]` -- **Italic**: two (2) `/` (`0x2F`) enclosing text. Converts to `[...]` -- **Underline**: two (2) `_` enclosing text. Converts to `[...]` -- **Superscript**: two (2) `^` () enclosing text. Converts to `[...]`.