PIXEL
DOCK

I like the smell of Swift in the morning…

Posted: October 1st, 2015 | Author: Jörn | Filed under: Objective-C, Swift, Xcode | 6 Comments »

I added some new keys to my Localized.strings files:

"HOME_TEAM" = "Home team"
"AWAY_TEAM" = "Away team"

Then I got this error from Xcode:

Read failed: The data couldn't be read because it isn't in the correct format

It took me a minute but when I found what caused the error I had to smile. I simply forgot the semicolons at the end of each line:

"HOME_TEAM" = "Home team";
"AWAY_TEAM" = "Away team";

Those poor semicolons! Coding in Swift really makes you forget they even existed in the first place 😉

1
Davidsaid at 10:14 am on November 27th, 2015:
Hi Jorn! If you are dealing with the translation of strings, my suggestion is to try a software localization tool with a flexible and user friendly work interface, where you can invite your localization team to work on the translation projects.
2
Jörnsaid at 7:57 pm on November 27th, 2015:
Hi David,

thank you for your comment! Yes, I would definitly use a localization tool for bigger projects. To be honest, this post was only half-serious. Just a little obituary for the semicolon character which seems to go extinct with the advent of Swift…

Best regards,

Jörn
3
Riyan Pratamasaid at 7:54 am on February 24th, 2016:
Bonjour, Joern!
You literally saved my time. I am dealing with this problem few hours, and it turns out into missing semi colons.
Just a little question, you said that you’ll use localization tool for big project. What tool do you use? I am waiting your answer on my email.
Thank you so much.
4
J Smithsaid at 6:01 am on July 5th, 2018:
Thanks for the help!
5
namesaid at 3:26 am on January 14th, 2022:
thanks bro
6
Elon Marksaid at 9:01 am on November 17th, 2022:
This tool can help solve this problem, just select your localizable.strings file, it will help you find out which line format is wrong, it can save a lot of time

[https://localizable.appdevtool.io/](https://localizable.appdevtool.io/)