Hello, I doubt you can compile a list of all charsets supported by the various (national) linux distributions and versions (and installed runtime packages). Especially not for OpenJDK which can be much less restrictive in picking supported (non enterprise) distributions.
And I also wonder why it is needed, if a locale is not known just fall back to a sane default. The OpenJDK should define a reasonable list (especially for compact profiles) and not declare to support all platforms fully. Gruss Bernd Xueming Shen <xueming.s...@oracle.com> schrieb am Fr., 31. Juli 2015 00:35: > On 07/30/2015 03:01 PM, David Holmes wrote: > > On 31/07/2015 1:41 AM, Xueming Shen wrote: > >> On 07/30/2015 01:37 AM, Volker Simonis wrote: > >>> On Thu, Jul 30, 2015 at 9:51 AM, Alan > >>> Bateman<alan.bate...@oracle.com> wrote: > >>>> > >>>> On 30/07/2015 06:21, Xueming Shen wrote: > >>>>> : > >>>>> > >>>>> Each platform has a list of "supported locale/encoding". All these > >>>>> encodings/charsets need to be in > >>>>> base module for that particular platform, to support the jvm to > >>>>> start (in > >>>>> a particular locale/encoding) > >>>>> under module system. The charsets in our repository can be > categorized > >>>>> into different groups, solaris/ > >>>>> linux specific, windows specific and IBM specific and couple that are > >>>>> shared by different platforms). > >>>>> The idea here is to build all those platform-specific charsets into > the > >>>>> base module for that platform. > >>>> Right, and furthermore, we should be able to build a compact1 image > >>>> or just > >>>> an image with the java.base module and it should be able to start on > >>>> platforms when running with a supported locale/encoding. I think the > >>>> main > >>>> issue we've had is establishing that list, hence it had to be > >>>> extended a few > >>>> times. > >>>> > >>> The change looks fine. > >>> > >>> But what about the 'supported locale/encoding' list. Is there a > >>> published 'official' version of this list for Oracle/OpenJDK and how > >>> is it maintained. > >> > >> I meant to say "all the supported/native locale+encoding" of the > >> platform/OS. If we have those > >> charsets in our repository, they all need go into the base module. > > > > Now I'm confused again. Do the platforms we officially support have set > lists of such locales/encodings? If so getting our list correct seems > trivial. If not, then how can we support an unknown target?? > > > > it's a "known" target. we know the list of the locale/encoding solais > /linux supports and the list > of charsets Java supports. > > -sherman > >
