JP2015225481A - Program for efficiently editing print setting information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide means for efficiently editing print setting information even for a large amount of print setting items in a print setting editing module provided by a V4 driver.SOLUTION: In a print setting editing module, data maintaining model dependence information is used to efficiently performing print setting editing, thereby deterioration of performance is suppressed.

Description

  The present invention relates to a program for performing print setting processing of a printer driver in a new architecture.

  In Windows (registered trademark) 8 of Microsoft Corporation, a printer driver that operates with a new architecture called a V4 printer driver was introduced. The V4 printer driver is an architecture succeeding the XPS (XML Paper Specification) printer driver provided as the architecture of the V3 printer driver, and uses a print path using an XPS document.

  In this XPS printing pass, what is used to determine the appearance of the printed material is print function information described in an XML format called PrintCapabilities and print setting information described in an XML format called PrintTicket. In order to generate PrintCapabilities and PrintTicket, the V4 printer driver describes a print setting definition file called GPD (Generic Printer Description) and can provide a user with a print setting change function (Non-Patent Document 1). ).

  However, the above GPD only defines options that the user can set for printing, and cannot define numerical values or character strings. For example, when the user performs margin setting, it can provide an option to enable / disable the margin setting function, but it is not possible to define how much margin value (numerical value) is actually set. . Therefore, the OS (Operation System) provides a mechanism that incorporates an extension module for modifying PrintCapabilities and examining PrintTickets into a configuration module having a function for generating PrintCapabilities and PrintTickets from GPD. Printer driver development vendors can add definitions related to parameters such as numerical values and character strings by installing a print setting change module, which is an extension module (Non-patent Document 2).

