[Originally published on Macoscope’s blog.]
In order to fully take advantage of the fact that an application is available worldwide, one must first localize it properly. Depending on the application, the region, and a host of other factors, the process of localization itself may change and require different amounts of resources.
Apple provides iOS developers with a number of different tools and utilities that significantly reduce the burden cost of localization. Using the
NSLocalizedString macro together with
.strings files is (and rightly so) considered a standard nowadays, but relying solely on the two can sometimes lead to suboptimal solutions. In this post I would like to demonstrate a way to handling localized strings that have to deal with plural forms.