mimo! @lyncia@pixie.town

since I'm ranting about subtle ways that FOSS software consistently otherises writing systems that are not European:

if you try to copy-paste a URL from Firefox that has non-European characters in it, e.g.
https://ja.wikipedia.org/wiki/ヤマネ , or
https://www.almaany.com/ar/dict/ar-ar/لسانيات/ ,

it will turn into something like:
https://ja.wikipedia.org/wiki/%E3%83%A4%E3%83%9E%E3%83%8D
or https://www.almaany.com/ar/dict/ar-ar/%D9%84%D8%B3%D8%A7%D9%86%D9%8A%D8%A7%D8%AA/ .

there's absolutely no reason whatsoever to URL escape these perfectly normal text characters, there's no benefit to it. other than perhaps aid in URL recognition by software written by uncaring Anglos who match regexpes without using the UCD properties to decide what counts as a text character (cf. previous discussion of how the UCD is conspicuously ignored and left unused by 95% of English-speaking programmers.)

yet Firefox does this for as far back as I can remember and no matter how much energy and willingness they have to add unwanted AI translations and stuff you have to disable on about:config if you want to get rid of, they never seen to care about giving uses the ability to copy-paste a URL without making their users feel like their native language are illegal, weird characters. I don't think most Anglo programmers are even *aware* of how used the rest of the world is to work around stuff like that, e.g. never selecting a URL with CTRL+L CTRL+C but always leave manually the "http" or even the "h" so that the URL escape doesn't trigger, or design your websites using ASCII characters exclusively in domain names and URL paths even though there's mechanisms to use your native language in both for decades now, and even though the software (Dr. Evil air quotes) "supports" "Unicode".