Hi Eric, eric.bachard wrote:
Thank's for the hint : looks like 10.2 build is stalled because of this. This API change is very annoying, and cases must be treated in the code. In runtime ( not while building ;-) )
Correct, either we treat this at runtime (dynamically loading the function on Mac OS X >=10.3) or we just use the fallback 'en' in case non ISO identifiers will be will be detected.
Do you think it could be possible to implement this part (I'm actually searching if a solution exists in the documentation) ? Provide a 10.2 version is something important, because 10.2 is still used.
The question is how many users are still using 10.2 and is this number big enought to justify effort. As we all know the resources for the Mac OS X port are very limited already so that we should concentrate and set the right priorities.
Kind regards, Tino --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
