To provide a fallback language for NSLocalizedString
, I\'m using this #undef
and #define
in Objective-C:
#undef NSLoca
You will have to do a global function... the other options will cause all sort of problems, such as retrain cycles, or classes classes witch do not inherit from NSObject(that is only subset of the problems) - this will not work at all. yes global function usually are big no! but that is the only way to "override" global function. , Here is a code I use in production, we had few thousands of string, at some point we had to make our app dynamically localized - and this is what we did.
// Global functions for lagacy code
func NSLocalizedString(_ key: String, comment: String) -> String {
return key.localized()
}
func NSLocalizedStringInTable(key: String, tableName: String ) -> String {
return key.localized(using: tableName)
}