SAMSUNG-PRINTER-EXT-TC

TEXTUAL-CONVENTION

Auxiliary sheets are added by the printing system and are not part of the actual print job. Examples include error pages and banner pages. This textual convention is used to specify the information content of auxiliary sheets.

TEXTUAL-CONVENTION

Auxiliary sheets are added by the printing system and are not part of the actual print job. This attribute uniquely identifies an auxiliary-sheet, which includes the types jobErrorSheet and printerStartupSheet. 'printerStartupSheet' is a sheet printed shortly after power-up when the device is ready. Typical startup pages include test patterns and/or printer configuration information. 'jobErrorSheet' is a sheet printed with error messages generated during the printing of a job-result-set that is to be printed with the hardcopy output of that job-result-set, and should be printed on an ending sheet of the job-result-set, or some similar sheet. These sheets are not a part of any job-copy. If no error messages have been generated, the device need not print an extra page. The default for this page type should be 'On'. The following Auxiliary-sheet-package types can be specified either for a job component (job result set or job copy) or document (document result set or document copy). For now, only the jobSetStart package has been enumerated. 'jobSetStart' - Auxiliary-sheet starts each result-set Sometimes referred to as a jobBanner sheet 'jobSetEnd' - Auxiliary-sheet at the end of a result set

TEXTUAL-CONVENTION

This enumeration indicates the type of channel that is receiving jobs. This enumeration is being added to the IETF Printer MIB. This is an IETF type 2 enum.

TEXTUAL-CONVENTION

These attributes specify the printing performance / economy mode setting.

TEXTUAL-CONVENTION

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional Printer MIB Extension object groups, specified in a bit-mask. The current set of values (which may be extended in the future) is given below: 1 : scmPrtBaseGroup -- 2**0 2 : scmPrtGeneralGroup -- 2**1 4 : scmPrtInputGroup -- 2**2 8 : scmPrtOutputGroup -- 2**3 16 : scmPrtChannelGroup -- 2**4 32 : scmPrtInterpreterGroup -- 2**5 64 : scmPrtInputAliasGroup -- 2**6 128 : scmPrtGeneralAuxSheetGroup -- 2**7 256 : scmPrtGeneralProdSpecificGroup -- 2**8 512 : scmPrtAuxPackageGroup -- 2**9 1024 : scmPrtChannelProdSpecificGroup -- 2**10 2048 : scmPrtInterpProdSpecificGroup -- 2**11 4096 : scmPrtInterpPCLGroup -- 2**12 8192 : scmPrtInterpPCLProdSpecificGroup -- 2**13 16384 : scmPrtMediumTypeSupportedGroup -- 2**14 Usage: Conforming management agents shall ALWAYS accurately report their support for SCMI Printer MIB Extensions object groups.

TEXTUAL-CONVENTION

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional IETF Printer MIB object groups, specified in a bit-mask. The current set of values (which may be extended in the future) is given below: 1 : prtGeneralGroup -- 2**0 (mandatory) 2 : prtResponsiblePartyGroup -- 2**1 4 : prtInputGroup -- 2**2 (mandatory) 8 : prtExtendedInputGroup -- 2**3 16 : prtInputMediaGroup -- 2**4 32 : prtOutputGroup -- 2**5 (mandatory) 64 : prtExtendedOutputGroup -- 2**6 128 : prtOutputDimensionsGroup -- 2**7 256 : prtOutputFeaturesGroup -- 2**8 512 : prtMarkerGroup -- 2**9 (mandatory) 1024 : prtMarkerSuppliesGroup -- 2**10 2048 : prtMarkerColorantGroup -- 2**11 4096 : prtMediaPathGroup -- 2**12 (mandatory) 8192 : prtChannelGroup -- 2**13 (mandatory) 16384 : prtInterpreterGroup -- 2**14 (mandatory) 32768 : prtConsoleGroup -- 2**15 (mandatory) 65536 : prtAlertTableGroup -- 2**16 (mandatory) 131072 : prtAuxiliarySheetGroup -- 2**17 262144 : prtInputSwitchingGroup -- 2**18 Usage: Conforming management agents shall ALWAYS accurately report their support for IETF Printer MIB object groups.

TEXTUAL-CONVENTION

This enumeration indicates the type of interpreter that is receiving jobs. This enumeration is being added to the IETF Printer MIB. This value is an IETF type 2 enumeration.

TEXTUAL-CONVENTION

Controls interpreter behavior when the requested Media Type is not currently available. * The values 'other' and 'unknown' are deprecated for conforming implementations. * 'abortJob' will cause the interpreter to abort the job with an appropriate error condition. * 'ignore' will cause the job to be printed on the default media as specified by scmPrtInterpInputIndexDefault OR scmPrtInterpPaperSizeDefault OR any available media deemed appropriate by the implementation. No adjustment will be made to the image size. Exact semantics of this setting are product specific. * 'interactWithOperator' will cause the printer to interact with the operator to determine what to do. For example, display a message at the operator console requesting the desired media. The semantics of this policy vary among different products and environments. * 'ignoreAfterTimeout' will cause the job to be ignored same as 'ignore' above, but not till after scmPrtInterpErrorPolicyTimeout expires.

