💾 Archived View for station.martinrue.com › adou2 › adbfcef08d5e47a084707086c4b18a70 captured on 2023-11-14 at 09:37:12. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Spartan is interesting but… US-ASCII? Does that mean that I couldn't type é, ä or ĉ?
2 years ago · 👍 syntheist, justyb, iam_ami
@mozz Oh, I should have understood. Thanks for your answer :-) · 2 years ago
If you're curious, see this long-ass thread about how complicated unicode can get with gemini requests (there has still not been any resolution AFAIK). https://gitlab.com/gemini-specification/protocol/-/issues/1 · 2 years ago
I really should clarify this in the docs. The spartan request and response header lines are US-ASCII, which just means to you need to %-encode paths and punycode domain names. This solves a bunch of unspecified edge-cases that gemini has with sending request URLs that contain unicode characters to servers. The response document for spartan can be whatever encoding you want, the default for text/gemini is UTF-8 just like in gemini. · 2 years ago
Curious. I've been sending UTF-8. The request specification seems to support an encoding format; the examples page shows:
2 text/plain; charset=utf-8
I think it's a leftover from some earlier summary that should be fixed. Spartan is a transport protocol anyway, and you can send gmi or html over it if you want. Or anything else. · 2 years ago