Details
Description
Workaround: start java with -Dfile.encoding=UTF-8
This is an umbrella issue for issues found in the FCS release. Code paths identified so far:
- auto export handling of repository resource bundles (
CMS-10234) - essentials translation instruction for translations and files (
ESSENTIALS-994) - l10n tooling (
CMS-10238)
Attachments
Issue Links
- relates to
-
CMS-10234 autoexport writes repository resource bundles using system Charset rather than UTF-8
- Closed
-
CMS-10238 translation tooling reads and writes files using system Charset rather than UTF-8
- Closed
-
ESSENTIALS-994 several code paths handle resources using system Charset rather than UTF-8
- Closed