Embedded Object Section

It is possible to embed files within other files. In this way, you can for example embed a picture within a text document.

These objects are structured exactly like normal documents. Their data is embedded in the file of the master file. But offsets within their data are relative to the start of the object in the file, not to the start of the whole file! So if an object's data start at offset 00005432 of the master file, an offset of 00004321 within the object data corresponds to offset 00009753 in the master file.

This section consists of one BListL of pairs of longs: the first long is an ID containing the section identifier, the second is the Offset within the file. It is likely that all three sections below need to be present in the shown order.

Identifier Description

46 01 00 10 Offset of the Object Display Section

2A 01 00 10 Offset of the Object Icon Section

44 01 00 10 Offset of the Section Table Offset Section

The Section Table Offset Section is also the start of the embedded object; offsets within it are relative to its location.

Object Display Section

Data Description

B Display as icon (00) or full (01)

Length Object displayed horizontal size

Length Object displayed vertical size

L Unknown; alsways 00 00 00 00 ?

The sizes are the size the object will be displayed with. If the object is displayed as an icon, for example, the size of the icon is put here; if it is cropped and/or scaled, the resulting size is found.

If this is embedded in a Text Layout Inline List, the sizes found here are the same as those in the inline list.

Object Icon Section

Data Description

String Application name

Length Icon horizontal size

Length Icon vertical size

If the object is displayed iconified, the sizes in the Object Display Section and the Text Layout Inline List (if the object is embedded in it) are the same as found here.