HPOS 3.5 Using -extended-features

10 HP Output Server 3.5
Using -extended-features
About mapper.xml file
<!--
This mapping is a combination of a translation and an equivalency. As
above,the sub-feature format and the attribute input-document-format
represent the same thing in the different domains, so a translation is
needed. The value of the sub-feature charset and the attribute
character-set represent the same concept and the values are equivalent.
-->
<equivalence>
<attribute-ref name="character-set"/>
<feature-ref name="ContentFormat">
<sub-feature-ref name="charset"/>
</feature-ref>
</equivalence>
<translation>
<attribute-ref name="input-document-format" value="text"/>
<feature-ref name="ContentFormat">
<sub-feature-ref name="format" value="text/plain"/>
</feature-ref>
</translation>
</mapping>
</class>
<class>
<!--
This class maps from one feature with two sub-features to two attributes.
-->
<attribute name="printer-x-resolutions-requested" units="dpi"
type="integer"/>
<attribute name="printer-y-resolutions-requested" units="dpi"
type="integer"/>
<feature namespace="pwg" name="PrinterResolution">
<sub-feature name="CrossFeedDir" type="integer">
<!--
The units are specified as an element here since the units come from a
different sub-feature of the feature. The value-of attribute of the
element indicates where to find the values.
-->
<units value-of="PrinterResolution/Units"/>
</sub-feature>
<sub-feature name="FeedDir" type="integer">
<units value-of="PrinterResolution/Units"/>