Oolite Bulletins

Seems like verifier disregards "like_ship" keys and reports errors where there are none. (e.g. "Required keys (model, roles) missing from dictionary") Also, says that "is_template" is an unknown key. Correction: Both 1.73.4 and trunk report "is_template" as un...

Nevermind. Found out that there was one "<true/>" too many. Not to many "<true/>", as it belonged to the missing one with: "smooth". It was just misplaced. I assume because something was pasted in between. Actually, I moved the "smooth" beneath the "mode...

Well, I have one possible approach.
First, check the whole file as a string and verify its structure using various rules.

That's what I did with my tool. It checks if there are strings, inegers and such where they should be. (I might finish it soon.. just need some coffee)

Heh.. me first, me first.

Anyway, stray "true" broke the verification.. IMO that shouldn't happen.

Nevermind.

Found out that there was one "<true/>" too many.

OXp Verification breaks with this log: ***** Exception while running verification stage "Checking shipdata.plist": <NSException 0x1fd9798> NAME:NSInvalidArgumentException REASON:Tried to add nil value for key 'YES' to dictionary INFO:{ai_type = nullAI.plist; forward_weapon_type = WEAPON_PU...

I'm too lazy to leave.

Besides, there still are some OXPs around here that I haven't downloaded yet.

I cannot fix bugs in my own OXPs because Lestade has overwritten all my bug fixes with OSE. I really really really don't get it... If he modified your work..: a) doesn't that mandate HIM to do the bug-squishing, and not you? I mean, if it is changed, then it is not your original work and you are no...

If I create an oolite ship and for whatever reason, I wish other OXPs not to include it, I have the right to manage that. I can only think of petty reasons. If someone created the ship and I downloaded it and used it, then it is OK... On the other hand, if I downloaded it and used it, then it is NO...

Damn!

Is CR/LF (or new line, enter, return...) valid string in both OpenStep (I call it ASCII, according to elitewiki...) and XML? To the best of my knowledge, yes. (And don’t. OpenStep format is not ASCII-encoded, it’s UTF-8. You’ll note that the EliteWiki page on property lists does not mention ASCII.)...

Is CR/LF (or new line, enter, return...) valid string in both OpenStep (I call it ASCII, according to elitewiki...) and XML? I've seen "\n" used instead CR/LF in both formats, and I've seen real CR/LFs being used in both formats as part of string (texts in missiontext.plists). My guess is ...

Well, whaddayaknow.. Oolite does parse binary format...

Now I only need to break the code...

Honestly, I don't see what possible use I can have with binary-formatted plists, if they are not parsed by Oolite (and I'm on win-PC platform), but thanks for the link. There was a plist editor for windows there.

This started as a reply in one of the treads, but went off topic big time. That's why I'm straiting a new thread. My issue is this: I'm making a translator code that will automatically translate plists XML to ASCII and ASCII to XML. It is pretty much done, but there are still some details that I'm n...