You need to localize the project first and then use NSLocalizedString.
You can find a helpful article here, written by @MarcoSantarossa, that can give you some excellent tips on how to handle localization with Swift.

You need to localize the project first and then use NSLocalizedString.
You can find a helpful article here, written by @MarcoSantarossa, that can give you some excellent tips on how to handle localization with Swift.

I made changes based on your suggestions. Now it works perfect !

Another issue is that I don't know what these strings below stands for, and I haven't met them yet , so it is not localized.

Hey @L1cardo, I want to merge your PR into Pock because I know how better it could be if more localizations will be added.
Sadly, I have to ask you to refactor your code in a way that, if Apple changed NSLocalizedString structure, we'd not need to mess around the project to fix all cases.

What do you think about something like this?

extension String {
    var localized: String {
        return NSLocalizedString(self, comment: self)
    }
}

Waiting for your refactor, will be merged in the next release! 🎉

How about now ? This is the best I can do .