System properties

[Mike Swingler]

On May 20, 2012, at 7:50 AM, Michael Hall wrote:

> On May 20, 2012, at 8:08 AM, Andrew Thompson wrote:
> 
>> The USASCII change in particular is going to cause spectacular breakage. Switching the UTF16 endianness is probably going to trip up non BOM using code too. 
> 
> I had just been looking at some native in working with OSType's. It used MacRoman in converting. I didn't think it should of.  I remembered that MacRoman had been the java file.encoding and wondered if it still was. I have no idea myself what impact changing would have but thought the issue worth raising.

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.

Regards,
Mike Swingler
Apple Inc.