You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java's StandardCharsets.UTF_8 does not write a Byte-Order Mark (BOM), while .NET's System.Text.Encoding.UTF8 does include a BOM by default. We have ensured that the IOUtils.CHARSET_UTF_8 does not include a BOM to match Java, and as part of #1018 we've added an internal Support class to allow for using StandardCharsets.UTF_8, but we need to review all usage of System.Text.Encoding.UTF8 to determine if it should be replaced with StandardCharsets.UTF_8 or IOUtils.CHARSET_UTF_8 (whatever best matches the corresponding Java Lucene code) to avoid BOM issues.
The text was updated successfully, but these errors were encountered:
I have reviewed usages of Encoding (most commonly Encoding.UTF8), and determined that most usages do not need to be changed. The following cases do not result in a BOM being generated:
Is there an existing issue for this?
Task description
Java's
StandardCharsets.UTF_8
does not write a Byte-Order Mark (BOM), while .NET'sSystem.Text.Encoding.UTF8
does include a BOM by default. We have ensured that theIOUtils.CHARSET_UTF_8
does not include a BOM to match Java, and as part of #1018 we've added an internal Support class to allow for usingStandardCharsets.UTF_8
, but we need to review all usage ofSystem.Text.Encoding.UTF8
to determine if it should be replaced withStandardCharsets.UTF_8
orIOUtils.CHARSET_UTF_8
(whatever best matches the corresponding Java Lucene code) to avoid BOM issues.The text was updated successfully, but these errors were encountered: