💾 Archived View for rawtext.club › ~sloum › geminilist › 002625.gmi captured on 2020-11-07 at 03:02:05. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2020-09-24)

-=-=-=-=-=-=-

<-- back to the mailing list

Escaping Gemtext

Sandra Snan sandra.snan at idiomdrottning.org

Thu Sep 10 07:32:44 BST 2020

- - - - - - - - - - - - - - - - - - - 

If you go to four spaces you'll become compatible with markdown ← notnecessarily worth it! Don't shoot the messenger on this one ♥

Paper <paper at tilde.institute> writes:

I am building a feed reader, so I am outputting plain text which can
contain some gemtext markup. I want to print it, but the client
shouldn't consider it a gemini markup. I could return "text/plain", but
I need some gemini formatting in the same page. After some discussion on
IRC yesterday, we found three approaches:
1. putting preformatting toggle lines before and after the user input
```
user input
```
- 10 more characters for each line (6 normal characters + 2x\r + 2x\n)
- if user inputs ```, all content under it will have preformatting toggle
reversed
+ supported in all clients
2. putting a single space in front of the user input
user input
+ only 1 line
+ supported in all clients
- shifts the entire user input one character to the right
3. putting a single unicode invisible space in front of the user input
‎user input
+ doesn't change the horizontal position of the text
- I am not sure what clients without support for outputting UTF-8 text
will do with it
For now, I think the second option is best for me, am I missing some
options?
Paper