What is the use-case for this library compared to Xcode - Export for Localization and import? about localizedstringkit HOT 1 OPEN

That's a great question 😄

There are a few reasons. The first is that when this library was actually written, it was when Xcode 6 was the latest version and it would be another 4 years before this functionality arrived in Xcode. The second is that when this functionality arrived, we looked at it, but didn't move to it since our translation team depended on .strings files at the time (despite their obvious disadvantages over more powerful formats).

Both of these issues are non-issues now, so we could switch in theory. However, there is one significant advantage that this library has: It can be connected up to our CI system to ensure that strings have been exported in every PR. We don't run a risk of missing strings that way.

Going forward, we will absolutely be moving to a better localization format and will be updating this tool to support it, but there is no timeline for that yet.

One more thing: If the Xcode functionality works better for you (especially since it gives a more powerful format), please continue using it. We aren't trying to say this is the best way at all. It's just what we use and we wanted to make it available for anyone who had the same issues we have. We know those don't affect everyone as each code base is unique.

from localizedstringkit.