On 7/30/15 4:55 PM, Bernd wrote:
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) di
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
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 wrote:
On 30/07/2015 06:21, Xueming Shen wrote:
:
Each platform has a list of "supported locale/encoding". All
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 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 m
On 07/30/2015 01:37 AM, Volker Simonis wrote:
On Thu, Jul 30, 2015 at 9:51 AM, Alan Bateman 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 suppo
On Thu, Jul 30, 2015 at 9:51 AM, Alan Bateman 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
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 repo
On 30/07/2015 04:54, Xueming Shen wrote:
Here is the webrev to add those "missing" charsets. The assumption
back then was that the linux platform has
successfully migrated to the "utf-8 default" world.
http://cr.openjdk.java.net/~sherman/8132459/
This looks okay to me.
-Alan
On 7/29/15 9:53 PM, David Holmes wrote:
Hi Sherman,
On 30/07/2015 1:54 PM, Xueming Shen wrote:
Here is the webrev to add those "missing" charsets. The assumption back
then was that the linux platform has successfully migrated to the
"utf-8 default" world.
This process seems somewhat ad-hoc,
Hi Sherman,
On 30/07/2015 1:54 PM, Xueming Shen wrote:
Here is the webrev to add those "missing" charsets. The assumption back
then was that the linux platform has successfully migrated to the "utf-8
default" world.
This process seems somewhat ad-hoc, what are we using to determine which
cha
Here is the webrev to add those "missing" charsets. The assumption back
then was that the linux platform has
successfully migrated to the "utf-8 default" world.
http://cr.openjdk.java.net/~sherman/8132459/
thanks,
Sherman
On 7/28/15 8:22 PM, Jonathan Lu wrote:
Hi Alan, Sherman,
Thanks for ta
On Wed, Jul 29, 2015 at 5:53 PM, Xueming Shen wrote:
> On 7/29/15 2:23 AM, Volker Simonis wrote:
>>
>> On Tue, Jul 28, 2015 at 11:11 PM, Xueming Shen
>> wrote:
>>>
>>> Volker,
>>>
>>> If fine with you I will re-open the gb18080 specific bug and fix it by
>>> adding the gb18030 into
>>> stdcs-sol
On 7/29/15 2:23 AM, Volker Simonis wrote:
On Tue, Jul 28, 2015 at 11:11 PM, Xueming Shen wrote:
Volker,
If fine with you I will re-open the gb18080 specific bug and fix it by
adding the gb18030 into
stdcs-solaris/linux and aix (does aix have a gb18030 locale?).
In general I'm fine with your
On Tue, Jul 28, 2015 at 11:11 PM, Xueming Shen wrote:
> Volker,
>
> If fine with you I will re-open the gb18080 specific bug and fix it by
> adding the gb18030 into
> stdcs-solaris/linux and aix (does aix have a gb18030 locale?).
In general I'm fine with your proposal. But I don't understand how
Hi Alan, Sherman,
Thanks for taking a look!
I understand and totally agree with improving module separation.
Another quick test was just done on my Linux box for all available locales, and
found several more which will cause
ExceptionInInitializerError on JDK9, but worked with JDK8.
ar_AE
ar_A
yes, gb18030 needs to be in linux/unix std-solaris/unix as well.
-sherman
On 07/28/2015 09:51 AM, Volker Simonis wrote:
Hi Jonathan, Alan,
this is a known problem and we've already discussed it intensively.
Please have a look at:
8081674: EmptyStackException at startup if running with extend
Volker,
If fine with you I will re-open the gb18080 specific bug and fix it by adding
the gb18030 into
stdcs-solaris/linux and aix (does aix have a gb18030 locale?). And keep the
8087171 open
for a more general solution, such as using iconv for a "IconvCharset"
-Sherman
On 07/28/2015 09:51
Hi Jonathan, Alan,
this is a known problem and we've already discussed it intensively.
Please have a look at:
8081674: EmptyStackException at startup if running with extended or
unsupported charset
https://bugs.openjdk.java.net/browse/JDK-8081674
and:
8087161: Fails to start up initialize syst
On 28/07/2015 10:50, 陆传胜(传胜) wrote:
Hello,
The issue
was found on one of my Linux boxes which uses locale zh_CN.GB18030 by default,
a simple
patch was made to fix it, may I have it reviewed ?
webrev: http://cr.openjdk.java.net/~luchsh/webrev-8132459/
bug: https://bugs.openjdk.java.n
Hello,
The issue
was found on one of my Linux boxes which uses locale zh_CN.GB18030 by default,
a simple
patch was made to fix it, may I have it reviewed ?
webrev: http://cr.openjdk.java.net/~luchsh/webrev-8132459/
bug: https://bugs.openjdk.java.net/browse/JDK-8132459
JBS seems to be
20 matches
Mail list logo