TEXTUAL-CONVENTION

Paper size classes for a printer.

TEXTUAL-CONVENTION

This attribute specifies the size of this medium by means of a pre-defined value. The medium size specified in this manner may be one of the standard sizes to which object identifiers have been assigned in ISO/IEC 10175 (DPA), or another applicable standard, or for which a value has been created. Enumerations for DPA defined medium sizes are derived by adding 1000 to the ISO/IEC 10175 enumerations. SCMI defined enumerations start at 10.

TEXTUAL-CONVENTION

Offset stacking types further refining that specified by the object prtOutputOffsetStacking in the Printer MIB. - offsetOnJob means that each job is offset but copies within the job are not offset. - offsetOnJobAndCopy means that there is an offset on job and copy boundaries.

TEXTUAL-CONVENTION

This Textual Convention enumerates possible staple positions. The staple positions enumerated are relative to the physical layout of the finishing device. The observer is on the front side of the finisher which is defined as for sheets passing through the finisher. The 'front' side is the side from which staples are pushed. The physical corners of the finishing device are specified by designating the corner of the finisher where a portrait long-edge fed sheet with english/left-to-right text is stapled as staplePosCorner1, and then the other corners are numbered in a counter-clockwise direction with the observer on the front side of the finisher. 'staplePosCorner1', 'staplePosCorner2', 'staplePosCorner3', and 'staplePosCorner4' indicate a single staple in the specified corner. This object does not specify the angle of the staple, e.g. 90, 45 or zero degrees. 'stapleEdge...' indicates multiple staples on the edge specified. 'stapleEdge12' is the edge which include Corner1 and Corner2. The current set of values (which may be extended in the future) is given below: 1 : staplePosCorner1 -- 2**0 2 : staplePosCorner2 -- 2**1 4 : staplePosCorner3 -- 2**2 8 : staplePosCorner4 -- 2**3 16 : stapleEdge12 -- 2**4 32 : stapleEdge23 -- 2**5 64 : stapleEdge34 -- 2**6 128 : stapleEdge14 -- 2**7

TEXTUAL-CONVENTION

TEXTUAL-CONVENTION

Controls interpreter behavior when the requested Page Size is not currently available. * The values 'other' and 'unknown' are deprecated for conforming implementations. * 'abortJob' will cause the interpreter to abort the job with an appropriate error condition. * 'ignore' will cause the job to be printed on the default media as specified by scmPrtInterpInputIndexDefault OR scmPrtInterpPaperSizeDefault OR any available media deemed appropriate by the implementation. No adjustment will be made to the image size. Exact semantics of this setting are product specific. * 'interactWithOperator' will cause the printer to interact with the operator to determine what to do. For example, display a message at the operator console requesting the desired media. The semantics of this policy vary among different products and environments. * 'useNearestAndAdjust' will cause the job to be printed on the nearest available media (as described below). The interpreter will adjust the image size (by scaling and centering) to fit. * 'useNextLargerAndAdjust' will cause the job to be printed on the next larger available media (as described below). The interpreter will adjust the image size (by scaling and centering) to fit. * 'useNearest' will cause the job to be printed on the nearest available media (as described below). No adjustment will be made to the image size. * 'useNextLarger' will cause the job to be printed on the next larger available media (as described below). No adjustment will be made to the image size. * 'ignoreAfterTimeout' will cause the job to be ignored same as ignore' above, but not till after scmPrtInterpErrorPolicyTimeout expires. In the above descriptions, nearest size is defined as the one closest in area to the requested size. The next larger size is the one that is at least as large as the requested size in both width and height and is smallest in area. To adjust the page means to scale the page image (if necessary) to fit the medium, then center the image on the medium.

TEXTUAL-CONVENTION

