Special characters, like Swedish Å, Ö, Ä, get garbled when a UTF-8-encoded script file is deployed via the IFS installer's file executor, but work fine if the file's encoding is changed to ANSI. Is there a better fix than converting every deployed script file's encoding?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This is a known limitation in the installer's own Java code, specifically its file-reading component, which reads files using a plain FileReader that defaults to the platform's OS-level default encoding rather than a specifically-forced encoding. Rather than changing the actual script files' own encoding to ANSI as a workaround, which avoids the symptom but isn't a genuine root-cause fix, force the JVM's default file encoding to UTF-8 for the installer process itself, by adding a -Dfile.encoding=UTF-8 argument to the java invocation inside the installer's own command/batch file. This correctly forces UTF-8 handling for the installer's own file reads without needing to alter the actual source script files' encoding.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions