plutil doesn't catch faulty .strings file
plutil doesn't catch faulty .strings file
- Subject: plutil doesn't catch faulty .strings file
- From: Markus Spoettl <email@hidden>
- Date: Mon, 12 Jul 2010 00:42:22 -0400
I came across a strange thing today which I'd like to confirm before I go an report it. I moved a project from iPhone OS 3.1 to iOS 4, compiled it an installed it on an iPhone (3GS) to find some of the localized strings where not translated.
After checking using "plutil -lint" to see if the .strings file was OK (which it confirmed), I went chasing the issue in all kinds of different directions. When I couldn't think of anything else, I went back to look at the .strings file and finally found the culprit:
"This is a" = "bad line";*/
"This is" = "not translated";
everything after the bad line wasn't translated. The .strings file gets compiled of the iPhone (into what I don't know), but that process also didn't output a warning (I assume it involves plutil) - not sure it is supposed to do that.
The funny thing is that the same .strings file used to work perfectly in prior builds.
Is this a known issue?
Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden