Localizable.strings corrupted?

Question

I'm trying to include the internationalization of my application, and only for testing purposes I added a simple line in the file Localizable.string.

This is my whole file:

"Test locale" = "Test locale"

And when I try run my application I get this error:

Localizable.strings:0: error: validation failed: The data couldn’t be read because it has been corrupted.

I've tried changing the "Text Encoding" to UTF-16 but nothing resolved.

Fulfil

here is a library that might help you to localize project github.com/dipkasyap/DGLocalization – Childbed

Answer 1

If this is your whole file, add a semicolon at the end. Change it to:

"Test locale" = "Test locale";

Malva

Learning iOS first time with swift comming from Android, this is actually a really annoying mistake... – Dowie

Answer 2

To get more detailed informations you can use the Property List utility from the command line:

plutil -lint <your_strings_file>.strings

the -lint switch is for checking the syntax. If you have an error you'll get line number and more informations, and in general better directions on how to fix the issue.

Graehme

Thanks, exactly what I needed. Way too big of a file to check by hand. – Warhol

Is there a way to integrate this command into the Xcode build ? – Pemberton

Never tried, but this is what you can try: you can add a run script phase in "build phases" and, in this phase, call a script that checks all of your .strings files. You can drag the script phase on top of the others (or drag the others down) in order to execute tour script pre-build. it you set XCode -> Preferences -> Building -> Build options "Continue building after errors" then the build stops if the script fails. – Graehme

In order to stop the process and fail the build you can simply terminate your script with an exit code other than zero. As an example if something goes wrong you can use "exit 1". – Graehme

If plutil -lint reports "OK", does not necssarily mean that there are no errors. For example I had the problem that there were unescaped quotation marks within my strings, but the Linter said the file was OK. So I would say you can trust plutil -lint if it reports errors but not if it reports OK. – Virg

It's sickening that Xcode itself doesn't show any line numberings for these errors and you have to run an external tool :/ – Primula

Answer 3

You can verify your Localizable.strings file with this script:

https://github.com/dcordero/Rubustrings

Gremlin

Answer 4

In my case, it was like this:

/* Comment for Very Long Sentence */
"Very Long Sentence Very Long Sentence Very Long Sentence Very Long Sentence " =;
"Very Long Sentence Very Long Sentence Very Long Sentence Very Long Sentence ";

(Notice the ' = ; ' instead of ' = ' at the end of the first line)

Samovar

Answer 5

In my case it was brackets inside string — I needed to add slash before \".

Led

Answer 6

I've made a little script to check whole folders .strings files using plutil.

https://github.com/CarlesEstevadeordal/check_strings

Gilroy

A simple command is enough: find . -name '*.strings' -exec plutil -lint {} \; – Pasture

Answer 7

There can be multiple reasons for this:

1. Semicolon is missing at the end.
2. Multiple semicolons at the end.
3. " within the message which should be escaped by \".
4. Extra character after semicolon.
5. Invalid white space in the file.
6. Other invalid characters in the file.
7. Merge conflict characters in the file!

<<<<<<< HEAD, ======= and >>>>>>>.

Please note that plutil -lint Localizable.strings returned OK for point-2 & 7!

Madaras