<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - New intl-numberformat.js test fails on many Linux platforms"
href="https://bugs.webkit.org/show_bug.cgi?id=154530#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - New intl-numberformat.js test fails on many Linux platforms"
href="https://bugs.webkit.org/show_bug.cgi?id=154530">bug 154530</a>
from <span class="vcard"><a class="email" href="mailto:darin@apple.com" title="Darin Adler <darin@apple.com>"> <span class="fn">Darin Adler</span></a>
</span></b>
<pre>There are two separate questions here:
One is how to make WebKit and JavaScriptCore properly choose a default locale for each platform. I don’t know what the right way to do that is for Linux in general. Fixing that for WebCore is what <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Intl.Collator uses POSIX locale (detected by js/intl-collator.html on iOS Simulator)"
href="show_bug.cgi?id=152448">bug 152448</a> is all about. But it almost certainly needs to be fixed for direct JavaScriptCore use too. At least I know it does need to be done on the Apple platforms. So we may need a bug to track that.
The other is how to make the test harness set a consistent language so that tests are reliable, rather than being sensitive to the language the user running the tests happens to prefer. That's something we need to address separately. There are lots of calls to setenv in various test tools, so it could be as simple as doing a setenv("LANG") in the right place for the appropriate platforms in some of the test tools.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>