homographs

If the output has homographs, likeliness is split per definition, but the UI only shows the best one.

And bidirectional rsync between practically everything else and a Mac still requires `--iconv=utf-8,utf-8-mac` to avoid problems because of homographs.

That said, bolting Unicode into unique identifiers humans are meant to read is a bad idea because of the homographs.

The results are different because it's matching somethings that are an exact character match, and others that are just visually similar (homographs?).

Yes but I guess that the message was meaning that browsers now detect homographs and display the punycode instead.

I think the popularity of retina displays will result in a clarifying divergence of these homographs into different representations.

It used very rudimentary language technology so it 'suffered' from things like homographs.

Some of these homophones double as homographs, as you can see.

Typo squatting is a thing, and so are Unicode homographs.

Ironically dictionaries may've been the reason this distinction was blurred with early lexicographers grouping homographs (logically, spelling in text not relevant) and homophones under an homonym heading.

Likewise, you understand homographs based on the context.

Well, auto-antonyms are homographs with opposite meanings.

It’s fascinating to see how words like “ground” can bridge entirely different concepts, or how homographs create unexpected connections between semantic domains.

Bear in mind that while homographs in American English, "metre" and "meter" are different things.

So, in practice, ambiguities like the one you point out are more likely than not to be as constraining to Latin script-based programmers as common English homographs like "bank" do.

Or "est" (he is) and "est" (the East) although English also has plenty of such "non-homophonic homographs"...

Homographs, Unicode madness (normalization etc..), and the biggest problem of all: input methods.