💾 Archived View for rawtext.club › ~sloum › geminilist › 004668.gmi captured on 2024-03-21 at 16:49:55. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Stephane Bortzmeyer stephane at sources.org
Sun Jan 3 13:33:14 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Mon, Dec 28, 2020 at 02:54:14PM +0100, Solderpunk <solderpunk at posteo.net> wrote a message of 22 lines which said:
it's still possible for the server and client to have different
ideas about how a hostname or path are represented, right? With one
using a composed form and the other a decomposed form?
Not right. RFC 5891, the standard for IDN, states that "By the time astring enters the IDNA registration process as described in thisspecification, it MUST be in Unicode and in Normalization Form C (NFC[Unicode-UAX15])." So, at least the hostname has no problem.
gemini://gemini.bortzmeyer.org/rfc-mirror/rfc5891.txt