From c480ac37365f5876bcb42080dcf6c1b2e6505a63 Mon Sep 17 00:00:00 2001 From: Atlas Cove Date: Thu, 11 May 2023 15:03:13 +0000 Subject: [PATCH 1/3] add in/article/perfect-markup.md --- in/article/perfect-markup.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 in/article/perfect-markup.md diff --git a/in/article/perfect-markup.md b/in/article/perfect-markup.md new file mode 100644 index 0000000..c5f90f0 --- /dev/null +++ b/in/article/perfect-markup.md @@ -0,0 +1,13 @@ +# 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 hack in formatting 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. From 968d2e62b063520539ce231d7df92e8b98ad0859 Mon Sep 17 00:00:00 2001 From: Atlas Cove Date: Wed, 31 May 2023 22:59:55 +0100 Subject: [PATCH 2/3] update perfect markup.md --- in/article/perfect-markup.md | 37 +++++++++++++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/in/article/perfect-markup.md b/in/article/perfect-markup.md index c5f90f0..ccca2ea 100644 --- a/in/article/perfect-markup.md +++ b/in/article/perfect-markup.md @@ -5,9 +5,44 @@ - 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 hack in formatting in plain text, you have `__underscores__` that look like *underlines*, +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. +\`\`\` +``` From 4ad3cd0f79d15c5e475b769edeffa3921b3474ea Mon Sep 17 00:00:00 2001 From: Atlas Cove Date: Sun, 4 Jun 2023 12:27:32 +0100 Subject: [PATCH 3/3] Added files to ignore debatable if i should publish --- dat/ignore.txt | 4 +++- in/postext/outline.md | 18 ++++++++++++++++++ 2 files changed, 21 insertions(+), 1 deletion(-) create mode 100644 in/postext/outline.md diff --git a/dat/ignore.txt b/dat/ignore.txt index 592c5b9..50ae5bf 100644 --- a/dat/ignore.txt +++ b/dat/ignore.txt @@ -1,2 +1,4 @@ css/extra.scss -dnd/template.org \ No newline at end of file +dnd/template.org +article/perfect-markup.md +article/perfect-markup.md diff --git a/in/postext/outline.md b/in/postext/outline.md new file mode 100644 index 0000000..a0acd66 --- /dev/null +++ b/in/postext/outline.md @@ -0,0 +1,18 @@ +# 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 `[...]`.