Translation tool Legacy<->OpenStep for Vista?(SOLVED)

[Lestradae]

Hi,

does anyone know if there is any kind of translation tool that can transfer legacy into OpenStep and vice versa under Vista or at least Windows?

Would be grateful for a tip or two.

Greetings

L

[JensAyton]

The question doesn’t make sense. Do you mean XML to OpenStep format for property lists?

“Legacy” in the context of Oolite generally refers to the old scripting system, as opposed to JavaScript. Legacy scripts can be expressed in any property list format.

In the context of property lists, thOpenStep format is a legacy format, while XML is the new format; however, the OpenStep format is recommended for Oolite because it’s easier to work with by hand.

This is easier to keep track of if you keep in mind that most of the property lists you deal with when making OXPs are not scripts. Thinking of them as scripts leads to confusion. Don’t do it. (A script is a series of instructions to be carried out by the computer, while most of the property lists – such as shipdata.plist – contain descriptions, not instructions.)

[Lestradae]

Hi Ahruman,

thanks for the clarification.

Do you mean XML to OpenStep format for property lists?

Yes, this is what I mean. I know that there are tools for this on Macs (from you, actually), but it would be really practical to have a Vista-compatible translator so that I don't have to pester people back and forth for translating things. I can do it by hand myself, but that's rather longwinded activity.

This is easier to keep track of if you keep in mind that most of the property lists you deal with when making OXPs are not scripts. Thinking of them as scripts leads to confusion. Don’t do it. (A script is a series of instructions to be carried out by the computer, while most of the property lists – such as shipdata.plist – contain descriptions, not instructions.)

Thanks again for the definition. You explained that already to me once, but I managed to confuse the terms again

So, still searching for that Vista translator ... XML <-> OpenStep ... format-wise.

[Thargoid]

Most of the translation can be done with simple search and replace, plus optionally a little bit of reformatting. It's just knowing what the equivalents are for each tag.