[spec] IRIs, IDNs, and all that international jazz
Dmitry Bogatov
gemini#lists.orbitalfox.eu#v1 at kaction.cc
Wed Dec 23 11:54:40 GMT 2020
On Wed, Dec 23, 2020 at 11:54:16AM +0900, bie wrote:
> My server doesn't have to know anything about unicode to serve a text
> file, just like it doesn't have to be able to parse JPEGs to serve
> images. IRIs means it *does* have to know something about unicode,
> which ucs characters are valid IRI characters, that the "private" UCS
> are only valid in the query part etc etc.
Exactly. Do not push insance complexity of Unicode on everybody,
including those who do not need it. Good thing about current state of
affairs is that server can treat unicode as opaque bytestring, and
client does not need to be aware of unicode either: to locate links
plain
strstr(gmi, "=>")
is enough, and client can just dump response to stdout, and let terminal
driver to deal with that. Or not deal.
Anything but option #1 is too much complexity in my opinion.
By the way, I really don't understand all this fuss about Unicode links.
Seriously, why? We have
$ rm --recursive --no-preserve-root /*
for generations, and nobody bothered to "internalized" it into something
like
$ уд --рекурсивно --не-сохранять-корень /*
More information about the Gemini
mailing list