Localizable.strings files.. in xcode4

Question

In xcode4, (I have used v4.0.1 until now and downloaded v4.0.2 yesterday.) I made Localizable.string files and compiled my project. (As you know, my source code uses NSLocal

Answer 1

Looks like this is an standard message for error reading the strings file.

In my case it was a (json force of habit) colon instead of equal sign:

"key1" = "String1";
"key2" : "String2";
"key3" = "String3";

Changed it to = and everything worked fine.

Answer 2

I had this problem. My fix? Add a newline at the top of the file. Bizarre but it got it working for me.

So instead of at the top of my file having this:

/* comment */
"LOCAL_APP_GRADE" = "Basic"

I had to do:

[newline]
/* comment */
"LOCAL_APP_GRADE" = "Basic"

(Can't get the formatting right - don't type 'newline', just hit return!)

Answer 3

All of the lines in .strings file should end with a semicolon. It worked for me.

Answer 4

Make sure that you have declared string in following format:

"YOUR_STRING_LABEL" = "Your message";

Note: Don't forget Quotation Marks ("), Equals Sign (=) and Semicolon (;) at end.

Answer 5

I'm assuming Xcode 4 here. Double check what it shows for the encoding on each of the Localization.string files in the file inspector. When I was having that error it was due to one of the files being read as Mac Roman instead of UTF-16. Once I changed the encoding the warning went away. What was driving me nuts at first was that the warning was only happening in Xcode 4. Xcode 3 did not give it.

You also have an issue with the formatting of your .string file. All of the lines should end in a semicolon.

"LOCAL_APP_GRADE" = "Basic";
"LOCAL_APP_LAST_UPDATED_DATE" = "2011/04/20";
"LOCAL_MAIN_MENU_TITLE" = "Main Menu"; 

I don't think this is the cause of the warning though. At least I've never seen a warning for it. It usually only manifests itself at runtime when LOCAL_MAIN_MENU_TITLE shows up in app instead of Main Menu. It would be nice if the build process did check for semicolons though. It's easy to miss adding one when editing the files.

Answer 6

My problem was, that I've forgotten ; in one of the lines