System properties

[Xueming Shen]

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...

-Sherman

On 5/21/2012 2:39 PM, Michael Hall wrote:
> On May 21, 2012, at 11:28 AM, Scott Kovatch wrote:
>
>> I thought this looked fishy, too. I would have expected UTF-8 for file names, and the default format of text files.
>>
>> Please file a bug.
>
> And Mike Swingler earlier
>
>> What I don't understand is why the encoding is US-ASCII instead of UTF-8. We should definitely not be trying to resurrect MacRoman, because the rest of OS X has basically moved on to UTF-8 or UTF-16.
>>
>> Anyone know why US-ASCII? This is probably worth a bug.
> Just to be sure I"m understanding what is a bug about this.
> I am not filing a bug for what I was thinking which was that this is a change from prior jvm's that may cause broken or incorrect file reading where MacRoman differed from US-ASCII.
> But that UTF-8 or UTF-16 would be more appropriate replacements for the essentially deprecated MacRoman?
> My main question was if differences in System properties in general were subject to verification and testing along the same lines as coding changes or might something change that would have side effects and slip under the radar (No pun intended I assure you).
>
>