>so he just selects a subset he can handle and bans everything else.

Yes? And the problem is?

The problem is the scale at which it happens and lack of methods-to-go in most runtimes/libs. No one and nothing is ready for unicode complexity out of box, and there's little interest in unscrewing it by oneself, cause it looks like an absurd minefield and likely is one, from the persepective of an average developer. So they get defensive by default, which results in $subj.

▲

throwaway290 7 months ago | parent | prev [-]

The next guy with a different subset? :)

▲

Muromec 7 months ago | parent [-]

The subset is mostly defined by the jurisdiction you operate in, which usually defines a process to map names from one subset to another and is also in the business of keeping the log of said operation. The problem is not operating in a subset, but defining it wrong and not being aware there are multiple of those.

If different parts of your system operate in different jurisdictions (or interface which other systems that do), you have to pick multiple subsets and ask user to provide input for each of them.

You just can't put anything other than ASCII into either payment card or PNR and the rules of minimal length will differ for the two and you can't put ASCII into the government database which explicitly rejects all of ASCII letters.

▲

throwaway290 7 months ago | parent [-]

HN does not accept emoji because of jurisdiction huh?

▲

Muromec 7 months ago | parent [-]

That depends on what political philosophy you follow -- they either do, or are wrong and mean.

	▲	throwaway290 7 months ago \| parent [-]
		I was being sarcastic. As top comment said if Unicode was not a joke and epitomization of feature creep this would be a non issue.