Honest question: would it be that bad to mandate and enforce 100% ASCII source files? Arguably every and any Unicode character and, well, arguably even any string of characters can (should?) go to a properties/resources file (properties/resources files which, btw, also greatly simplifies i18n/l10n).
Then build/commit/test hooks could be used to enforce that source code files are indeed 100% ASCII.
I know, I know... Some are going to lament they don't have their shiny Unicode symbols right in their source file. But... It looks like you get what you pay for.
Bruce Schneier wrote it when Unicode came out btw: "Unicode is too complex to ever be secure".
Then build/commit/test hooks could be used to enforce that source code files are indeed 100% ASCII.
I know, I know... Some are going to lament they don't have their shiny Unicode symbols right in their source file. But... It looks like you get what you pay for.
Bruce Schneier wrote it when Unicode came out btw: "Unicode is too complex to ever be secure".