When I run my application, my iPhone/iPad simulator only gives me 6 language choices (English, German, Japanese, Italian, Spanish, and Hungarian). After having Googled this it seems like there should be at least 18 language choices available.
I’ve reinstalled Xcode 4.3.1, and installed the iOS 5.1 simulator, and it has the same issues, same languages.
Does anyone know where these languages are defined, and why a simulator wouldn’t have all available options? Google and the Apple Dev forums are of no help.
Here’s a screenshot:

Update: I decided to install the slightly older 5.0 simulator (instead of 5.1), and whenever I’m using the 5.0 simulator it appears I have all of the languages. If I switch back to the 5.1 simulator I still only have the 6 languages shown in the above screenshot.
Based on information in the answer posted the user named idz, located in this same question, I was able to figure out how to fix this.
I was using 5.1, I had to install the previous version of my simulator (5.0), then locate the language directories from 5.0 and copy them into the proper location for 5.1, and then restart the iPhone Simulator. Here are some detailed steps:
/Applications/Xcode-4.3.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator5.0.sdk/System/Library/PrivateFrameworks/Preferences.framework/English.lproj. Copy all of the .lproj folders that you find here./Applications/Xcode-4.3.3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator5.1.sdk/System/Library/PrivateFrameworks/Preferences.framework/Hardware -> Version -> 5.1. Now when you go to choose the language for the simulator you should have all of the languages available that you copied over from the 5.0 folder.Alternatively some have said that you might be able to fix this by simply uninstalling the Xcode SDK and reinstalling it, but I’ve found this way to be much faster.
I submitted a bug report to Apple for this, and after a week had no response. I’ve directed them to this page for the fix to the problem, but I’m still not sure how this happened in the first place.