Sure Magnus. Thank you for your suggestion. Once am ready with the prototype, I will initiate the infrastructure related discussion to build-...@openjdk.java.net and continue the streamlining of the extended charsets related discussion here.
Thank you, Nasser Ebrahim From: Magnus Ihse Bursie <magnus.ihse.bur...@oracle.com> To: Alan Bateman <alan.bate...@oracle.com>, Nasser Ebrahim <enas...@in.ibm.com>, core-libs-dev@openjdk.java.net, build-dev <build-...@openjdk.java.net> Date: 08/22/2018 02:27 PM Subject: Re: Adding new IBM extended charsets On 2018-08-05 20:38, Alan Bateman wrote: > > As regards the way forward then I think we have to put infrastructure > into the build to make it easy to allow specific charsets be included > or excluded from specific platforms. As things stand, and as have you > have found with your updates to the stdcs-<platform> files, the > charsets are generated to be included in either java.base or > jdk.charsets. We need another input to the configurability to make it > possible to include or exclude so that the main stream platforms do > not have to include the IBM charsets. There are several details around > this, particularly around aliases, but if we can get that done then we > have a lot of flexibility. And when you are ready to discuss the required build changes, please head over to build-...@openjdk.java.net. ;-) The build part of the charset handling is less-than-ideal. I hope we can find a way to clean this up as well, as part of streamlining the included charsets. /Magnus
