It's already utf-8, even just lower case for both author and publisher. Author works fine, not publisher.

Even restarted publisher server to make sure no cache issue. Still the same result.

We have an AEM 6.5.8 form display in Spanish and works fine for submission as well, all the fields with spanish character in data.xml are working fine:{"afData": {"afBoundData": {"data": {"latamInfo": {"topMarginContainer": {"nasNo": "5007699", "reportNo": "ü, é, á, í, ó, ú, ñ, Ñ, ¿, ¡, Á, É, Í, Ó, ...

in AEM 6.5.8, it uses mozilla rhino package with is ages older, that's why the ecmascript 6 arrow function cannot be parsed and report syntax error. AEM 6.5.9 has the latest and works out of the box. 

Finally, in AEM 6.5.8, the javascript uses apach rhino 1.7.7.1_1:<dependency><artifactId>org.apache.servicemix.bundles.rhino</artifactId><version>1.7.7.1_1</version><groupId>org.apache.servicemix.bundles</groupId><scope>provided</scope></dependency> Which has a bug for arrow function and it was rele...

Finally, I make the json-path works in my workflow steps osgi bundle. It's hell lots of work. You need to put all your maven dependencies in pom.xml, even it is explicitly referred. then you need to export all the packages felix need to lookup, and put the maven bundles in the build list:<plugin> ...

Does anyone has an osgi service bundle that include a few dependency jar files? I want to use json-path in my osgi bundle, however, json-path need a few maven dependencies: json-smart, asm, etc. I tried to convert each jar as separate osgi bundle jar or embed all the jars in my bundle, none of them ...

No, just the AEM forms rules editor can pass the validation, the final output *.min.js still not minified and the client library source code showed on the final publisher page. Seems need more dig into it. ^_^ I enabled the Minify on the HTML client library manager, still, the ecmascript_2019 source...

problem resolved:In HTML library manager, change the default jsProcessor to min:gcc.Then for client library folder, add the following:jsProcessor=[min:gcc;obfuscate=true;languageIn=ECMASCRIPT_2019;languageOut=ECMASCRIPT3] then application works. At least AEM js compiler syntax check passed for this ...

Thanks, opened a ticket to Adobe support already. Seems for now, we have to gcc ourselves and put the compiled code in the client library.