Beware that genstrings is going to overwrite existing strings files. By default, the strings file will be called Localizable.strings. The -o argument specifies the output directory where the. m files in your project, you can invoke it, for example, like this:įind. strings files with one entry per unique localizable string key. Second, these macros get picked up by the genstrings tool that creates strings files you can then translate. It's a lot shorter than NSBundle's localizedStringForKey:value:table. First off, it makes the code easier to read.
The point of using those macros is twofold.
All of them use NSBundle's localizedStringForKey:value:table: method to do the heavy lifting. There are three more lesser-known variants of it: NSLocalizedStringFromTable, NSLocalizedStringFromTableInBundle, and NSLocalizedStringWithDefaultValue. We're going to focus on strings in code in this article.Īt the heart of string localization is the macro NSLocalizedString. String localization comes in two different flavors: strings in code and strings in nib files and storyboards. Since this issue is all about strings, we're going to take a look at the topic of string localization. Localizing apps into multiple languages comes with a variety of different tasks.
0 kommentar(er)
