Add best practices for dealing with localisation

[elland]

Needs some research as well, on possible methods to deal with it. NSLocalizedString() is subpar.

[3lvis]

I mentioned not using a wrapper for NSLocalizedString because it breaks genstrings usage.

http://nshipster.com/nslocalizedstring/

[3lvis]

What do you have in mind?

[onmyway133]

I like the JSON approach https://github.com/tomkowz/Swifternalization

[elland]

This seems interesting. Will take a closer look tomorrow if time allows. 👍

[3lvis]

This was suggested as well.

import Foundation

extension String {
    func localized() -> String {
        return self.localizedWithComment("")
    }

    func localizedWithComment(comment:String) -> String {
        return NSLocalizedString(self, tableName: nil, bundle: NSBundle.mainBundle(), value: "", comment: comment)
    }
}

[3lvis]

So far I would go for having a tool that would generate static keys for every key in a localization file.

[elland]

I'd like that. No issues with typos.

[3lvis]

• Localize requesting app permissions. InfoPlist.strings (http://stackoverflow.com/questions/25736700/how-to-localise-a-string-inside-the-ios-info-plist-file)
• Pluralization

[designatednerd]

This is addressed in the updated style guide in #118