Description
Is your feature request related to a problem? Please describe.
We have some strict language requirements within some of the public sector, where "business" expect to do their work in Swedish (with the crazy character å, ä and even ö).
It is fine to use those characters and other as variable names in go, but we generally avoid that since we define it as IT-specific woke.
However, a rule is something share by IT and busiess, where it really would make sense to be able to use non-ascii characters in structs and functions. Even better if we could translare the few keywords in a rule to Swedish as well (but that is minor).
Describe the solution you'd like
A clear and concise description of what you want to happen.
Allow all runes in rules that are allowed in golang variable name.
(if easy, allow translation of the keywords in a rule as well).
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
- A preprocessor translating rules where we try to identify any non-ascii characters and figure out if it's inside a comment or is a real identifier will duplicate alot of the parsing already done by the rule engine.
- Just omit the dots give us a lot of trivial but annoying tries, since we use swedish words not spelled as we have learned to do
Additional context
Add any other context or screenshots about the feature request here.