There is a fairly good solution to this for things like code editors and URLs or search strings in browsers: If a string contains a non-ASCII code point that is a homograph for an ASCII character, swap the text and background colors.
It's a design goal of Unicode to support exact round-trip transformation with any code page ever in use in the real world, so they can't unify two characters that appear at different code points in a greek codepage without breaking things, even if they're always graphically indistinguishable in a font.
Context is the key here. Greek text doesn't use the semicolon for other purposes and searching/replacing such single characters in source code is a terrible idea anyway (think comments, string literals...). So what is the prohibitive failure scenario here?
Indistinguishable (for humans) characters with different code points were a stupid idea, it's fine to abuse it in order to point out that fact.
A semicolon is not considered sentence final, whereas a question mark usually is. This makes it easier for software to auto capitalize. So at least that's possible a use case.
There's also the possibility that Greek requires the top dot to be square or circle, meaning it might in fact have subtle differences in print.
And those people are a menace. "Ball bearings" is a single word with a space in the middle. The only way you're going to get reliable word segmentation is with a natural language parser and a lexicon with an entry for "ball bearing". At that point, you're already recognizing "aren't" as a word; the punctuation isn't really relevant.
On the other hand, if you're not particularly upset about messing up space-including words, there's no real reason to be upset about apostrophe-including ones either.
Such software will need and have a language setting anyway (e.g. for hyphenation). It doesn't have to and cannot rely on code points alone, so the characters (or rather, different uses of the semicolon) needn't have different codepoints.
This is true, but it's equally true that they both have undiverged continuity with 'Greek Α', which has its own code point.
Case in point: 每 (chinese) vs 毎 (japanese).
I know that I am perhaps not well informed on this issue, but I also think that having multiple code points for what most people would perceive as the "same" character is not a good idea.
入 vs 人
玉 vs 王
口 vs ロ <- my font might make those indisguishable out of context
千 vs 干 vs 于
of course in English we have 0 vs O and l vs 1
Compare 人 with: http://i.imgur.com/ZpFMQoU.png for one of the most obvious differences.
For Japanese there is: 篆書、隷書、楷書、行書、草書.
https://en.wikipedia.org/wiki/Seal_script
https://en.wikipedia.org/wiki/Clerical_script
https://en.wikipedia.org/wiki/Regular_script
https://en.wikipedia.org/wiki/Semi-cursive_script
https://en.wikipedia.org/wiki/Cursive_script_(East_Asia)
Can see more here:
[1] https://en.wiktionary.org/wiki/%E6%AF%8F [2] https://en.wiktionary.org/wiki/%E6%AF%8E
I'm sure a Japanese person would be perplexed as to why that extra "u" matters since it's the "same damn word".
Want to jump off ?
That's somewhat language dependent, though its true for most uses of most popular languages.
It's really difficult to do the right thing here. If Greek question marks share code point with semi-colon, it obstructs search and replace for question marks.
Subtle differences in how Japanese and Chinese are written has led to differently written characters sharing the same code point. It's nice that you can easily look up most Japanese characters in a Chinese dictionary and see how they are used in China, but it has become frustratingly hard to get subtleties in their written form right. The Chinese version may have the line strike through another line, while the Japanese only has it touching.
I honestly don't know how to go about posting how to same code points have different written forms!
But it seems like it would be nice if code editors warned about text outside ascii. You usually only want that in strings and comments.