On 19/08/2021 07:40, Alan Bateman wrote:
Yes, if there is code that really wants to use the native encoding and run of wide range of JDK releases without the using COMPAT then it can read the value
of native.encoding and use Charset.defaultCharset if the property is not set.
-Alan.
Thanks
On 18/08/2021 22:44, Naoto Sato wrote:
On 8/18/21 2:03 PM, Simon Nash wrote:
I am the developer of a fairly large application that uses file I/O
extensively. In most cases, the charset should be UTF-8 and I have
used an explicit charset parameter on all method invocations where
this applies.
On 8/18/21 2:03 PM, Simon Nash wrote:
I am the developer of a fairly large application that uses file I/O
extensively. In most cases, the charset should be UTF-8 and I have used
an explicit charset parameter on all method invocations where this
applies. In some cases, the charset needs to be
On 18/08/2021 20:49, Naoto Sato wrote:
Hi Simon,
Please post your comments at core-libs-dev mailing list, where the discussion
should take place.
Naoto
My apologies that I am late into the discussion of this JEP.
I am the developer of a fairly large application that uses file I/O
