Code: Select all
[plist.parse.foundation.failed]: Failed to parse /Users/jayton/Library/Application Support/Oolite/AddOns/Orb.oxp/Config/shipdata.plist as a property list using Foundation. Retrying using home-grown parser. WARNING: the home-grown parser is deprecated and will be removed in a future version of Oolite. XML parser error: Found non-key inside <dict> at line 1239 Old-style plist parser error: Malformed data byte group at line 1; invalid hex
The home-grown parser bit: currently Oolite tries to use Foundation, then falls back on a custom XML property list parser. This was introduced a while back, when GNUstep under Windows had problems with them. This is no longer the case, so we intended to remove the custom parser. However, it turns out that the custom one accepts some malformed plists – notably, the ones with the problem mentioned above – so it will be kept around at least into the next major version. However, it will eventually be removed to reduce code complexity, so if your OXP causes a message like this in the next version of Oolite, fix it.
I’m still considering the idea of using a single plist parser on all platforms. This won’t be in the next release, but the work done to provide error messages will make it simpler.