💾 Archived View for rawtext.club › ~sloum › geminilist › 002832.gmi captured on 2020-10-31 at 14:48:34. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Sandra Snan sandra.snan at idiomdrottning.org
Mon Oct 5 09:25:46 BST 2020
- - - - - - - - - - - - - - - - - - -
Now, I wouldn't be opposed to Gemini instead using iris with utf8mb4supported both RTL and LTR. I rail against change on here but that wouldbe a welcome change. There are some severe security risks that come withsuch a change so it's not undertaken lightly. As discussed earlier withthe NN/.. issue.
Sandra Snan <sandra.snan at idiomdrottning.org> writes:
https://stackoverflow.com/questions/2742852/unicode-characters-in-urls
Gemini uses URLs.
So 예 한글, but, percent encoded.
"mieum" <mieum at tilde.team> writes:
Hi Everyone,
I recently decided to start an experimental Gemlog written in Korean. I
found, however, that some clients do not like having Asian text in the
path of the URL---either as the name of a folder or a file.
What is the general consensus about non-latin characters in URLs? The
Gemini Spec doesn't say anything that would lead me to believe I
shouldn't name my files and folders in Korean. Also, for most clients it
is apparently a non-issue.
For an example, you can point your client to gemini://namu.blue/쌍록/
Some clients will crash, some will not attempt to load the page, and
some will just return a Permanent Failure. Some will even crash
attempting to parse the link to that page on gemini://namu.blue/.
Anyway, I just wanted to see what everyone thinks about the best
practice in this situation.
Thanks!
~mieum
gemini://rawtext.club/~mieum/