An SPS can be set up so that Authentic View users can also style text. They do this by selecting a text fragment in Authentic View and setting styling properties for the selected text. These styling properties can be pre-defined by you (the SPS designer) or they can be defined by the Authentic View user. In either case, the Authentic View user can be given the option of styling text in Authentic View.
The following text-styling options are available:
|•||Composite Styles: A set of CSS style properties (the Composite Style) is defined on the attribute of an element in the source XML document. By setting this attribute as the Composite Style property-value of a design component, the Composite Style becomes editable with the RichEdit feature of Authentic View. See the section Composite Styles for a description of how this mechanism works.|
|•||RichEdit: If an element is created in the SPS design as a RichEdit component, then the Authentic View user can select text fragments within that element and style it using the RichEdit styling properties of Authentic View. RichEdit enables the Authentic View user to specify the font, font-weight, font-style, font-decoration, font-size, color, background color and alignment of text. See the section RichEdit for details.|
|•||Text State Icons: You (the SPS designer) can create an Authentic View toolbar button and associate this button with an element name. We call such a toolbar button a Text State Icon. When the Authentic View user selects a text fragment in Authentic View and clicks a Text State Icon, the element associated with the Text State Icon is created around the highlighted text (a Text State Icon is enabled only if the schema allows it around the selected text). Consequently, the text formatting defined for this element (in a global template for this element) will be applied to the selected text fragment.|
You can use a combination of all three text-styling options in your SPS.
You should note the following points:
|•||All three text-styling options depend on and require styling-related elements and/or attributes to be present in the XML document. Consequently, the schema on which the SPS is based must allow the required elements and/or attributes at the hierarchical levels on which they are required.|
|•||Text styling applied by the Authentic View user will appear in both Authentic View as well as the output formats.|
|Note:||The styling options listed above are derived from styling properties stored in the XML file and are additional to styling properties assigned in the SPS.|
© 2019 Altova GmbH