Three possible uses for IRIs

[Philip Linde]

On Mon, 7 Dec 2020 23:00:01 -0500
John Cowan <cowan at ccil.org> wrote:
 
> 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.

There's a "drawl the owl" step somewhere here regarding Unicode
normalization. Does the server like your ä:s fully composed or
decomposed, or should the server itself be responsible for
normalization?

-- 
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201208/cf4dc147/attachment.sig>