If I can do this, what's preventing some guy in Japan or India or Peru from doing the same, of course focusing on their languages?
When you claim that a word in some other culture is not "a word", just because it's not recognized by your machine, that's demeaning to say the least.
In this case, the code doesn't match the word regexp, like it may be a @TwitterHandle or a "comp.lang.c" with periods in it, or an unsupported Unicode range. It doesn't know why it is not matching, just that it doesn't.
Nonetheless, even when coding, one should also consider thoroughly the UX and how it would be addressing the others.
Saying "unsupported word" is much more sympathetic than "needs to be a word" (where you define what a "word" is, and the general user is unaware of such definition).
> The term "𓀀" contains characters that are not currently supported