aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-06-01 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-06-01 00:00:00 +0000
commita4bf3d331ac4b5929d74dd6dbce092f1406003fe4e5f6a89f4c52ce8f8162e34 (patch)
tree0c59cbc072b31f0b159c15e201ade610c66602777a0bef4b0da5c1298e0cb0f6
parent63d9398da10daed4d9dcc22a59cdd941307daeb4b3ac1c8ebcb9e9f3729921c3 (diff)
Update documentationv0.6.0
-rw-r--r--GEMTEXT-COMPATIBILITY.md26
1 files changed, 14 insertions, 12 deletions
diff --git a/GEMTEXT-COMPATIBILITY.md b/GEMTEXT-COMPATIBILITY.md
index 3e206a4..2d4e7b3 100644
--- a/GEMTEXT-COMPATIBILITY.md
+++ b/GEMTEXT-COMPATIBILITY.md
@@ -45,27 +45,29 @@ Newlines are partially supported. Line breaks are unsupported.
Explanation:
-The gemtext renderer and HTML renderer handle whitespace differently. While whitespace has special meaning in Markdown, the gemtext renderer simply copies it unmodified into the output. It is possible to achieve consecutive newlines in the HTML, but the gemtext won't render it correctly. For compatibility, use exactly two literal newlines except after headings. After headings, just use one newline.
+The gemtext renderer and HTML renderer handle whitespace differently. While whitespace has special meaning in Markdown, the gemtext renderer simply copies it unmodified into the output. It is possible to achieve consecutive newlines in the HTML, but the gemtext won't render it correctly. For compatibility, use two literal newlines after each new element except before headings. Headings must be preceded by three literal newlines.
E.g:
-```markdown
-Do
+````markdown
+I am a paragraph.
-this
-```
+* unordered list item 1
+* unordered list item 2
-```markdown
-Don't do
-this
-```
+1. ordered list item 1
+2. ordered list item 2
-```markdown
-Don't do
+## I am a Heading
-this
```
+I am preformatted text.
+```
+
+> I am
+> a quote
+````
## Emphasis