RE: RFR: 8214533 IBM-29626C is required for AIX default charset

2019-01-28 Thread Ichiroh Takiguchi
Januar 2019 14:13 To: Baesken, Matthias Cc: build-dev ; ppc-aix-port-dev d...@openjdk.java.net>; core-libs-...@openjdk.java.net; Alan Bateman Subject: RE: RFR: 8214533 IBM-29626C is required for AIX default charset Hello. I'm very sorry. It's my fault. EUC_JP class w

RE: RFR: 8214533 IBM-29626C is required for AIX default charset

2019-01-28 Thread Lindenmaier, Goetz
ag, 28. Januar 2019 14:13 > To: Baesken, Matthias > Cc: build-dev ; ppc-aix-port-dev d...@openjdk.java.net>; core-libs-...@openjdk.java.net; Alan Bateman > > Subject: RE: RFR: 8214533 IBM-29626C is required for AIX default charset > > Hello. > > I'm very sorry

RE: RFR: 8214533 IBM-29626C is required for AIX default charset

2019-01-28 Thread Ichiroh Takiguchi
core-libs-...@openjdk.java.net Subject: Re: RFR: 8214533 IBM-29626C is required for AIX default charset Hello Alan. Could you review the fix again ? Bug:https://bugs.openjdk.java.net/browse/JDK-8214533 Change: https://cr.openjdk.java.net/~itakiguchi/8214533/webrev.01/ I added IBM29626C charset as standard w

RE: RFR: 8214533 IBM-29626C is required for AIX default charset

2019-01-28 Thread Baesken, Matthias
dk.java.net>; core-libs-...@openjdk.java.net > Subject: Re: RFR: 8214533 IBM-29626C is required for AIX default charset > > Hello Alan. > > Could you review the fix again ? > > Bug:https://bugs.openjdk.java.net/browse/JDK-8214533 > Change: https://cr.openjdk.java.ne

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2019-01-15 Thread Alan Bateman
On 15/01/2019 00:51, Ichiroh Takiguchi wrote: Hello Alan. Could you review the fix again ? Bug:    https://bugs.openjdk.java.net/browse/JDK-8214533 Change: https://cr.openjdk.java.net/~itakiguchi/8214533/webrev.01/ I added IBM29626C charset as standard way. Please give any suggestion and quest

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2019-01-14 Thread Ichiroh Takiguchi
Hello Alan. Could you review the fix again ? Bug:https://bugs.openjdk.java.net/browse/JDK-8214533 Change: https://cr.openjdk.java.net/~itakiguchi/8214533/webrev.01/ I added IBM29626C charset as standard way. Please give any suggestion and question. Thanks, Ichiroh Takiguchi IBM Japan, Ltd.

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2018-12-14 Thread Ichiroh Takiguchi
Hello Alan. I opened JDK-8215333 for Charset filtering issue [1]. I cannot wait until JDK-8215333 is closed. Is it possible to put IBM-29626C charset with standard way ? [1] https://bugs.openjdk.java.net/browse/JDK-8215333 Thanks, Ichiroh Takiguchi On 2018-12-10 21:21, Ichiroh Takiguchi wrote:

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2018-12-10 Thread Ichiroh Takiguchi
Hello Roger, Magnus and Alan. I may need to put alias information into charsets file. stdcs-xxx cannot handle this information... Still AIX needs IBM-29626C charset for default encoding... I appreciate if you give me further suggestions. Thanks, Ichiroh Takiguchi On 2018-12-10 20:50, Alan Bate

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2018-12-10 Thread Alan Bateman
On 10/12/2018 11:01, Magnus Ihse Bursie wrote: On 2018-12-07 21:20, Roger Riggs wrote: Hi, It is a nice feature that charsets are selected at build time using the stdcs-xxx files. This change breaks that pattern and embeds os specific information in more than one place. That does not seem li

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2018-12-10 Thread Magnus Ihse Bursie
On 2018-12-07 21:20, Roger Riggs wrote: Hi, It is a nice feature that charsets are selected at build time using the stdcs-xxx files. This change breaks that pattern and embeds os specific information in more than one place. That does not seem like an improvement. Is there any alternative? I

Re: RFR: 8214533 IBM-29626C is required for AIX default charset

2018-12-07 Thread Roger Riggs
Hi, It is a nice feature that charsets are selected at build time using the stdcs-xxx files. This change breaks that pattern and embeds os specific information in more than one place. That does not seem like an improvement.  Is there any alternative? Thanks, Roger On 12/06/2018 12:05 PM, Ic