If your Localizable.strings file looks like this then you’re probably doing it wrong…
Back in August I presented some best practices for localising your cocoa apps. The presentation centred around my experiences localising my own apps and the realestate.com.au app. I highlighted how using NSLocalizedString properly (or it’s more useful cousin NSLocalizedStringFromTable) can make localisation a lot easier and logical.
The first part of the presentation touched on something most people in the audience could relate too… the most notorious misuses of NSLocalizedString that I’ve seen.
I then went onto explain how NSLocalizedString works.
Towards the end I touched on a custom implementation of NSLocalizedString I had been working on aptly named JCLocalizedString that had a compatible interface with NSLocalizedString but would allow switching the active localisation at run time. JCLocalizedString exists on github in it’s early stages.