aboutsummaryrefslogtreecommitdiff
path: root/GEMTEXT-COMPATIBILITY-EXPLANATION.md
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2024-05-02 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2024-05-02 00:00:00 +0000
commit2edd4b1e19403ac267aebff3221c611ba8a05d04fc27be84d099da235cd06793 (patch)
tree92b1e29da3b99769e1f803b11a8a19f5ed015293536339325325a7057adad3d5 /GEMTEXT-COMPATIBILITY-EXPLANATION.md
parent61ba4b8cbb02bde9c62faa2698f7e0a419fe60a98193b2a70de1a2b475bb39c8 (diff)
Give rationale for why feature isn't implemented
Diffstat (limited to 'GEMTEXT-COMPATIBILITY-EXPLANATION.md')
-rw-r--r--GEMTEXT-COMPATIBILITY-EXPLANATION.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/GEMTEXT-COMPATIBILITY-EXPLANATION.md b/GEMTEXT-COMPATIBILITY-EXPLANATION.md
index ca033df..a2a311c 100644
--- a/GEMTEXT-COMPATIBILITY-EXPLANATION.md
+++ b/GEMTEXT-COMPATIBILITY-EXPLANATION.md
@@ -80,4 +80,4 @@ In order to allow other output formats to use inline image syntax without harmin
Whitespace has no special meaning in gemtext. Gemini clients simply display whitespace verbatim. This can lead to discrepancies between the gemtext output format and other output formats if the guidelines in the [gemtext compatibility reference guide](GEMTEXT-COMPATIBILITY-REFERENCE-GUIDE.md) are not followed.
-There are plans to implement regex which "autocorrects" the whitespace between elements so that discrepancies cannot appear in the gemtext output and so that the user does not need to manually insert the correct amount of whitespace between elements.
+The gemtext renderer can "autocorrect" whitespace to avoid the need to manually format it. This feature was implemented, but later scrapped since it made the regex unmaintainable and introduced too many new edge cases.