[
https://issues.apache.org/jira/browse/DAFFODIL-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454121#comment-17454121
]
Steve Lawrence commented on DAFFODIL-2600:
------------------------------------------
I wonder if this is an actual bug and more than just a diagnostics thing?
For example the XMLTextInfosetOutputter explicitly outputs as UTF-8. So this
must mean that somewhere we aren't be explicit about what encoding we use.
Perhaps we need to be explicit in some other places about ensuring we use UTF-8
encoding
Note that I can reproduce test faliure with with the following command:
{code}
sbt -Dfile.encoding=US-ASCII test
{code}
> Poor diagnostic if UTF-8 not properly set
> -----------------------------------------
>
> Key: DAFFODIL-2600
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2600
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: 3.1.0, 3.2.0
> Reporter: Mike Beckerle
> Priority: Major
>
> A clear diagnostic is needed if, when building daffodil, the UTF-8
> capabilities are not properly setup. This otherwise leads to a long list of
> errors that are not easily interpreted.
> Note that LANG=en_US isn't sufficient. On some systems unicode/UTF-8 is the
> default, on others some other charset for en_US. A portable check here may
> be somewhat challenging, given that different systems have different defaults
> (e.g, Linux MINT, vs. Linux Red-Hat, .... and that's just considering Linux.)
> We know MS-Windows also requires specific UTF-8 configuration. So likely we
> need a test that
> (1) runs very early or first, so that the error message isn't lost in the mix
> (2) checks that UTF-8 behaviors are working properly for Daffodil, regardless
> of how that particular operating system variant must be configured to get
> those settings.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
