Three possible uses for IRIs

On Mon, Dec 7, 2020 at 9:47 PM <colecmac at protonmail.com> wrote:


> I don't think that's true. To convert them to a URI reference, the domain
> needs
> to be extracted and punycoded,


Agreed.  But if you have a Punycode encoder, then the following steps will
convert an IRI reference to a URI reference, without regard to whether it
is an IRI or a relative reference:

1) Look in the IRI reference for a "//" and a following "/"; if they exist,
pass the characters in between through your encoder and substitute the
result into the IRI reference.

2) Start over from the beginning.  If a character is ASCII, leave it
unchanged.  Otherwise, take the character, convert it to UTF-8 bytes (easy)
and each byte to hex digits (trivial), decorate it with leading %
(trivial), and move on.  When you come to the end, stop.


> Furthermore, it's breaking change to Gemini. I don't think that's a good
> idea in
> any case with the possible exception of TLS security. Gemini must be
> reliable,
> and it's too late for a breaking change.
>

Probably true.  ~~sigh~~



John Cowan          http://vrici.lojban.org/~cowan        cowan at ccil.org
Normally I can handle panic attacks on my own; but panic is, at the moment,
a way of life.                 --Joseph Zitt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201207/67b2
3603/attachment.htm>

---

Previous in thread (2 of 32): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)

Next in thread (4 of 32): 🗣️ Emma Humphries (ech (a) emmah.net)

View entire thread.