Missing many locales support on AIX platform

[Bhaktavatsal R Maram]

Hi Alan,

Thank you for your response. I'm happy that my patch was attached. But, I don't see attachment. So, I inlined patch which contain diffs from 2 changesets in mail text. If a Jira bug is opened for this issue, probably I can attach complete and consolidated patch there.

At high level, I'm adding following charsets to standard charset in java.base. For this, I have to change IBM943C and IBM942C from source to template to handle java package and aliases. It is also required to add codepage 932 as alias for IBM942C because both are one and same.

Big5, Big5_HKSCS, GB18030, IBM942, IBM942C, IBM943, IBM943C, IBM950, IBM970, IBM1124, TIS_620


These are default charsets for some of locales supported by Operating System (AIX). Since these are not available in standard charset, JDK can't be used in those locale even if they are available in jdk.charset module (java -version fails).

I've followed some of the discussions around this in community and understand that default charset of a locale should be made available in java.charset module by using stdcs-* mechanism. On Linux, they were added to java.base in similar way. As it is missing for AIX, I've added them to enable JDK support for more locales.
 

Thanks,
Bhaktavatsal Reddy

-----Alan Bateman <Alan.Bateman at oracle.com> wrote: -----
To: Bhaktavatsal R Maram <bhamaram at in.ibm.com>, core-libs-dev at openjdk.java.net
From: Alan Bateman <Alan.Bateman at oracle.com>
Date: 04/13/2018 03:52PM
Subject: Re: Missing many locales support on AIX platform

On 13/04/2018 10:35, Bhaktavatsal R Maram wrote:
> Given that patch is big, I am sending patch as attachment again after changing some mail settings. Hopefully, it will make to community this time.
Your patch was attached.

If I read it correctly, you've switched IBM943C to a template but there 
aren't additional aliases so this part is effectively a no-op, is that 
right? For IBM932C, you've moved it to be template and added several 
aliases.

The rest is AIX specific and I hope the SAP engineers that maintain the 
AIX port can help you. It may be that you are testing with locales that 
aren't supported configurations for the AIX port in OpenJDK. As a 
general point, we try to keep as many of the exotic and multibyte 
charsets out of java.base. They are of course still available to 
applications via the API and the jdk.charsets service provider module.

-Alan