<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thanks Philippe,<div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><span class="" style="float: none; display: inline !important;">Good find, </span><div class="">You can make a pull request and we can get our continuous integration servers to start building that and testing your change – that is probably the easiest way to get validation on your tests and changes.</div><div class="">There are a few issues however with your test that might be worth considering. Comments inline…</div></blockquote>… </div><div class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="">Building a CLI tool will use the objective-c Foundation in the system so that wont use your freshly built swift-corelibs-foundation. So that means we have a bug in the objc side if this is actually happening on Darwin (which is a completely different issue…) That should be a radar against Foundation and I definitely think that may very well be a bug… </div></div></div></blockquote></div><div class=""><div class=""><div class=""><div class=""><br class=""></div></div></div></div><div class=""><div class="">I have been filling a radar <a href="https://bugreport.apple.com/web/?problemID=36107307" class="">https://bugreport.apple.com/web/?problemID=36107307</a></div><div class="">I do think you are right it's a bug in the Objc Foundation… and trying to solve it in "swift-corelibs-foundation" was a mistake :) </div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class=""><blockquote type="cite" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class=""><div class=""><div class="" style="margin: 0px; font-stretch: normal; font-size: 9.5px; line-height: normal; font-family: Menlo; color: rgb(189, 178, 160); background-color: rgb(0, 58, 93);"><span class="" style="font-size: 12px;"> <span class="" style="color: rgb(118, 194, 255);">setlocale</span>(<span class="" style="color: rgb(0, 177, 255);">LC_ALL</span>,<span class="" style="color: rgb(171, 69, 71);">"fr_FR”</span>)</span></div></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">This change will set the locale globally for the rest of the process, you probably want to make sure to reset the locale back to it’s original state.</div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>Setting the locale globally was just a temporary test.</div><div><br class=""></div><div>But i do think that it triggers a serious question: Should all your tests be ran on all the available locales? </div><div>You will certainly find a smarter solution …</div><div><br class=""></div><div>Benoit</div><div><br class=""></div><div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div></div></body></html>