Thanks for your work @danielmartin !!

I like the idea but I think this change doesn't get along with spgenstrings (which is part of the "package"). It doesn't crash but look at the result of running spgenstrings on SPExample.m:

Localizable.strings:

"(Context for variable string)variable" = "variable";

"(First hello world)Hello world!" = "Hello world!";

"(Followers label description##one)%d people is following you" = "Just one person is following you";

"(Followers label description##other)%d people is following you" = "%d people are following you";

"(Friends counter##one)variablePlural" = "variablePlural";

"(Friends counter##other)variablePlural" = "variablePlural";

"(Second hello world)Hello world!" = "Hello world again";

OtherTable.strings:

"(Another text from another table)Hello world!" = "Hello world from another table!";

"(Another variable text from another table)variableTable" = "variableTable";

I changed the example to work with NSLocalizedString and check how it works with genstrings from Apple and this is the result:

$ genstrings -o . SPExample.m
Bad entry in file SPExample.m (line = 41): Argument is not a literal string.
Bad entry in file SPExample.m (line = 42): Argument is not a literal string.
Bad entry in file SPExample.m (line = 46): Argument is not a literal string.
Bad entry in file SPExample.m (line = 47): Argument is not a literal string.

I don't like it failing miserably, but I don't like it just working without informing the user. Would you mind editing spgenstrings to emit a warning (with line number and file name, if possible) when it finds a key, text or table name that is not a literal string?

If you want to test your changes in spgenstrings you only have to run the project, it already has the arguments to analyze SPExample.m and update the strings files you already know 😄

@danielmartin Wow! I just noticed you changed spgenstrings already, you're my hero! 😄 Is that all or does it need more changes?

@sergiou87 I think that's enough. The change does warn the user if a non-literal string is found in keys, contexts, or table names (indicating file name and line number, same information as in genstrings). The diff is very local to spgenstrings's scanner.

I think there's still a problem when there are comments inside SPLocalizedString parameters (there is a TODO comment about that that comes from the first release, I think), but this is a matter of a future pull request. 😄

Yeah, the problem is it's based on parsing the code files manually, rather than using something like libclang (which actually understands Objective-C… and Swift when it's needed 😄 ). I started writing a tool in Python based on libclang but I couldn't get enough free time to finish it 😕

Anyway, thank you very much for your contribution, I'll add you to the README file too, and I hope I can get you a 🍺 some time!! 😄