Editor-Related Properties

The presentation file itself contains data that provide configuration information for the implementation’s editor.

For example, the presentation can define a set of smart tags for use while editing the particular presentation. Because Smart Tags are stored in a separate part, the presentation object contains the relationship ID of the Smart Tag part.

In a fully functioning OLE server, PresentationML objects can be embedded into OLE containers, during which time a customer can set a zoom scale. This is stored in the file as a percentage called serverZoom.

An internationalized application might support configuring the editor to respect different screen orientations. For example, in regions of the world where Complex Scripts are in use, it is customary to orient the screen right-to-left. As such, a presentation can request the editor reconfigure itself for such usage scenarios.

Finally, due to changes in the file format and functionality (e.g., graphics and text engines), PresentationML introduces some end-user complexity when working collaboratively with other customers using older versions. To help remedy this, an implementation might support a Compatibility Mode, which restricts the functionality exposed by the editor to optimize the output for the best cross-version collaboration story possible. As a result, each presentation needs to opt-into this mode.