This is one of the 2nd-level (inner) formats for the Simis file format used by Microsoft Train Simulator.
As I mentioned last time, the 1st-level (outermost) format has an adjusted header when working with this 2nd-level format; in particular, the file starts with a UTF16-LE byte order mark and the header itself is Unicode text encoded as UTF-16LE. Here it is again:
00000000 FF FE 53 00 49 00 4D 00 49 00 53 00 41 00 40 00 ÿþS.I.M.I.S.A.@.
00000010 40 00 40 00 40 00 40 00 40 00 40 00 40 00 40 00 @.@.@.@.@.@.@.@.
00000020 40 00 @.
The 2nd-level format identifies itself with its own header, unsurprisingly, starting with the text "JINX0", two values indicating the 3rd-level (inner inner) format, the text "t" indicating the Unicode text variety of this format, some padding (6 underscores) and a newline.
00000020 4A 00 49 00 4E 00 58 00 30 00 .. .. .. .. J.I.N.X.0.....
00000030 74 00 5F 00 5F 00 5F 00 5F 00 5F 00 5F 00 0D 00 t._._._._._._...
00000040 0A 00 ..
Those 4 missing bytes are the two characters (a letter then a number) that identify the 3rd-level format used. As text, the header of these files looks like the following line:
SIMISA@@@@@@@@@@JINX0..t______
Now follows the actual data...
Simis Jinx files all store data in a tree-like structure, where each tree node has a type and optional name, and is intermixed with values. In other words, each node's children can be both nodes and values, including a mixture. The structure is marked out by parentheses ("(" and ")") for blocks, with values being raw or quoted strings (generally speaking, any value with no whitespace and no significant symbols - quotes, parentheses - can be left unquoted). Let's get straight to an example from Microsoft Train Simulator, the file GLOBAL\gui.txt:
SIMISA@@@@@@@@@@JINX0I0t______
io_dev ( KEYB 0
io_map ( T "sounddialog" ALL_UP SHIFT_DOWN )
io_map ( ESCAPE "escape" ALL_UP )
io_map ( F1 "Help" ALL_UP )
)
The header has identified this as containing 3rd-level format "I0"; for now, though, let's focus on the 2nd-level format. There is a single root node of type "io_dev" (and it has no name) which contains:
- The value "KEYB".
- The value "0".
- Three nodes of type "io_map", each containing a selection of values but no further nodes.
This is just a simple example, but the format is pretty easy to read (although a little tricky to parse correctly); the 3rd-level format actually defines which node types and what nesting of them is allowed and which values should be where.