I do not recommend going without localized resources, however, because even if your application will only ever be available in one localization, it is likely to use localized resources from the various frameworks installed on your system, and CFBundle/ NSBundle need to be able to determine what localization your application is running in so as to be able to select those. I don't have complete visibility here and might be completely wrong, but the frameworks should choose localized resources based on user settings, not on the language of the app. At least the most prominent (Date & Time, number format, sort order, authentication) seem to be handled that way. The frameworks needs to know which language of the user-defined order was chosen (supported) by the application. Say, your language order is German, French, English. Then, if an app supports all languages, it would choose German and framework objects (which support all, too), should be in German. Another app though supports English only; therefore, it uses an English GUI, and the frameworks -- which still support all with the very same user preferences -- should use English this time. Otherwise, you would get an extremely ugly Windoze-like behaviour of, say, German alerts in French GUI. In a decent environment, that is not done (unless there really is no other way) :)
I do not recommend going without localized resources, however, because even if your application will only ever be available in one localization, it is likely to use localized resources from the various frameworks installed on your system, and CFBundle/ NSBundle need to be able to determine what localization your application is running in so as to be able to select those. I don't have complete visibility here and might be completely wrong, but the frameworks should choose localized resources based on user settings, not on the language of the app. At least the most prominent (Date & Time, number format, sort order, authentication) seem to be handled that way.
I do not recommend going without localized resources, however, because even if your application will only ever be available in one localization, it is likely to use localized resources from the various frameworks installed on your system, and CFBundle/ NSBundle need to be able to determine what localization your application is running in so as to be able to select those.
Ondra and Douglas,