Thank you so much for the summary! I lost track of the ML for a few
days and... it was just too much >.<
My contention is this: I want us to support internationalization as
best we can. And as far as I understand it the web has done this with
punycoded domain names and percent encoded paths for years. And after
a few hours of fiddling with my own cli tool gemcall
(https://notabug.org/tinyrabbit/gemcall/src/master/gemcall) it doesn't
look like it's too hard. Check line 35:
parsed = up.urlparse(url).encode("idna")
As far as I can tell gemcall can now handle gemini://[rabbit emoji
that I don't know how to include...].mozz.us/
As for the path that follows, that must be percent encoded in the
gemtext document. There is no way for a client to know if a path is
already percent encoded or not, and percent encoding twice breaks the
link. Consider this:
=> gemini://example.com/why-space-is-%20-in-urls.gmi We see that this
needs to be percent encoded, but a tool can't reliably tell if it does
or if it is already.
Requiring clients to punycode domain names will break existing
clients. Sorry about that, but let's just fix them instead of
complaining about it.
Cheers,
ew0k
Oh! Mandatory rabbit!
()_()
(^.^)
_(| |)_
---
Previous in thread (1 of 34): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)
Next in thread (3 of 34): 🗣️ Alex // nytpu (alex (a) nytpu.com)