At 2009-02-18T17:45-0500, Nat Hager III wrote: > It's just sometimes, they seem so insistent on forcing ifp-only down > your throat it's hard-to-believe you can actually get around it.
iPhones have hard wired internationalization in a few respects, but 24 hour time is a separate switch. However, if you want km you have to tell it you're in a country other than the USA (I pick Australia), but sucks to be you if you want ISO8601 date formats (I've mailed Apple a few times about this, if you have an iPhone please use their feedback form at http://www.apple.com/feedback/iphone.html). Similarly, phone setting formats are hard wired in rather annoying non-internationalized ways and you can't for love or money have +X XX XX XX XX XX (i.e. internationalized string followed by the phone number broken into 2 digit blocks so it's easy to read and remember). The non-US format choice is to just squash it all together without spacing. All this is rolled into a generic internationalization framework so that client applications will change between metric and US customary based on your set internationalization. I'm not sure if there's a way to program around it (I've not written such code for the iPhone yet). Paul -- End dual-measurement, let's finish going metric! http://gometric.us/