This Textual Convention enumerates plex modes which may be supported by a printer or interpreter. A plex mode specifies whether pages are to be printed one-sided or two-sided, as well as the content orientation between consecutive pages. For the ScmPrtPlex TC, the following definitions apply: 'one-sided' - Print on only one side of each sheet. 'two-sided' - Print on both sides of each sheet. 'simplex' - The document pages are to be oriented so as to condition them for one-sided printing. 'long-edge-bind' - The document pages are to be oriented so as to condition them for two-sided printing, bound along the length (the longer edge) of the physical page. 'short-edge-bind' - The document pages are to be oriented so as to condition them for two-sided printing, bound along the width (the shorter edge) of the physical page. ScmPrtPlex's representation is bit-encoded, so that a device may show multiple plex modes supported. The value zero shall mean notSpecified. The following ScmPrtPlex values and meanings are defined: 0x001 simplex, one-sided 0X002 simplex, two-sided 0x010 long-edge-bind, one-sided 0x020 long-edge-bind, two-sided 0x040 short-edge-bind, one-sided 0x080 short-edge-bind, two-sided The following describes the relationship of the scmPrtPlex modes to DPA, PostScript and PCL. DPA: In DPA, Plex specifies whether the page images of the output document are to be conditioned for (eventual) one-sided or two-sided printing, and also specifies whether the relative orientation between consecutive page-images is to be altered. In DPA, the Plex modes specified are named 'Simplex', 'Duplex' and 'Tumble'. However, 'Duplex' would more accurately be named bindLongEdge, and 'Tumble' would more accurately be named bindShortEdge. As written in DPA, 'Whether the images are portrait or landscape, the binding edge is parallel to: the y axis for 'duplex', and the x axis for 'tumble'. This last observation is important for understanding when to use 'tumble'. If the binding edge of the document is along the y-axis, the plex is 'duplex', whether the orientation is portrait or landscape, and if the binding-edge is along the x-axis, the plex is 'tumble', whether the orientation is portrait or landscape. In DPA, a separate attribute, 'Sides', specifies 1-sided or 2-sided printing. In DPA, the value of this attribute may also be used by the presentation processes of some document formats to determine whether or not to print certain designated pages (e.g. the extra blank pages needed in two-sided printing to cause sections to begin on the righthand side of a book, or recto page). The following enumerations are relevant to DPA: simplexOneSided, simplexTwoSided, bindLongEdgeOneSided, bindLongEdgeTwoSided, bindShortEdgeOneSided, bindShortEdgeTwoSided. PostScript: In PostScript, the keys 'duplex' and 'tumble' are booleans which specify relative orientation between consecutive pages, and to the number of sides printed. If 'Duplex' is False, pages are printed 1-sided, i.e. 'simplex'. If 'Duplex' is True, pages are printed 2-sided. (For most PostScript interpreters, only when 'Duplex' is set to True) 'Tumble' specifies how the page images on opposite sides of a sheet are oriented with respect to each other. If 'Tumble' is False, the default user spaces of the two pages are oriented such that the highest value of y in the two spaces lie along the same edge of the media. Informally, a Tumble value of False produces output suitable for binding on the left or right. When the default user space is set to a portrait 'pagesize', setting Tumble to false is the same as using the ScmPrtPlex attribute longEdgeBind. When the default user space is set to a landscape 'pagesize', setting Tumble to false is the same as using the ScmPrtPlex attribute shortEdgeBind. If 'Tumble' is True, the default user spaces of the two pages are oriented such that the highest value of y in the two spaces lie along opposite edges of the media. Informally, a Tumble value of True produces output suitable for binding on the top or bottom. When the default user space is set to a landscape 'pagesize', setting Tumble to true is the same as using the ScmPrtPlex attribute shortEdgeBind. When the default user space is set to a landscape 'pagesize', setting Tumble to true is the same as using the ScmPrtPlex attribute longEdgeBind. The following ScmPrtPlex enumerations are relevant to PostScript: bindLongEdgeOneSided, bindLongEdgeTwoSided, bindShortEdgeOneSided, bindShortEdgeTwoSided. Typically (ie, for a Portrait default user space): OneSided maps to the duplex boolean set to false TwoSided maps to the duplex boolean set to true bindEdgeLong maps to the tumble boolean set to false bindEdgeShort maps to the tumble boolean set to true PCL: In PCL, the attributes simplex, duplex long-edge-binding, and duplex short-edge-binding, along with content orientation, landscape or portrait, detail the number of sides to be printed, content orientation, and relative orientation between consecutive pages. The PCL model matches that of DPA. The following ScmPrtPlex enumerations are relevant to PCL: simplexOneSided, bindLongEdgeTwoSided, bindShortEdgeTwoSided.

TEXTUAL-CONVENTION

These attributes specify the output quality of the printed document. Some printers have programmatically controlled output quality. This attribute allows the user to specify the level of output quality desired from printers. The following standard values are defined: - 'draft' means lowest quality available on the printer. Uses include increasing the printer's speed and saving toner. - 'normal' means normal or intermediate quality on the printer. - 'high' means highest quality available on the printer.

TEXTUAL-CONVENTION

This Textual-Convention enumerates special modes for 80 character screen dumps onto A4 size paper, which is usually 77 characters wide. This function is useful when printing the 80 characters per line width of computer displays. The PrintScreen mode enables characters to be printed as shown on the display when PrintScreen is executed from the host. When mode850 or mode852 is set, the following is done: - Symbol set value changed to PC-850 or PC-852. with the current Symbol set value being stored. - A4 size horizontal printable area expanded to being 80 characters wide. When the special mode is returned to Off, the following is done: - Symbol set value returned to the stored SymbolSet Value. - A4 size horizontal printable area returned to being 77 characters.

TEXTUAL-CONVENTION

This Textual-Convention enumerates which tray switching declaration mechanism is used.

OBJECT-IDENTITY

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE

OBJECT-TYPE

Dummy - DO NOT USE