Just a few comments on this topic for anyone lurking here.
"the great freedom to use PowerShell everywhere on the World - with almost every language" - By using culture and localized keyboard specific characters you are negating that freedom. Anyone wanting to use your functions would need to switch to YOUR keyboard to produce that character. Best practices exist to prevent that. While language specifications may allow it, that does not make it a good idea.
It is misleading to state that "after 10 years SAPIEN still does not support international character sets" - You found
one character on your localized keyboard that poses a problem. That is all.
As a matter of fact SAPIEN tools have supported unicode and international character sets for longer than PowerShell existed.
The "old ASCII characters" are, well, just the regular characters all western languages use. They maybe old, but your are implying that it is outdated to support them, which is incorrect.
PowerShell Studio's parser does not "stop support for international character sets". That is an incorrect statement. Again, because you found one key on your keyboard that poses a problem, it is incorrect to state we do not support international character sets altogether.
Last but not least, Visual Studio Code does not support your local special character either at this point in time.
- illegal legal character.png (52.75 KiB) Viewed 1864 times
As you can see neither the function keyword nor the identifier are colored.
Script Analyzer correctly identifies your function name as a non-standard verb.
I am not saying this character should not be supported in function names. Technically it is absolutely within the language specifications to use it, that much is correct.
Is it a good idea? Best practices suggest no. Stick to the characters everyone has on their keyboard for identifiers.