Re: Validating dictionary strings file

2011-11-21 Thread Norbert M. Doerner
Thanks for the plutil tip Brian. It's not supposed to be an old style dictionary - it's just a strings file, and I have the whole thing in English and Spanish - the English one loads fine, and the Spanish one doesn't. Unfortunately seeing as plutil thinks it's supposed to be an old style

Re: Validating dictionary strings file

2011-11-21 Thread Gideon King
I have filed a report on this. The problem originally exhibited itself in a strings file that was used for localization, and the error report gave no indication which file it was that had the problem, so I included that in the bug report too. Regards Gideon On 21/11/2011, at 5:05 PM, Joar

Validating dictionary strings file

2011-11-20 Thread Gideon King
Hi, I'm trying to use NSDictionary's dictionaryWithContentsOfFile: method and am getting an error: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary. The entire file is of the format: /*some comment */ Some string = Some other string; Clearly there is

Re: Validating dictionary strings file

2011-11-20 Thread Brian Krent
For validation, try plutil -lint yourFile.plist in the Terminal. Also, use curly braces for dictionaries in old-style ASCII plists.  Brian Krent On Nov 20, 2011, at 11:33 PM, Gideon King gid...@novamind.com wrote: Hi, I'm trying to use NSDictionary's dictionaryWithContentsOfFile: method

Re: Validating dictionary strings file

2011-11-20 Thread David M. Cotter
strings files are not true dictionary files in the sense of NS or CF dictionaries, so you can't treat them like an xml file (plist) you can parse them line by line, manually, if you want to read them in. unless there's another way i don't know about. On Nov 20, 2011, at 9:33 PM, Gideon King

Re: Validating dictionary strings file

2011-11-20 Thread Gideon King
Thanks for the plutil tip Brian. It's not supposed to be an old style dictionary - it's just a strings file, and I have the whole thing in English and Spanish - the English one loads fine, and the Spanish one doesn't. Unfortunately seeing as plutil thinks it's supposed to be an old style

Re: Validating dictionary strings file

2011-11-20 Thread Kyle Sluder
On Sun, Nov 20, 2011 at 10:13 PM, Brian Krent codesamu...@mac.com wrote: For validation, try plutil -lint yourFile.plist in the Terminal. Also, use curly braces for dictionaries in old-style ASCII plists. I tried that before suggesting it; plutil just uses the same plist parser that

Re: Validating dictionary strings file

2011-11-20 Thread Brian Krent
+ (id)dictionaryWithContentsOfFile:(NSString *)path Parameters path A full or relative pathname. The file identified by path must contain a string representation of a property list whose root object is a dictionary.  Brian Krent On Nov 21, 2011, at 12:23 AM, Gideon King gid...@novamind.com

Re: Validating dictionary strings file

2011-11-20 Thread Kyle Sluder
On Sun, Nov 20, 2011 at 10:23 PM, Gideon King gid...@novamind.com wrote: Thanks for the plutil tip Brian. It's not supposed to be an old style dictionary - it's just a strings file, and I have the whole thing in English and Spanish - the English one loads fine, and the Spanish one doesn't.

Re: Validating dictionary strings file

2011-11-20 Thread Stephen J. Butler
On Sun, Nov 20, 2011 at 11:33 PM, Gideon King gid...@novamind.com wrote: Clearly there is some formatting error in the file but it is a rather large file and would take a very long time to manually go through and find the issue - is there some tool available that will tell me where to look in

Re: Validating dictionary strings file

2011-11-20 Thread Gideon King
Thanks for the suggestions guys - I have found the issues by a binary search process (there were some quotes in the wrong places). I'll keep those ideas in my bag of tricks for if I encounter something similar again. Regards Gideon ___ Cocoa-dev

Re: Validating dictionary strings file

2011-11-20 Thread Joar Wingfors
On 20 nov 2011, at 22:49, Gideon King wrote: Thanks for the suggestions guys - I have found the issues by a binary search process (there were some quotes in the wrong places). I'll keep those ideas in my bag of tricks for if I encounter something similar again. Please file a bug report.