Swift v3.0.2

ios_locale_identifiers_feb2017.csv

Playground code to generate

import UIKit

print("localeIdentifier, Description")

let identifiers: NSArray = NSLocale.availableLocaleIdentifiers as NSArray
let locale = NSLocale(localeIdentifier: "en_US")

identifiers.forEach {
    let name = locale.displayName(forKey: NSLocale.Key.identifier, value: $0)!
    print("\($0),\"\(name)\"")
}

@xta is there a specific reason that iOS uses an underscore to separate rather than the standard dash?

@ryanve Yeah it's weird. I forked and replaced with dashes for react-native-i18n and i18n-js.

• iOS locale identifiers XML version
• iOS locale identifiers JSON version
• iOS locale identifiers CSV version
• iOS locale identifiers Markdown table version
• iOS locale identifiers HTML table version
• iOS locale identifiers LaTex table version
• iOS locale identifiers create and insert sql version
• iOS locale identifiers plain text table version

I've wondered the same regarding underscore versus hyphen. Apple documentation refers to both usages, though more recent documentation refers to hyphenation while NSLocale returns underscores. My impression is that initially Apple APIs used underscore which was not up to standard. So they updated their language logic to support handling hyphenation while keeping APIs returning underscore so as to be backwards-compatible so production apps wouldn't break.