On Mon, 11 Jul 2022 at 20:18, 多多氷氷 <[email protected]> wrote: > My next idea was to change the order by which the encoding is inferred to the > behavior introduced by JEP400. This would result in first checking > Console.charset()/sun.stdout.encoding thennative.charset and as a fallback > for JDK16 and lower Charset.defaultEncoding()/file.encoding > > Neil said that best place to discuss a fix to Issue #4261 would be this > mailing list, hence this mail.
Well, there doesn't seem to have been much interest in discussing a fix for this here either! :-\ I think your idea above sounds more useful, also taking into account the new system properties here - https://bugs.openjdk.org/browse/JDK-8283620 and https://git.openjdk.java.net/jdk/pull/8270 That way preferring values of the system properties stdout.encoding > sun.stdout.encoding > native.encoding ? As mentioned in the issue, in some ways it might make sense to pick up overrides to these properties in the launching process eg. `exec.vmArgs`? But that might be something to look at as a later enhancement. Getting the revised system properties lookup into NB15 would be good IMO. Do you want to propose a PR against delivery branch? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
