HPOS 3.5 Using -extended-features

8 HP Output Server 3.5

Using -extended-features

About mapper.xml file

</translation>

</mapping>

<attribute-ref name="sides" value="2"/>

<attribute-ref name="plex" value="duplex" optional="true"/>

<feature-ref name="sides" value="TwoSidedLongEdge"/>

</translation>

</mapping>

<attribute-ref name="sides" value="2"/>

<attribute-ref name="plex" value="tumble"/>

<feature-ref name="sides" value="TwoSidedShortEdge"/>

</translation>

</mapping>

</class>

3. Complex feature <--> attribute mapping

In this style of mapping, the sub features present in the attributes of HP Output Server are mapped to the

features in the cap ticket.

Examples

• <class>

<!--

This is a complex mapping from feature to attribute. The value of the

feature must be parsed to determine if it will set one or two attributes.

Additionally, the feature value comes from a sub-feature of the feature.

-->

<sub-feature namespace="pwg" name="DocumentFormat" type="regex">

<!--

Sub-features indicate that the feature is a structure and this is the way

to address the value of a particular field in the feature.

-->

<!--