[
https://issues.apache.org/jira/browse/DAFFODIL-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461730#comment-17461730
]
Mike Beckerle commented on DAFFODIL-2612:
-----------------------------------------
Don't we tell people that the setup must have UTF-8 capability?
Perhaps we should somehow detect the lack there-of and exit with a non-zero
exit code.
> Integration tests fail with non UTF-8 LANG
> ------------------------------------------
>
> Key: DAFFODIL-2612
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2612
> Project: Daffodil
> Issue Type: Bug
> Components: CLI, Debugger
> Affects Versions: 3.2.1
> Reporter: Steve Lawrence
> Priority: Minor
>
> The CLI debugger sometimes outputs non-ascii characters when outputting a hex
> dump. Two integration tests checks for these non-ascii characters:
> *
> org.apache.daffodil.debugger.TestCLIdebugger.test_3258_CLI_Debugger_infodata
> *
> org.apache.daffodil.debugger.TestCLIdebugger.test_CLI_Debugger_utf16_encoding
> With LANG set to an ASCII encoding, those non-ascii characters are output as
> question marks, and the integration tests fail. To reproduce, run the
> following
> {code:java}
> $ export LANG=en_US.US-ASCII
> $ sbt IntegrationTest/test{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