"PrintTicket and PrintCapabilities Support in Windows Print Drivers" (URL: http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/XPSDrv_PrintTicket.doc) `` Developing v4 Print Drivers v1.3 '' (URL: http://download.microsoft.com/download/1/D/8/1D84C319-0082-4DEB-8708-856EF3CE21C7/developing-v4-print-drivers.docx)

  By the way, the number of print setting items for a multi-function peripheral having many functions is enormous, and it is assumed that the print setting information is enormous. Further, it is assumed that the number of print setting items for designating numerical values and character strings is enormous, and it has been found that the process of the print setting change module has a great influence on the performance of the print process. In this way, the introduction of the print setting editing process that did not occur in the V3 driver has caused a decrease in performance.

  The present invention has been made in view of the above problems. That is, it is an object of the present invention to provide more efficient print setting information editing means in a program for print setting editing processing.

The present invention
In the print setting editing module provided by the printer driver having the print setting capability information described in the XML format and the print setting changing function using the print setting information,
Means for obtaining parameter information from a data file holding model-dependent information;
Means for editing print setting capability information and print setting information using parameter information;
A means for editing the print setting capability information and the print setting information according to the print settings set by the user;
Means for registering the value of the print setting information in DEVMODE;
Means for reflecting the value registered in DEVMODE in the print setting information;
This program is characterized in that these processes are efficiently performed even with a large amount of print setting information.

  According to the present invention, efficient print setting editing processing can be performed, and the performance in the print setting editing processing having a huge function is improved. Therefore, it is possible to reduce the print setting change process performed by the user and the time required for printing.

It is a block block diagram of the hardware and software of a computer system as one Embodiment of this invention. 1 is a block configuration diagram of a print processing system as an embodiment of the present invention. FIG. 6 is an example of an XML format PrintCapabilities that is a print setting used in a driver print processing system according to an embodiment of the present invention. 6 is an example of an XML format PrintTicket that is a print setting used in a driver print processing system according to an embodiment of the present invention. It is an example of the JSON data as model dependence information preserve | saved at DriverPropertyBag as one Embodiment of this invention. It is an example of the definition data regarding DEVMODE described in the XML format as one embodiment of the present invention.

  The best mode for carrying out the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram of a system using a general computer showing an embodiment of the present invention.

  The CPU 101 controls the entire apparatus according to a program stored in the ROM 1021 or the RAM 1022 of the main storage device 102 or the auxiliary storage device 105. The RAM 1022 is also used as a work area when the CPU 101 performs various processes. All the processing of each component in this embodiment is read into the RAM 102 and operates. The auxiliary storage device 105 records an application 1051, a printer driver 1052, an operating system (OS) 1053, and the like. The printer driver 1052 can issue a print instruction to a device having a print function. An input device such as a pointing device 1032 typified by a keyboard 1031 and a mouse / touch panel is a device for the user to give various instructions to the computer through the input I / F 103. The output I / F 104 is an interface for outputting data to the outside, and outputs data to an output device such as a monitor 1041 or a printer 1042. The printer 1042 may be connected not only through the local I / O directly connected but also through the network 1061 connected through the communication I / F 106. Reference numeral 107 denotes a common data system bus, which exchanges data between I / Fs and modules.

  FIG. 2 is a block diagram of the driver printing system. The driver printing system is a system that performs printing using the XPS file format as spool data. The driver printing system operates on the operating system 1053. The print manager 218, the GDI to XPS conversion module 207, the filter pipeline manager 212, and the port monitor 219 are modules included in the operating system 1053. GDI is a graphics component that generates a print image of a printer. The GDI to XPS conversion module 207 has a function of converting data drawn in GDI into XPS data.

  The filter pipeline manager 212 is a module that manages filter print processing, which is a feature of the XPS print path. The port monitor 219 can control communication between the print manager 208 accessing the device and the printer driver, and the printer driver performs print processing via the port monitor 219. The GDI to XPS conversion module 207, the configuration module 208, and the filter pipeline manager 212 are included in the printer driver 1052, but are positioned as modules of the printer driver 1052 provided from the operating system 1053. The configuration module 208 can edit the print setting information using the print setting editing module 2081 provided by the printer driver. The print setting editing module 2081 prints using the property bag 2082 provided by the printer driver. Edit the setting information. The property bag 2082 indicates an area in which data such as model-dependent information and information associated with a print queue is held.

  Each filter of the printer driver 1052 and the filter pipeline manager 212 is stored as the printer driver 1052 in the auxiliary storage device 105 of FIG. The GDI printing application 201 and the XPS printing application 202 are stored as applications 1051 in the auxiliary storage device 105 of FIG. A user uses an input device such as a keyboard 1031 or a pointing device 1032 typified by a touch panel / mouse to display a GDI print application 201 (hereinafter abbreviated as GDI application) displayed on the monitor 1041 of the output device or XPS printing. Print processing is executed from an application program 202 (hereinafter abbreviated as XPS application). The print process is executed by sequentially performing three processes, ie, printer selection, print setting creation, and drawing data conversion.

  First, the printer 1042 to be printed is selected. From the viewpoint of the user, selecting the printer 1042 is synonymous with selecting the printer driver 1052 corresponding to the printer 1042 that executes printing. A print queue is used to select 1052.

  Next, print settings are created. For print setting, first, the application 1051 secures a memory area for print setting in the RAM 1022. Then, the application 1051 calls the configuration module 204 of the printer driver 1052 to create and store print setting data. The GDI application 201 uses a binary DEVMODE structure 203 as print setting data, and the XPS application 202 uses a PrintTicket 204 written in markup language XML. The DEVMODE structure 203 has a standard area defined by the operating system and an extended area uniquely defined by the printer driver. PrintTicket 204 is print setting information described in the XML format, and the description of the standard area and the extended area is divided according to the name space. Since the print setting data includes model-specific information, the configuration module 208 uses the model-dependent file 209 to create print setting data. The DEVMODE structure 203 or the PrintTicket 204 holds the print setting, and the application changes the print setting by directly rewriting the value. Dedicated settings depending on the printer 1042 are set by a user interface of the printer extension 210.

  The printer extension 210 is a kind of the printer driver 1052, but is installed as another application. The printer driver 1052 changes the setting depending on the printer 1042 of the DEVMODE structure 203 or the PrintTicket 204 according to the setting of the user interface. Specifically, the print setting refers to data necessary for printing such as “A4” for the output paper size and “landscape” for the print orientation. Since the print settings of the PrintTicket 204 are described in the XML format, it is easy for the XPS application 202 to directly change and rewrite all the setting values. However, the setting may be changed using the user interface of the printer extension 210. The print settings are created every time a document is printed, but the user interface stores settings such as optional devices of the printer 1042 and environment settings for each user in the registry database 205 of the operating system. When the registry database 205 cannot be used, the user interface stores settings in the application data 220. The default value of the print setting is stored in the registry database 205 by the print manager 218 of the operating system. The registry database 205 and application data 220 are stored in the auxiliary storage device 105. Finally, drawing data is converted. When the print settings are determined, the user executes print processing from the application. When printing from the GDI application 201, drawing data is sent to the GDI to XPS conversion module 207 in the form of a printer driver, and an XPS spool file 206 is created. At this time, the GDI to XPS conversion module 207 calls the configuration module 208 to convert the print setting from the DEVMODE structure 203 to the PrintTicket 204. At the time of conversion, a print setting editing module 2081 is used. When printing from the XPS application 202, there are two methods: an XPS file is generated by the XPS application itself, and an XPS file is generated by the operating system in response to a drawing command from the XPS application. In either method, the XPS spool file 206 is generated during printing.

  When the XPS spool file 206 is generated, the process is passed to the print filter pipeline 211. The print filter pipeline 211 is a mechanism in which printing is performed by passing a plurality of filters. The filter configuration file 216 controls the number and order of the filters. In this embodiment, the filter pipeline manager 212 operating in the print filter pipeline 211 performs processing in the order of the communication filter 213, the layout filter 214, and the renderer filter 215 in accordance with the filter configuration file 216. The number and type of filters differ depending on the configuration of the printer driver 1052. The printing process is performed by passing the XPS spool file 206 to the filter, and the process proceeds when the filter processes the XPS spool file 206 and passes it to the next filter. The communication filter 213 has a function of communicating with the printer 1042 via the print manager 218 and the port monitor, and a function of directly communicating with the printer 1042. The layout filter 214 performs layout-related processing such as magnification change, bookbinding imposition layout, and stamp. The renderer filter 215 renders the XPS spool file 206 and converts it into PDL. The PDL data is managed by a print manager 218 that manages a print processing schedule, and print jobs are successively registered in a queue (queue). When the printer 1042 is ready to print, it transmits through the port monitor 219 in the order registered in the queue. In this way, conversion of print data from the application into PDL data is the main role of the printer driver, and print processing is performed.

  Here, PrintCapabilities and PrintTicket of print setting information used by the printer driver will be described with reference to FIGS. FIG. 3 is an excerpt of a part of PrintCapabilities. In PrintCapabilities, option values that can be set as print settings are described in XML format. Specifically, an Option item written in the Feature is provided to the user as an option. Also, ParameterDef describes definitions related to parameters such as numerical values and character strings. FIG. 4 is an extracted part of the PrintTicket. The print settings actually selected by the user from the above-mentioned PrintCapabilities items are described. A Parameter indicating a numerical value or a character string is described in ParameterInit.

Next, processing of the print setting editing module 2081 will be described. In the present embodiment, it is assumed that the print setting editing module 2081 is written in the JavaScript (registered trademark) language. The print setting editing module 2081 has the following I / F and is called from the OS configuration module 208.
・ CompletePrintCapabilities
ConvertDevmodeToPrintTicket
-ConvertPrintTicketToDevmode
-ValidatePrintTicket
The printer development vendor can implement processing when called from the configuration module 208 in each I / F. When called from each I / F, an access I / F to the PrintCapabilities, the PrintTicket, and the property bag 2082 can be received, and the PrintCapabilities and the PrintTicket are edited using these.

Hereinafter, processing of each I / F will be described using source code.
・ CompletePrintCapabilities
This function is a function that is called when PrintCapabilities are generated or needs to be corrected. In the present embodiment, the following functions are mainly described.

-Addition of ParameterDef-Addition of ParameterRef-Conversion to SubFeature-Editing of effective print area when margin is set The following describes the processing contents in order from the addition of ParameterDef.

  First, when a function of printPrintCapabilities is called, the print setting editing module 2801 generates an object for accessing the property bag 2082 received from the OS. In the present embodiment, an object for accessing the DriverPropertyBag in which the information on the model supported by the driver is stored is prepared.

  The DriverPropertyBag shown in the present embodiment refers to a data group in which model-dependent information is defined, and holds a character string called JSON (Java Script Object Notation) as shown in FIG. JSON is a data format that can be easily used by JavaScript, and is defined in a form that conforms to the definition of DriverPropertyBag. Hereinafter, these data are referred to as additional parameter information. In this item, information to be added as ParameterDef is held in the JSON format. The print setting editing module 2081 converts the additional parameter information into an object and lists the data. Then, the print setting editing module 2081 searches whether each additional parameter information listed is already defined in PrintCapabilities. For the search, XPATH (XML Path Language) is used. XPATH has a function of searching for a specific location in XML, and in this embodiment, searches for a ParameterDef as a search target from PrintCapabilities.

  As a result of searching the additional parameter information, if it is determined that the definition is already defined in the PrintCapabilities, the next additional parameter information is searched without performing the following ParameterDef addition processing.

  If it is determined as a result of searching for additional parameter information that it is not defined in PrintCapabilities, ParameterDef addition processing is performed. Regarding the ParameterDef addition processing, additional parameter information is created in the XMLNode format, and the created XMLNode is added to PrintCapabilities.

  These processes are repeated until all the data groups related to the additional parameter information defined in the DriverPropertyBag are completed. The following is the source code. Also, the GetParamDef function in the source code is a function that searches for ParameterDef using XPATH.

addParameterDef = function () {
// jsonParameterDef is a generated jsonobject by "ParameterDef" Property of the DriverPropertyBag.
if (jsonParameterDef) {
var arrayParameterDef = jsonParameterDef;

// Create New ParameterDef Node.
var newParameterDefNode = rootNode.createNode (1, "psf: ParameterDef", psfNs);
var newPropetyNode = rootNode.createNode (1, "psf: Property", psfNs);
var newValueNode = rootNode.createNode (1, "psf: Value", psfNs);
var newTypeNode = rootNode.createNode (2, "xsi: type", xsiNs);
var newTextValueNode = rootNode.createTextNode ("");

// Add all items defined by DriverPropertyBag to PrintCapabilities as ParameterDefNode.
for (var i = 0, parameterDefLentgh = arrayParameterDef.length; i <parameterDefLentgh; i ++) {
var orgParameterDefName = arrayParameterDef [i] .name;

var parameterDefName = GetSchemaName (orgParameterDefName);
var parameterDefNSPrefix = GetSchemaPrefix (orgParameterDefName);
var parameterDefNSUri = nsObj [parameterDefNSPrefix];

// If already defined ParameterDef by PrintCapabilities,
// Not add parameterDefNode in PrintCapabilities.
if (GetParamDef (pcNode, parameterDefNSUri, parameterDefName)) {
continue;
}

// Append cloned NewParameterDefNode to PrintCapabilities.
var parameterDefNode = newParameterDefNode.cloneNode (true);
parameterDefNode.setAttribute ("name", orgParameterDefName);
var pcParameterDefNode = pcNode.appendChild (parameterDefNode);

// Add items defined by DriverPropertyBag to PrintCapabilities
// as PropertyNode.
for (var j = 0, jsonParameterDefItemLength = arrayParameterDef [i] .item.length; j <jsonParameterDefItemLength; j ++) {
var parameterDefItem = arrayParameterDef [i] .item [j];

// Append cloned NewPropertyNode to ParameterDefNode.
var propertyNode = newPropetyNode.cloneNode (true);
propertyNode.setAttribute ("name", parameterDefItem.name);
var pcPropertyNode = pcParameterDefNode.appendChild (propertyNode);

// Append cloned NewValueNode to PropertyNode.
var valueNode = newValueNode.cloneNode (true);
var pcValueNode = pcPropertyNode.appendChild (valueNode);

// Set cloned NewAttributeNode to ValueNode.
var typeNode = newTypeNode.cloneNode (true);
typeNode.value = parameterDefItem.type;
pcValueNode.setAttributeNode (typeNode);

// Append cloned NewValueTextNode to ValueNode.
var textNode = newTextValueNode.cloneNode (true);
textNode.text = parameterDefItem.value;
pcValueNode.appendChild (textNode);
}
}
}
}

By implementing the above code, it is possible to add a ParameterDef item to PrintCapabilities.

  Next, a process for adding ParameterRef to PrintCapabilities will be described. ParameterRef is an XML attribute described in Option, and it is defined which ParameterDef is related to the Parameter related to the described Option.

  First, additional parameter information described in JSON data is acquired from DriverPropertyBag. In the additional parameter information, “Feature name and Option name to be added” and “Parameter name to be added” are described. Next, in order to determine whether or not a Feature for adding ParameterRef is defined, a search is performed from PrintCapabilities using XPATH. If it is determined that it is not defined, the process ends without performing the parameterref addition process. If it is determined that it is defined, a search is performed from PrintCapabilities using XPATH in order to determine whether the Option to be added is defined. If it is determined that it is not defined, the process ends without performing the parameterref addition process. If it is determined that it is defined, it is determined whether ParameterRef is already defined. If it is determined that it is defined, the process ends without performing the parameterref addition process. If it is determined that it is not defined, an XMLNode of ParameterRef is created using the additional parameter information acquired from DriverPropertyBag and added to the target Option. These are repeated until all of the data related to the additional parameter information defined in the DriverPropertyBag is completed. The following is the source code. Further, the GetFeature function, GetOption function, and GetParameterRef function in the source code are functions for searching for each Feature, Option, and ParameterRef.

addParameterRef = function () {
// jsonParameterRef is a generated jsonobject by "ParameterRef" Property of the DriverPropertyBag.
if (jsonParameterRef) {
var arrayParameterRef = jsonParameterRef;

// Create New ParameterRef Node.
var newParameterRefNode = rootNode.createNode (1, "psf: ParameterRef", psfNs);
var newScoredPropetyNode = rootNode.createNode (1, "psf: ScoredProperty", psfNs);

// Add All Defined DriverPropertyBag As ParameterRefNode.
for (var i = 0, parameterRefLength = arrayParameterRef.length; i <parameterRefLength; i ++) {
var parameterRef = arrayParameterRef [i];
var orgParameterRefFeatureName = parameterRef.featureName;
var parameterRefFeatureName = GetSchemaName (orgParameterRefFeatureName);
var parameterRefFeatureNSPrefix = GetSchemaPrefix (orgParameterRefFeature);
var parameterRefFeatureNSUri = nsObj [parameterRefFeatureNSPrefix];
var arrayParameterRefOption = parameterRef.option;
var featureNode = GetFeature (pcNode, parameterRefFeatureNSUri, parameterRefFeatureName);

// Search FeatureNode of the additional Object.
if (featureNode) {
for (var j = 0, parameterRefOptionLength = arrayParameterRefOption.length; j <parameterRefOptionLength; j ++) {
var p = arrayParameterRefOption [j];
var orgParameterRefOptionName = p.optionName;
var parameterRefOptionName = GetSchemaName (orgParameterRefOptionName);
var parameterRefOptionNSPrefix = GetSchemaPrefix (orgParameterRefOptionName);
var parameterRefOptionNSUri = nsObj [parameterRefOptionNSPrefix];
var optionNode = GetOption (featureNode, parameterRefOptionNSUri, parameterRefOptionName);

// Search OptionNode of the additional Object.
if (optionNode) {
var scoredPropertyName = p.scoredPropertyName;
var parameterRefName = p.parameterRefName;

// If already defined ParameterRef, not add printCapabilities.
if (! GetParameterRef (optionNode, GetSchemaPrefix (parameterRefName), GetSchemaName (parameterRefName))) {

// Append Cloned New scoredPropetyNode to OptionNode.
var scoredPropertyNode = newScoredPropetyNode.cloneNode (true);
scoredPropertyNode.setAttribute ("name", scoredPropertyName);
var optionScoredPropertyNode = optionNode.appendChild (scoredPropertyNode);

// Append Cloned New ParameterRefNode to scoredPropetyNode.
var parameterRefNode = newParameterRefNode.cloneNode (true);
parameterRefNode.setAttribute ("name", parameterRefName);
optionScoredPropertyNode.appendChild (parameterRefNode);
}
}
}
}
}
}
}
By implementing the above code, the ParameterRef item can be added to PrintCapabilities.

  Next, processing for converting a Feature item into SubFeature will be described.

  “SubFeature” refers to a feature existing in the feature, and is used to express a high relationship between the features. In GPD, SubFeature cannot be defined, so in GPD, it is defined as Feature, and in the print setting change module 2081, Feature is converted as SubFeature. Hereinafter, the SubFeature conversion process will be described.

  First, the JSON data is acquired from the DriverPropertyBag. The JSON data describes “feature name to be converted” and “feature name to be added”. Hereinafter, this information is referred to as conversion parameter information. Next, in order to determine whether or not a target Feature to which SubFeature is added is defined, a search is performed from PrintCapabilities using XPATH. If it is determined that it is not defined, the process ends without performing conversion to SubFeature. If it is determined that the feature to be converted is defined, a search is performed from PrintCapabilities using XPATH to determine whether the feature to be converted is defined. If it is determined that it is not defined, the process ends without performing conversion to SubFeature. If it is determined that it is defined, the conversion parameter information acquired from the DriverPropertyBag and the conversion target feature are converted into a form conforming to the definition of the subfeature, and moved to the addition target feature.

  These are repeated until all of the data relating to the conversion parameter information defined in the DriverPropertyBag is completed. The following is the source code. Further, the GetFeature function in the source code is a function for searching for a Feature.

convertSubFeature = function () {
var ConvertToSubfeatureNode = function ConvertToSubfeatureNode (pcNode, moveFeatureNode, parentNode) {
var removedFeature = pcNode.removeChild (moveFeatureNode);
if (removedFeature) {
if (parentNode) {
if (parentNSPrefix == pskPrefix) {
// Change namespace, delete scope.
var attirbuteName = removedFeature.getAttribute ("name");
var nonScopeAttirbuteName = attirbuteName.substring (attirbuteName.indexOf (":") + 1);
var newAttributeName = "";

// When top character string had Scope, I delete it
if (nonScopeAttirbuteName.indexOf ("Job") == 0) {
newAttributeName = pskPrefix + ":" + nonScopeAttirbuteName.replace ("Job", "");
} else if (nonScopeAttirbuteName.indexOf ("Document") == 0) {
newAttributeName = pskPrefix + ":" + nonScopeAttirbuteName.replace ("Document", "");
} else if (nonScopeAttirbuteName.indexOf ("Page") == 0) {
newAttributeName = pskPrefix + ":" + nonScopeAttirbuteName.replace ("Page", "");
} else {
newAttributeName = attirbuteName;
}
removedFeature.setAttribute ("name", newAttributeName);

}
parentNode.appendChild (removedFeature);
}
}
};

// jsonSubFeature is a generated jsonobject by "ParameterRef" Property of the DriverPropertyBag.
if (jsonSubFeature) {
// Convert All items defined by DriverPropertyBag to PrintCapabilities as SubFeature.
for (var i = 0, jsonSubFeatureLength = jsonSubFeature.length; i <jsonSubFeatureLength; i ++) {
// var sf = jsonSubFeature.subFeature [i];
var sf = jsonSubFeature [i];
var parentName = GetSchemaName (sf.parent);
var parentNSPrefix = GetSchemaPrefix (sf.parent);
var parentNSUri = nsObj [parentNSPrefix];
var parentNode = GetFeature (pcNode, parentNSUri, parentName);

// If parentNode is nothing, do not convert SubFeature.
if (parentNode) {
var subfeatureName = GetSchemaName (sf.subfeature);
var subfeatureNSPrefix = GetSchemaPrefix (sf.subfeature);
var subfeatureNSUri = nsObj [subfeatureNSPrefix];
var subfeatureNode = GetFeature (pcNode, subfeatureNSUri, subfeatureName);

// If subfeatureNode is nothing, do not convert SubFeature.
if (subfeatureNode) {
ConvertToSubfeatureNode (pcNode, subfeatureNode, parentNode);
}
}
}
}
}
By implementing the code as described above, PrintCapabilities can be converted from Feature to SubFeature.

  Next, the effective print area changing process described in PrintCapabilities will be described. A property related to an effective print area called “PageImageableSize” is set in PrintCapabilities. In the present embodiment, a process for rewriting the value of PrintCapabilities is performed so that a correct effective print area is obtained when the user performs margin setting.

  First, it is confirmed whether the margin setting is valid in the current print setting, that is, the PrintTicket. If the margin setting is valid, a page imageable size that is a property related to an effective print area is searched from PrintCapabilities. If PageImageableSize is defined, the currently set paper size is acquired. Next, the margin setting values (upper and lower left and right margin values) of ParameterInit designated as the margin setting are acquired. Then, the origin of the effective print area and the print start position is calculated from the paper size and the margin setting value, and is set to PageImageableSize. The following is the source code. Further, the GetParamInit function, GetProperty function, and GetFeature function in the source code are functions for searching ParameterInit, Property, and Feature using XPATH.

setImageableSize = function () {
var jobPrintMarginAdjustmentNode = GetFeature (ptNode, privateNs, "JobMarginAdjust");
if (jobPrintMarginAdjustmentNode) {
// Get jobPrintMarginAdjustmentNode Feature Selected Node.
var marginSelectedOptionNode = jobPrintMarginAdjustmentNode.selectSingleNode ("descendant :: psf: Option");
var selectedOptionAttributeName = marginSelectedOptionNode.getAttribute ("name");
var selectedOptionName = GetSchemaName (selectedOptionAttributeName);

if (selectedOptionName == "MarginAdjust") {
var pageImageableSizeNode = GetProperty (pcNode, pskNs, "PageImageableSize");

if (pageImageableSizeNode) {
var pageImageableAreaNode = GetProperty (pcNode, pskNs, "ImageableArea");

if (pageImageableAreaNode) {
var pageMediaSizeNode = GetFeature (ptNode, pskNs, "PageMediaSize");

if (pageMediaSizeNode) {
// Get pageMediaSizeNode Feature Selected Node.
var selectedOptionNode = pageMediaSizeNode.selectSingleNode (xpath);
var mediaSizeWidthNode = GetScoredProperty (selectedOptionNode, pskNs, "MediaSizeWidth");
var mediaSizeHeightNode = GetScoredProperty (selectedOptionNode, pskNs, "MediaSizeHeight");
var marginTopNode = GetParamInit (ptNode, privateNs, "JobMarginAdjustTop");
var marginBottomNode = GetParamInit (ptNode, privateNs, "JobMarginAdjustBottom");
var marginLeftNode = GetParamInit (ptNode, privateNs, "JobMarginAdjustLeft");
var marginRightNode = GetParamInit (ptNode, privateNs, "JobMarginAdjustRight");

// When I cannot get these parameters, do not set it.
if (! (mediaSizeWidthNode == null) ||! (mediaSizeHeightNode == null) ||! (marginTopNode == null) ||! (marginBottomNode == null) ||! (marginLeftNode == null) ||! (marginRightNode == null)) {
var mediaSizeWidth = mediaSizeWidthNode.text;
var mediaSizeHeight = mediaSizeHeightNode.text;
var marginTop = marginTopNode.text;
var marginBottom = marginBottomNode.text;
var marginLeft = marginLeftNode.text;
var marginRight = marginRightNode.text;

// Set ImageableArea Property
var imageableSizeWidthNode = GetProperty (pageImageableSizeNode, pskNs, "ImageableSizeWidth");
if (imageableSizeWidthNode) {
imageableSizeWidthNode.firstChild.text = mediaSizeWidth;
}

var imageableSizeHeightNode = GetProperty (pageImageableSizeNode, pskNs, "ImageableSizeHeight");
if (imageableSizeHeightNode) {
imageableSizeHeightNode.firstChild.text = mediaSizeHeight;
}

var originWidthNode = GetProperty (pageImageableAreaNode, pskNs, "OriginWidth");
if (originWidthNode) {
originWidthNode.firstChild.text = marginLeft;
}

var originHeightNode = GetProperty (pageImageableAreaNode, pskNs, "OriginHeight");
if (originHeightNode) {
originHeightNode.firstChild.text = marginTop;
}

var ExtentWidthNode = GetProperty (pageImageableAreaNode, pskNs, "ExtentWidth");
if (ExtentWidthNode) {
var ExtentWidth = mediaSizeWidth-marginLeft-marginRight;
if (ExtentWidth <1000) {
ExtentWidthNode.firstChild.text = 1000;
}
else {
ExtentWidthNode.firstChild.text = ExtentWidth;
}
}

var ExtentHeightNode = GetProperty (pageImageableAreaNode, pskNs, "ExtentHeight");
if (ExtentHeightNode) {
var ExtentHeight = mediaSizeHeight-marginTop-marginBottom;
if (ExtentHeight <1000) {
ExtentHeightNode.firstChild.text = 1000;
}
else {
ExtentHeightNode.firstChild.text = ExtentHeight;
}
}
}
}
}
}
}
}
}
By implementing the code as described above, it is possible to change the effective print area when the margin is set.

  In addition to the above, processing for adding capability information of each paper feed stage is performed on the feature relating to the paper feed stage called PageInputBin. However, the means for the addition process uses the same means as described above. Omitted.

  With the above processing, the print settings editing processing of PrintCapabilities is completed.

ConvertDevmodeToPrintticket
This function is a function that is called when the value of DEVMODE is registered in the PrintTicket. In particular, in this embodiment, a process for performing an additional process related to a parameter that cannot be described in the GPD is performed on the print ticket, and a process for reflecting a value related to the parameter registered in the DEVMODE to the print ticket. In the present embodiment, the following functions are mainly described.

-Addition of ParameterInit-Reflect DEVMODE value in ParameterInit The processing contents will be described in order from the addition of ParameterInit.

  First, when a function of convertDevmodeToPrintTicket is called, the print setting editing module 2801 generates an object for accessing the property bag 2082 received from the OS. In the present embodiment, an object for accessing the DriverPropertyBag in which the information on the model supported by the driver is stored is prepared.

  The print setting editing module 2081 converts the additional parameter information into an object and lists the data. Then, the print setting editing module 2081 searches whether each listed information is already defined in the PrintTicket. XPATH is used for the search. In this item, it is searched whether there is a ParameterInit to be searched. Next, it is determined whether a parameter corresponding to the additional parameter information is defined in DEVMODE. In order to define a specific parameter in DEVMDOE in advance, a DEVMODE definition file described in XML format as shown in FIG. 6 needs to be included in the printer driver package. If it is not defined in DEVMODE, the following additional processing is not performed, and the processing proceeds to the next additional parameter information processing. If it is determined that it is defined, the value registered in DEVMODE is acquired. Next, it is checked whether the acquired parameter value is appropriate. The appropriate parameter is scrutinized whether the data format matches the definition of PrintTicket or whether it falls within the range of the maximum value and the minimum value. If it is determined to be inappropriate, it is changed to the default value described in the additional parameter information. In the present embodiment, the process of changing to the default value is performed, but it may be changed to the maximum value or the minimum value.

  Next, when it is determined that the searched ParameterInit exists, the acquired DEVMODE value is reflected in the target ParameterInit value. If it is determined that it does not exist, ParameterInit is added. Regarding the ParameterInit addition process, additional parameter information is created in the XMLNode format, and the created XMLNode is added to the PrintTicket.

  These processes are repeated until all the data groups related to the additional parameter information defined in the DriverPropertyBag are completed. The following is the source code. The GetParamInit function in the source code is a function that searches for ParameterInit using XPATH.

addParameterInit = function () {
var dataType,
defaultValue,
checkParameter = function () {
var maxValue;
var minValue;
var maxLength;
var minLength;

for (var j = 0, jsonParameterDefItemLength = arrayParameterDef [i] .item.length; j <jsonParameterDefItemLength; j ++) {
var parameterInitItem = arrayParameterDef [i] .item [j];
switch (parameterInitItem.name) {
case "psf: DataType":
dataType = parameterInitItem.value; break;
case "psf: DefaultValue":
defaultValue = parameterInitItem.value; break;
case "psf: MaxLength":
maxLength = parameterInitItem.value; break;
case "psf: MinLength":
minLength = parameterInitItem.value; break;
case "psf: MaxValue":
maxValue = parameterInitItem.value; break;
case "psf: MinValue":
minValue = parameterInitItem.value; break;
default:
break;
}
}

if (dataType == "xsd: string") {
if (minLength == null || maxLength == null) {
return;
}

if ((devmodeString.length> = minLength) && (devmodeString.length <= maxLength)) {
}
else {
devmodeString = defaultValue;
}
}

if (dataType == "xsd: integer") {
if (minValue == null || maxValue == null) {
return;
}

devmodeString = devmodeString.replace (/ [\ t] + / g, '');
// I make a decision whether it is numerical value
if (devmodeString.match (/ ^ [-]? \ d + (\. \ d +)? $ /)) {
// numeric value
devmodeString = Number (devmodeString);
if ((devmodeString <minValue) || (devmodeString> maxValue)) {
devmodeString = defaultValue;
}
} else {
// besides numerical value
devmodeString = defaultValue;
}
}
};

// Create JsonObject with the "ParameterDef" Property of the DriverPropertyBag.
var jsonParameterDef = CreateJsonObject (driverPropertyBag, "ParameterDef");
if (jsonParameterDef) {
var arrayParameterDef = jsonParameterDef.parameterDef;

// Create New ParameterInit Node.
var newParameteInitNode = rootNode.createNode (1, "psf: ParameterInit", psfNs);
var newValueNode = rootNode.createNode (1, "psf: Value", psfNs);
var newTypeNode = rootNode.createNode (2, "xsi: type", xsiNs);
var newTextValueNode = rootNode.createTextNode ("");


// Add items defined by DriverPropertyBag to PrintTicket as ParameterInitNode.
for (var i = 0, jsonParameterDefLength = arrayParameterDef.length; i <jsonParameterDefLength; i ++) {
var parameterDef = arrayParameterDef [i];
var orgParameterInitName = parameterDef.name;
var parameterInitName = GetSchemaName (orgParameterInitName);
var parameterInitNSPrefix = GetSchemaPrefix (orgParameterInitName);
var parameterInitNSUri = nsObj [parameterInitNSPrefix];
var ptParameterInitNode = GetParamInit (ptNode, parameterInitNSUri, parameterInitName);

// Get DevmodeMap value
var devmodeString = "";
try {
devmodeString = devModeProperties.GetString (parameterInitName);
} catch (errorObject) {
// When DevmodeMap does not have a definition, not handle the following
continue;
}

// I check it whether a value of DevmodeMap is right
checkParameter ();

if (! ptParameterInitNode) {
// If ParameterInit is none, create it.
var parameterInitNode = newParameteInitNode.cloneNode (true);
parameterInitNode.setAttribute ("name", orgParameterInitName);

ptParameterInitNode = ptNode.appendChild (parameterInitNode);

var valueNode = newValueNode.cloneNode (true);
var ptValueNode = ptParameterInitNode.appendChild (valueNode);

var typeNode = newTypeNode.cloneNode (true);
typeNode.value = dataType;
ptValueNode.setAttributeNode (typeNode);

var textNode = newTextValueNode.cloneNode (true);
if (devmodeString! = "") {
// set DevmodeMap Value
textNode.text = devmodeString;
}
else {
// set default Value.
textNode.text = defaultValue;
}
ptValueNode.appendChild (textNode);

} else {
if (devmodeString! = "") {
ptParameterInitNode.firstChild.text = devmodeString;
}
}
}
}
}

By mounting the above code, it is possible to add a PrintTicket and reflect the value to DEVMODE.

  In this function, ParameterRef addition, SubFeature conversion, and PageInputBin addition processing are performed. However, since only the addition target of the above-described PrintCapabilities addition processing is a PrintTicket, the description is omitted.

With the above processing, the print setting editing processing related to the PrintTicket scrutiny is completed.
ConvertprintticketToDevmode
This function is a function called when registering the value of PrintTicket in DEVMODE. In particular, in the present embodiment, a process for registering a value related to Parameter that cannot be described in GPD in DEVMODE is performed. This embodiment mainly has the following functions.

-Registering the value of ParameterInit in DEVMODE The process for reflecting the value of ParameterInit in DEVMODE will be described below. First, when the convertPrinttToDevmode function is called, the print setting editing module 2801 generates an object for accessing the property bag 2082 received from the OS. In the present embodiment, an object for accessing the DriverPropertyBag in which the information on the model supported by the driver is stored is prepared.

  The print setting editing module 2081 converts the additional parameter information into an object and lists the data. Then, the print setting editing module 2081 searches whether each listed information is already defined in the PrintTicket. XPATH is used for the search. Next, it is checked whether the acquired parameter value is appropriate. The appropriate parameter is scrutinized whether the data format matches the definition of PrintTicket or whether it falls within the range of the maximum value and the minimum value. If it is determined to be inappropriate, it is changed to the default value described in the additional parameter information. In the present embodiment, the process of changing to the default value is performed, but it may be changed to the maximum value or the minimum value.

  Next, when it is determined that the searched ParameterInit exists, the value of the target ParameterInit is registered in DEVMODE. If it is determined that it does not exist, registration in DEVMODE is not performed. These processes are repeated until all the data groups related to the additional parameter information defined in the DriverPropertyBag are completed. The following is the source code. The GetParamInit function in the source code is a function that searches for ParameterInit using XPATH. A function for checking an appropriate parameter is the same as the source code described above, and is omitted.

setDevmode = function () {
var jsonParameterDef = CreateJsonObject (driverPropertyBag, "ParameterDef");
if (jsonParameterDef) {
var arrayParameterDef = jsonParameterDef.parameterDef;

// Get all items deefined by DriverPropertyBag, Search item from PrintTicket.
for (var i = 0, jsonParameterDefLength = arrayParameterDef.length; i <jsonParameterDefLength; i ++) {
var orgParameterInitName = arrayParameterDef [i] .name;
var parameterInitName = GetSchemaName (orgParameterInitName);
var parameterInitNSPrefix = GetSchemaPrefix (orgParameterInitName);
var parameterInitNSUri = nsObj [parameterInitNSPrefix];
var ptParameterInitNode = GetParamInit (ptNode, parameterInitNSUri, parameterInitName);

if (ptParameterInitNode) {
var parameterInitValueNode = ptParameterInitNode.firstChild;
var parameterInitText = parameterInitValueNode.text;

// check PT Value
checkParameter ();

// Set ParameterInit Value in DEVMODE.
try {
if (devModeProperties.GetString (parameterInitName)! = parameterInitText) {
devModeProperties.SetString (parameterInitName, parameterInitText);
}
}
catch (errorObject) {
Debug.writeln ("Set DEVMODE PropertyBag error:" + parameterInitName + errorObject.message);
}
}
}
}
}

By implementing the above code, the value of PrintTicket can be registered in DEVMODE.
-ValidatePrintTicket
This function is a function for examining the value of PrintTicket. The present embodiment mainly has the following functions.

-Check upper and lower limit values in PrintTicket's ParameterInit-Check empty characters in PrintTicket's ParameterInit This function checks the upper and lower limit values of Parameter for items related to PrintTicket and deletes the Parameter if the value is empty . The check on the upper limit value and the lower limit value is omitted because it has been described above. Next, the empty character of Parameter is checked. All ParameterInit is searched for the target PrintTicket, and it is determined whether or not the parameter value of ParameterInit is empty. If it is determined to be empty, the target ParameterInit is deleted. This is examined for all ParameterInit found in the search. The following is the source code.

deleteEmptyParameterInit = function () {
// Count PrintTicket Feature
var countNum = ptNode.childNodes.length;
for (var i = 0; i <countNum; i ++) {
var node = ptNode.childNodes [i];
if (node.nodeName == "psf: ParameterInit") {
if (node.firstChild.text == "") {

// If ParameterRef contains, delete ParameterRefNode.
var ParamRefName = GetSchemaName (node.attributes [0] .text);
var ParamRefNSPrefix = GetSchemaPrefix (node.attributes [0] .text);
var paramRefNSUri = nsObj [ParamRefNSPrefix]

var paramRefNode = GetParameterRef (ptNode, paramRefNSUri, ParamRefName);
if (paramRefNode) {
ptNode.removeChild (paramRefNode);
}
ptNode.removeChild (node);

// ChildNode carries by deleting, so reduce countNum.
i--;
countNum--;

retVal = 1;
}
}
}
return retVal;
}

By implementing the code as described above, it is possible to perform a print ticket scrutiny process.

  By performing the above processing, it is possible to efficiently edit the print setting information for PrintCapabilities and PrintTicket.

101 CPU, 102 main storage, 1021 ROM, 1022 RAM,
105 Auxiliary storage device

Claims (1)

In the print setting editing module provided by the printer driver having the print setting capability information described in the XML format and the print setting changing function using the print setting information,
Means for obtaining parameter information from a data file holding model-dependent information;
Means for editing print setting capability information and print setting information using parameter information;
A means for editing the print setting capability information and the print setting information according to the print settings set by the user;
Means for registering the value of the print setting information in DEVMODE;
Means for reflecting the value registered in DEVMODE in the print setting information;
A program characterized by efficiently performing these processes even for a large amount of print setting information.