11

I have english, Japanese, korea Localizable.strings file. I cannot load some word from korea file. I have checked spelling, capital letter or small letter also. It is correct. I have cleaned project, reset simulator and delete app on device also. It is not working for some words. May I know how to do?

Jageen
  • 6,345
  • 2
  • 37
  • 56
Khant Thu Linn
  • 5,905
  • 7
  • 52
  • 120
  • Could you please show that words. – Jageen May 01 '15 at 05:55
  • My app has support for 10 languages, including Korean, Chinese and Japanese, and we never had this kind of problem. Could you show your Localizable.strings file and the code where you are calling this specific word? – FormigaNinja May 01 '15 at 06:05

4 Answers4

15

A common problem is this: If there is an error in your localisable.strings file, anything after that error will be just ignored. The line that you are checking may be fine; if the line 10 lines above is broken, it won't work. If that is the problem, for example the item in the next line isn't going to work either.

Cleaning project, reset simulator, delete app on device, are all not going to do anything for you.

gnasher729
  • 51,477
  • 5
  • 75
  • 98
  • It is soooo bad. I have commented out all and check only that word. It is okay. Is there any easy way to detect which is broken? – Khant Thu Linn May 01 '15 at 07:44
  • In my case, I had tried to add a comment to localizable.strings file as `#comment` and all the translations after that comment was not working (I don't know why I added that line in the first place). I changed it to `//comment` and it worked. – Okhan Okbay Apr 09 '18 at 19:36
  • Thank you very much. after spending 2 days to find the reason. xCode not presenting warning during build. – Ofir Malachi Jul 18 '23 at 11:46
1

Also it may be some words, that repeats. If two same keys in Localizable.strings - it may be work not properly.

Also i found, that continue key make some bugs, so i changed it to CONTINUE. HINT something like continue_question and anything that contains continue - makes same bug.

It seems like there are another words like this. Also got to say, that i didn't delete app and clean build folder due to debag this. In Xcode 7.3 it was't necessary.

Nike Kov
  • 12,630
  • 8
  • 75
  • 122
  • In my case all other cases did not work at all. And complier does not show any warning/error in Localizable.strings file. Then I have started my key value format as **"key" = "value";** And I found some my stupid mistake which was in format that was **"key"; = "value";** Note : there was a extra semicolon (*) after key . After removed that I localisation works like a charm. Very easy way to catch your format. Just comment entire file's key value pairs. Then just put a key value and run the code. I think you will get know what is the actual issue. Thanks Guys. – Ravi Jul 10 '17 at 19:45
0

It might also be due to a blank space in one of your empty lines in the Localizable.strings file.

It's tough to spot but you can spot it by looking at which point of the file the strings start to fail localization.

Jonathan Cabrera
  • 1,656
  • 1
  • 19
  • 20
-1

Check or search for # in your localizable.String .if there is any remove it . the key value pairs below the # are not working

SRINIVAS KR
  • 1