Building package fails with a process which includes double-byte(multi byte) chars in BRMS

Issue

• If my process includes double-byte chars and BRMS standalone is running under non-UTF-8, building package will fail.

[ERR 101] Line 12:39 no viable alternative at input ''
[ERR 102] Line 9:6 mismatched input 'RuleFlow' in rule "RuleFlow-Split-defaultPackage.processI18N-2-3-DROOLS_DEFAULT"
Parser returned a null Package

• In Business Central on Windows, if Japanese name is used as rule name in DRL, build fails even though compilation of it succeeds with JBDS.