For someone, this would be a very trivial and insignificant issue.
Even in non-English speaking countries, it is generally recommended not to use non-English characters for programming.
But I have a slightly different opinion about the functionality of the Behavior Package
The strength of Behaviour package
- Productivity
(easy to make / easy to collaboration)
- Accessibility
(easy to read / can use non-engineers)
Non-native English speakers lose some of their strengths.
(Of course, it’s very good and satisfying enough.)
I like the fact that use “Natural language” to visualize it.
Through this, I think I can easily collaborate with colleagues who are not programmers.
here is example
It works well on Blackboard
However when create action,
Non-English characters are not allowed for the name of variable.
But if i change this manually in Script, it works!!
Will this create other unintended problems?
I hope non-eng variable names are supported. 
Hi Seoyeon,
Thank you for taking the time to give us your feedback.
We do believe that the tool should be usable with all languages and, although I wasn’t personally working on the localisation support aspect of the package, I remember seeing a fair amount of code written to support this feature. So you shouldn’t have any underlying problems using them.
After a brief discussion with the team, we actually found the issue in the node wizard story field validation! The fix should be deployed in an upcoming patch (probably landing in 2 weeks).
Please let us know if you have any problems using the tool with non-English characters.
Thanks again!
Side node: We use UITK internally, so we are currently limited to its capabilities, so some localisation functions such as right-to-left writing and Arabic support may not be supported at the moment.
2 Likes
The fix should be deployed in an upcoming patch (probably landing in 2 weeks)
→ Was this omitted in the latest patch? It seems like the same issue still persists (1.0.3) 
