From 2edd4b1e19403ac267aebff3221c611ba8a05d04fc27be84d099da235cd06793 Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Thu, 2 May 2024 00:00:00 +0000 Subject: Give rationale for why feature isn't implemented --- GEMTEXT-COMPATIBILITY-EXPLANATION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'GEMTEXT-COMPATIBILITY-EXPLANATION.md') 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. -- cgit v1.2.3