DRY String Localization with Interface Builder
Victor Pavlychko

D Casserly Sorry for the late reply, something messed up with my notifications. Anyway, that used to be the case but the .strings has been default for a long while now and I guess I never considered the strings file an issue since we came up with an automated solution for that early on. We’ve since moved to .xliff (soon after it was introduced). Either through Xcode or in our case through a script using `xcodebuild -exportLocalizations`. Xcode 9 fills in the gaps here finally with .stringsdict support which was missing before.

But yeah, there are many different ways to solve this.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.