System properties

[Xueming Shen]

I tried both 7u4 and 7u6 on my Leopard (I would not expect any 
difference if on Lion), in
en_US.UTF-8 locale, both report the file.encoding as UTF-8, which I 
think is correct.
(it reports US-ASCII if run in C/PROSIX). I don't see a problem here.

Yes, Apple's jdk6 does report MacRoman when run in en_US.UTF-8 locale, 
which I would
assume is problematic.

-Sherman

On 5/21/12 3:35 PM, Michael Hall wrote:
> On May 21, 2012, at 5:13 PM, Xueming Shen wrote:
>
>> Whether or not this is a bug depends on your locale setting.  If your locale is set to C locale,
>> then the US-ASCII is the correct pick, if your locale is using UTF-8 as its encoding (I would
>> assume this should be the default setting), then this property should be UTF-8. Command
>> "locale" tells you your current locale setting and "locale -a" tells you all the choices. I'm
>> still setting/upgrading my leopard, so I can't verify what JDK7 is doing with various locale
>> settings, but I don't see any thing special in prop_md.c...
>   locale
> LANG="en_US.UTF-8"
>
> and a number of LC_ attributes(?) also set to en_US.UTF-8.
> So file.encoding=US-ASCII would be right.
> So this change is a feature not a bug, it now uses the more appropriate locale setting rather than a hardcoded MacRoman?
>
>