After spending too many hours wondering why my document icons weren't showing up under Mac OS X, and finally figuring out that it was caused by a typo in my 'plst' resource, I wrote this utility to help other Mac OS X programmers. Drag a packaged application, or a single-fork application containing a 'plst' resource, or an Info.plist file and drop it on PlistChecker. PlistChecker displays a report listing any problems it found. What PListChecker does: Verifies the UTF-8 encoding. Reports any XML/plist parsing errors. Reports any undocumented top-level keys. Checks the types of the values for most documented keys, and keys within the CFBundleDocumentTypes array. Reports keys recommended by TN 2013 that are missing from the plist. These checks are based on my understanding of what a plist should look like, and should not be taken as gospel. PListChecker does not examine InfoPlist.strings files. What's New: Version 1.3 adds the following: The report text is now antialiased when running on OS X. The About box is movable. When dealing with an unbundled application with a 'plst' resource, PListChecker now verifies that the PList type and creator codes match the application's actual type and creator codes, and that the value of CFBundleIconFile is a number. There is a specific error message if a standard key is typed with incorrect capitalization. The keys LSUIElement and LSHasLocalizedDisplayName are recognized. The key CFBundleExecutable is now on the recommended list, though it probably doesn't really serve a purpose for unbundled applications. |  |
| 
