Patent Description:
The configuration described below is generally known. Using a printer driver installed on a host computer as software for controlling a printing apparatus, the printing apparatus connected to the host computer performs printing. An operating system (OS), which is basic software, is installed on the host computer, and the printer driver is configured according to the specifications prescribed by the OS and operates by being called by the OS. A vendor providing the printing apparatus provides a printer driver that matches the specifications of the OS, and thereby can provide a method for instructing the printer to perform printing, using the OS. In a case where a version earlier than Windows® <NUM> of Microsoft® is used as the OS, the printer driver is configured according to an architecture termed the "V3 printer driver". The V3 printer driver can provide the function of displaying a graphical user interface (hereinafter also referred to as a "user interface" or a "GUI") at the timing when a print request is made by a user, and urging the user to perform some operation. For example, if a print request is made, a prescribed event of a configuration module as a component of the V3 printer driver is called. Thus, the configuration module can display a user interface in the processing of the event.

In recent years, a new architecture termed the "V4 printer driver" appears in Windows®. In the V4 printer driver, security is emphasized, and therefore, the customizability of the printer driver itself decreases. For example, the above configuration module is provided by the OS, and the vendor can provide only a setting file and a script file for customizing the operation of the configuration module. To compensate for such a decrease in the customizability, the vendor providing the printing apparatus can provide an application dedicated to assisting the function of the printer driver. This application (app) is termed a "Windows Store Device App (WSDA)". In the publication of <CIT>, a vendor providing a printing apparatus provides a WSDA so that a print setting screen for performing printing can be customized through a particular application.

<CIT> describes a device application that provides a GUI depending on the capabilities of a printer driver in a V4 printer driver environment. <CIT> details a device application that provides a GUI in a V4 printer driver environment. <CIT> discloses a Windows store application capable of providing a printer-vendor-unique print setting screen. <CIT> describes the previewing management in a V4 printer driver environment.

The V4 printer driver can be configured as a class driver for, as a single printer driver, supporting a plurality of printing apparatuses. In recent years, a standard class driver is provided. The standard class driver can be used by an OS in common for printing apparatuses provided by a plurality of vendors. Such a standard driver is included in the package of the OS and can be used by simply connecting any printing apparatus to a host computer. Thus, it is not necessary to separately install a printer driver suitable for a printing apparatus, which is convenient.

As described above, while the V4 printer driver improves security and convenience, the customizability of the printer driver itself decreases, an example of which is as follows: the printer driver does not have the function of providing a GUI. Consequently, a WSDA is used to provide a GUI, such as a print setting screen, even in a case where a driver does not include the function of providing a GUI, as in the V4 printer driver. A conventional WSDA, however, still has functional restrictions. In view of such a problem, the present invention is directed to providing an appropriate function according to a driver to be used.

According to an aspect of the present invention, there is provided a program as specified in claims <NUM> to <NUM>.

In embodiments of the present invention, a description is given of an example for providing an appropriate function according to a driver, using a graphical user interface (hereinafter also referred to as "user interface" or "GUI") application. This GUI application starts and provides a GUI in a case where a driver that does not have the function of providing a GUI, as in the V4 printer driver, is used.

A conventional Windows Store Device App (WSDA) for extending the V4 printer driver can also provide a GUI, but has the following functional restrictions. Specifically, the conventional WSDA is optionally started according to a user instruction and therefore is incompatible with a use case where a user interface should always be displayed when printing is requested. Further, the conventional WSDA is an application configured to change print settings, and therefore cannot access drawing data (an image or text information based on which printing is formed on a sheet surface) generated by a drawing application having issued a print request. Thus, the conventional WSDA cannot display or edit the drawing data. Thus, in the V4 printer driver, it is difficult for the conventional WSDA to provide the function of displaying a user interface at the timing when a print request is made by a user, receiving a user operation, and reflecting the user operation on a printing process.

Further, according to information indicating the capability of a printer driver connected to the conventional WSDA, the conventional WSDA provides a user interface for designating the information. If the WSDA includes, in print settings, a function instruction regarding a function that is not included in the capability information of the printer driver, the function instruction is information unknown to the printer driver, and therefore does not effectively work. Further, as described above, since the conventional WSDA cannot access drawing data, the WSDA itself cannot receive a function instruction and edit drawing data, either. Accordingly, even if a vendor providing a printing apparatus provides the WSDA for a class driver provided together with an OS as described above, the vendor cannot independently extend the function of the class driver.

In the present invention, it is possible to provide an appropriate function according to a driver, using an application that is not subject to the above functional restrictions. Suitable embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The following embodiments do not limit the present invention according to the appended claims, and not all the combinations of the features described in the embodiments are essential for a method for solving the problems in the present invention. The same component is designated by the same reference number, and is not repeatedly described.

<FIG> is a block diagram illustrating the hardware configuration of a printing system. In <FIG>, a host computer <NUM> is an example of an information processing apparatus and includes an input interface <NUM>, a central processing unit (CPU) <NUM>, a read-only memory (ROM) <NUM>, a random-access memory (RAM) <NUM>, an external storage device <NUM>, an output interface <NUM>, and an input/output interface <NUM>. Further, the input interface <NUM> is connected to input devices, such as a keyboard <NUM> and a pointing device <NUM>. The output interface <NUM> is connected to a display device, such as a display unit <NUM>.

The ROM <NUM> stores an initialization program. The external storage device <NUM> stores a group of application programs, an operating system (OS), a printer driver, and various other types of data. The RAM <NUM> is used as a work memory when various programs stored in the external storage device <NUM> are executed.

In the present embodiment, the functions of the host computer <NUM> described below and processing regarding flowcharts described below are achieved by the CPU <NUM> performing processing according to the procedure of a program stored in the ROM <NUM>. A printing apparatus <NUM>, which is a device, is connected to the host computer <NUM> via the input/output interface <NUM>. In this case, the host computer <NUM> and the printing apparatus <NUM> are separately configured. Alternatively, the host computer <NUM> and the printing apparatus <NUM> may be configured as a single information processing apparatus.

<FIG> is a diagram illustrating the block configuration of a driver printing system. In this case, a description is given on the premise of a printing system operating according to an architecture termed the "V4 printer driver", using the host computer <NUM> in which an OS of Windows® <NUM> or later of Microsoft® is provided as an OS.

If a user gives an instruction to perform printing through a Universal Windows Platform (UWP) application <NUM>, a predetermined screen is displayed by Modern Print Dialog (MPD) (not illustrated), which is a function of the OS. The UWP application <NUM> is a drawing application. The screen provided by the MPD has a print preview function for allowing the user to check a printing result on the screen, and the function of allowing the user to select basic print settings. <FIG>, <FIG>, and <FIG> illustrate specific examples. In <FIG>, if an instruction to perform printing is given on a screen <NUM> provided by the UWP application <NUM>, which is a drawing application, a setting screen <NUM> illustrated in <FIG> is displayed by the MPD of the OS. On the setting screen <NUM>, the user can select a driver to be used. Further, on the setting screen <NUM>, the user can also designate basic print settings.

Further, the MPD receives an instruction from the user and starts a WSDA <NUM>, which allows the user to select detailed print settings. Specifically, if an "other settings" button <NUM> is pressed on the setting screen <NUM> in <FIG>, a detailed setting screen <NUM> provided by the WSDA <NUM> and illustrated in <FIG> is displayed. On the detailed setting screen <NUM>, the user can designate more detailed print settings. The WSDA <NUM> is an application for extending the function of a printer driver <NUM>, which is provided by a vendor providing the printing apparatus <NUM> (hereinafter, a "printer vendor"). An image that is displayed in the detailed setting screen <NUM> provided by the WSDA <NUM> and looks like a document image is a sample image originally included in the WSDA <NUM>. Thus, this image in the detailed setting screen <NUM> provided by the WSDA <NUM> is not a preview image based on drawing data generated by the UWP application <NUM>, but a sample image that does not change even if the drawing data changes. The WSDA <NUM> receives information indicating print settings from the MPD, changes setting information of the print settings according to a user operation, and returns the setting information to the MPD. In this case, the information indicating the print settings is described in an Extensible Markup Language (XML) format based on a form defined by the OS and is included in data termed "PrintTicket". The WSDA <NUM> can reference and change the PrintTicket, but cannot reference drawing data (an image or text information based on which printing is formed on a sheet surface). Further, the WSDA <NUM> is started only in a case where the user presses the "other settings" button <NUM> on the setting screen <NUM> provided by the MPD. Thus, the WSDA <NUM> is not always started when print settings are made.

The PrintTicket is generated by a configuration module <NUM> of a selected printer driver <NUM>. The WSDA <NUM> calls the configuration module <NUM> to generate PrintTicket to which designation by the user is reflected. Further, the configuration module <NUM> also has the function of generating PrintCapabilities describing, in XML format based on the form defined by the OS, a function that can be set by the selected printer driver <NUM> and a selection item. The WSDA <NUM> or Printer Extensions (PEX) <NUM> provides a user interface based on the information described in the PrintCapabilities. Further, through the functions of the OS, an at-time-of-printing start application <NUM> can acquire the PrintCapabilities generated by the configuration module <NUM>.

Although <FIG> illustrates the configuration module <NUM> as a function of the printer driver <NUM>, the configuration module <NUM> is originally a component of the OS. The V4 printer driver itself, however, does not include a configuration module, and therefore uses the configuration module <NUM>, which is a component of the OS, as a configuration module of the driver. The printer vendor can customize the operation of the configuration module <NUM> by Generic Printer Description (GPD) (not illustrated) included in the printer driver <NUM> or JavaScript (registered trademark) Constraint.

After the print settings illustrated in <FIG>, <FIG>, and <FIG> are made, and if a "print" button is pressed on the setting screen <NUM> provided by the MPD of the OS, a print request is made. If the user gives an instruction to perform printing on the MPD, the UWP application <NUM> receives a request from the MPD and generates print data necessary for printing. This print data is an "XML Paper Specification" (hereinafter, "XPS") document described in a form termed "XPS". The print data in the present embodiment includes the PrintTicket and drawing data generated by a drawing application.

The XPS document generated by the UWP application <NUM> is transferred to an at-time-of-printing start application launcher <NUM>, which is a component of the OS. If it is determined that an at-time-of-printing start application <NUM> associated with the printer driver <NUM> is present and configured to start, the at-time-of-printing start application launcher <NUM> starts the at-time-of-printing start application <NUM>. If a corresponding at-time-of-printing start application <NUM> is not present, the at-time-of-printing start application launcher <NUM> stores the XPS document as a spool file <NUM>.

Similarly to the WSDA <NUM>, an at-time-of-printing start application <NUM> is an application for extending the function of the printer driver <NUM>, which is provided by the printer vendor. That is, the at-time-of-printing start application <NUM> is a GUI application capable of providing a GUI based on an instruction from the OS in a case where a driver that does not include the function of providing a GUI, as in the V4 driver, is selected. If a V3 driver, which has the function of providing a GUI, is selected, the OS does not start the at-time-of-printing start application launcher <NUM>, and stores an XPS document generated by a drawing application as the spool file <NUM>. That is, if a V3 driver is selected, the at-time-of-printing start application <NUM> does not start or provide a GUI.

Neither the WSDA <NUM> nor the at-time-of-printing start application <NUM> is provided as one of the components of the printer driver <NUM>, and both the WSDA <NUM> and the at-time-of-printing start application <NUM> are independent applications. Further, the WSDA <NUM> and the at-time-of-printing start application <NUM> can be configured together as a single application. For convenience, however, to describe the difference from the conventional WSDA, the WSDA <NUM> and the at-time-of-printing start application <NUM> are described as separate applications.

Normally, the WSDA <NUM> and the at-time-of-printing start application <NUM> are acquired from an application distribution system (a server managed by Microsoft®) (not illustrated) via the Internet by the OS. Further, the printer vendor provides, in advance, metadata described below for a metadata server managed by Microsoft®, whereby an appropriate WSDA <NUM> and an appropriate at-time-of-printing start application <NUM> are automatically installed. Specifically, if the printing apparatus <NUM>, which is a device, is connected to the input/output interface <NUM>, then based on the metadata, a WSDA <NUM> and an at-time-of-printing start application <NUM> associated with the printing apparatus <NUM> are automatically installed on the printing apparatus <NUM>.

The at-time-of-printing start application <NUM> can display a user interface for receiving an operation instruction from the user. Further, the at-time-of-printing start application <NUM> can receive an XPS document, which is print data, and edit PrintTicket and drawing data in the XPS document. If the at-time-of-printing start application <NUM> outputs the XPS document edited as necessary, the OS stores the output XPS document as the spool file <NUM>. If the spool file <NUM> is stored, the processing is transferred to a filter pipeline manager <NUM>. The filter pipeline manager <NUM> has a mechanism for performing printing through a plurality of filters and controls the number and the order of filters using a configuration file (not illustrated). The group of filters in the present embodiment includes a layout filter <NUM>, which is a layout processing unit, and a print command filter <NUM>, which is a print command conversion unit.

To the layout filter <NUM>, the XPS document stored as the XPS spool file <NUM> is input. The layout filter <NUM> has the function of performing a layout process for pages based on print setting information, and outputting the laid out XPS document. The layout process includes, for example, layout printing for printing a plurality of pages on a single sheet surface, and poster printing for printing a single page on a plurality of sheet surfaces.

To the print command filter <NUM>, the output of the layout filter <NUM> is input. The print command filter <NUM> has the function of, according to the print setting information, converting the XPS document into a print command that can be interpreted by the printing apparatus <NUM>, and outputting the print command. In a case where the print command filter <NUM> converts the input XPS document into image data, the print command filter <NUM> is generally termed a "render filter". The render filter is often used in a printer driver for an inexpensive raster printer typified by an inkjet printer. In a case where the print command filter <NUM> operates as the render filter, the print command filter <NUM> converts the input XPS document into image data once. Then, through image processing including color space conversion and binarization, the image data is converted into a print command that can be interpreted by a raster printer.

In a highly functional printer typified by a page printer, if the types of print commands that can be interpreted by the printing apparatus <NUM> include XPS, the print command filter <NUM> edits the input XPS document and outputs the XPS document. If the print command filter <NUM> does not need to process the input XPS document, the print command filter <NUM> may output the input XPS document as it is, or the print command filter <NUM> may not be included in the printer driver <NUM>. This is the basic process of printing through the UWP application <NUM>.

A legacy application <NUM>, which is a drawing application for a Win32 application, can start the PEX <NUM> to make print settings. The PEX <NUM> is started via the configuration module <NUM> and can provide a user interface allowing the user to designate print settings. The PEX <NUM> may be provided together with the printer driver <NUM> as components in a driver package, or may be distributed separately from the printer driver <NUM>. Similarly to the WSDA <NUM>, the PEX <NUM> can reference and change PrintTicket, but cannot reference drawing data (an image or text information based on which printing is formed on a sheet surface). Further, the PEX <NUM> is started only in a case where the user gives an instruction to start the PEX <NUM> on the legacy application <NUM>. Thus, the PEX <NUM> is not always started when printing is performed. If an instruction to perform printing is given on the legacy application <NUM>, the legacy application <NUM> generates an XPS document as print data. The subsequent flow is equivalent to that when printing is performed through the UWP application <NUM>, and therefore is not described here.

The printer driver <NUM> in this configuration may also function as a fax driver. In this case, the printer driver <NUM> generates not a print command that can be interpreted by the printing apparatus <NUM>, but a fax command for requesting the printing apparatus <NUM> to transmit fax. Also in the following description, for convenience, even the fax driver will occasionally be described as the printer driver <NUM>, and even a fax instruction will occasionally be described as a print instruction.

<FIG> is an example of a description indicating corresponding device information in metadata <NUM>, which associates the printing apparatus <NUM> with the at-time-of-printing start application <NUM>. In the metadata <NUM>, a "HardwareIDList" tag <NUM> is described, which indicates a list of printing apparatuses <NUM> that use the metadata <NUM>. An item <NUM> indicates that a printing apparatus <NUM> having the hardware identification (ID) "MFP1_abcd" uses the metadata <NUM>. Similarly, an item <NUM> indicates that a printing apparatus <NUM> having the hardware ID "MFP2_ijkl" uses the metadata <NUM>. As described above, for a single piece of metadata, a plurality of devices that use the single piece of metadata can be listed. For the metadata <NUM>, two printing apparatuses are designated as devices. Alternatively, a single printing apparatus or three or more printing apparatuses may be designated. A "hardware ID" is identification information returned from a printing apparatus <NUM> and for uniquely identifying the printing apparatus <NUM>.

<FIG> is an example of a description indicating the at-time-of-printing start application <NUM>, which is to be associated, in the metadata <NUM> that associates the printing apparatus <NUM> (i.e., a device) with the at-time-of-printing start application <NUM> (i.e., a GUI application),. In the metadata <NUM> in <FIG>, a "DeviceCompanionApplications" tag <NUM> is described, which indicates an at-time-of-printing start application <NUM> associated by the metadata <NUM>. An item <NUM> indicates that an at-time-of-printing start application <NUM> having the name "1234abcd. MFPUtility" and provided by a printer vendor "<NUM>-abcd-efgh-ijkl-<NUM>" is associated with the printing apparatuses <NUM> listed in the "HardwareIDList" tag <NUM>.

If the printing apparatus <NUM> is connected to the host computer <NUM>, the OS searches for metadata registered in a predetermined server (a metadata server managed by Microsoft®). Then, if the OS finds metadata in which a hardware ID returned from the connected printing apparatus <NUM> is described in the HardwareIDList, the OS saves the metadata in the external storage device <NUM> of the printing apparatus <NUM>. Further, the OS acquires, from an application distribution system (not illustrated), an at-time-of-printing start application <NUM> described in the "DeviceCompanionApplication" tag <NUM> of the saved metadata. Then, the OS installs the at-time-of-printing start application <NUM> on the external storage device <NUM> and associates the at-time-of-printing start application <NUM> with the printing apparatus <NUM>. Consequently, when a print request is made to the printing apparatus <NUM> via the printer driver <NUM>, the at-time-of-printing start application <NUM> associated with the printing apparatus <NUM> is started.

This metadata is provided by the printer vendor. The printer vendor provides the metadata in advance for a metadata server managed by Microsoft® and thereby can perform control so that when a printer driver <NUM> is installed on a user environment, an optimal at-time-of-printing start application <NUM> for a connected device is automatically installed on the connected device. According to an instruction from the user, a plurality of printer drivers <NUM> can also be installed on a single device.

<FIG> is a diagram illustrating an example of a print environment configured by the metadata <NUM>. A multifunction peripheral (MFP) <NUM>, which is the printing apparatus <NUM>, includes a printer <NUM> (print function unit) and a fax <NUM> (fax function unit) in a single apparatus. The fax <NUM> transmits a received print request as facsimile. The printer <NUM> has the hardware ID "MFP1_abcd". The fax <NUM> has the hardware ID "MFP1_efgh". The hardware ID of the fax <NUM> can also be the same hardware ID as that of the printer <NUM> so that processing between the printer <NUM> and the fax <NUM> can be switched according to a command.

If the MFP <NUM> is connected to the host computer <NUM>, the OS acquires the metadata <NUM> in which the hardware ID "MFP1_abcd" is described in the "HardwareIDList" tag <NUM>.

Further, the OS acquires an at-time-of-printing start application <NUM>, which corresponds to MFPUtility <NUM>, described in the metadata <NUM>. Then, the OS associates the at-time-of-printing start application <NUM> with the MFP <NUM>. Although the fax <NUM> has a hardware ID different from that of the printer <NUM>, the OS determines these two processing units as the same device (a composite device) based on information acquired from the printing apparatus <NUM>. Thus, the fax <NUM> is also associated with the same metadata <NUM> and the same MFPUtility <NUM> as the printer <NUM>. Alternatively, the hardware ID "MFP1_efgh" of the fax <NUM> can be described in the "HardwareIDList" tag <NUM> of the metadata <NUM>.

There can be a plurality of types of printer drivers <NUM> to be installed for the printer <NUM> of the MFP <NUM>. That is, there can be a plurality of drivers as drivers compatible with the MFP <NUM>, which is a single device. A model-based printer driver <NUM> is a printer driver provided by the printer vendor and dedicated to the printer <NUM> of the MFP <NUM>. A common printer driver <NUM> is a common printer driver provided by the printer vendor and capable of processing a plurality of types of printing apparatuses <NUM> of the printer vendor. Then, a standard printer driver <NUM> is a class driver that can be used in common for printing apparatuses provided by a plurality of vendors, and is a printer driver provided together with the OS as one of functions in the package of the OS. The standard printer driver <NUM> is a printer driver capable of processing a wide range of printing apparatuses <NUM>, using a standardized printing method.

As described above, there are a plurality of printer drivers <NUM> that can be used for a certain printing apparatus <NUM>. A printer driver <NUM> to be used differs according to the Internet connection state, the type of the OS, or the use environment. Normally, the OS references version information of a printer driver, automatically selects and installs the most functional and newest printer driver <NUM> among the printer drivers <NUM> that can be used. Each printer driver <NUM> includes information termed a "Hardware ID" and a "Compatible ID" for identifying an apparatus. If the printing apparatus <NUM> is connected to the host computer <NUM>, the OS acquires the above ID information from the printing apparatus <NUM>, searches for a printer driver <NUM> having corresponding IDs, and installs the printer driver <NUM> on the printing apparatus <NUM>.

For the fax <NUM> of the MFP <NUM>, a fax driver <NUM> having the hardware ID "MFP1_efgh" is installed. Further, if an MFP <NUM> having the hardware ID "MFP2_ijkl" is connected to the host computer <NUM>, the MFP <NUM> is associated with the MFPUtility <NUM>. This is because, as indicated by the item <NUM> in <FIG>, the HardwareIDList as a target in the metadata <NUM> includes MFP2_ijkl. An MFP <NUM> having the hardware ID "MFP3_mnop" is associated with MFPUtility <NUM>, which is different from the MFPUtility <NUM>, according to the description of metadata (not illustrated) different from the metadata <NUM>.

As described above, the printer vendor providing printing apparatuses <NUM> provides metadata and thereby can control which of at-time-of-printing start applications <NUM> is to be provided for each printing apparatus <NUM>. For example, the printer vendor can provide a single at-time-of-printing start application <NUM> in common for the plurality of printing apparatuses <NUM>, or can provide different at-time-of-printing start applications <NUM> for the plurality of printing apparatuses <NUM>. It is, however, not possible to separately provide at-time-of-printing start applications <NUM> according to the types of printer drivers <NUM> associated with the printing apparatuses <NUM>. In <FIG>, there are four types of drivers, namely the drivers <NUM> to <NUM>, as printer drivers <NUM> to be used by the MFP <NUM>, but the printer drivers <NUM> are always associated with a single type of at-time-of-printing start application <NUM>.

The WSDA <NUM> is also associated with the printing apparatus <NUM> and the printer driver <NUM> by a mechanism equivalent to that of the at-time-of-printing start application <NUM>. Thus, restrictions regarding the association are equivalent to those of the at-time-of-printing start application <NUM>.

<FIG> is a diagram illustrating a main processing procedure in a setup process for the at-time-of-printing start application <NUM> in the printing system. This processing flow is an example of the processing of the at-time-of-printing start application <NUM> in the configuration of the MFPUtility <NUM> in <FIG>, for example. In the following description, the at-time-of-printing start application <NUM> may perform each process, but actually, each function is achieved by the CPU <NUM> executing a corresponding program. All the processing is not necessarily sequentially executed in a single process, and there can also be a case where the processing is transferred to the OS once and called by the OS again. The processing procedure is merely a procedure simply illustrating the main processing of the at-time-of-printing start application <NUM> for convenience.

In a case where receiving an XPS document from a drawing application as a print request source, the at-time-of-printing start application launcher <NUM> calls an initialization process for an at-time-of-printing start application <NUM> associated with the printing apparatus <NUM>. After the print settings described with reference to <FIG>, <FIG>, and <FIG> are made, and if the "print" button is pressed on the setting screen <NUM> provided by the OS, a print request is made, and an XPS document is output from a drawing application.

In the initialization process, the at-time-of-printing start application <NUM> registers the setup process illustrated in <FIG> and an editing and ending process illustrated in <FIG> as an event handler prescribed by the OS. In a case where the at-time-of-printing start application <NUM> ends the initialization process, the OS executes the setup process for the at-time-of-printing start application <NUM> registered as the prescribed event handler. <FIG> illustrates this setup process.

First, in step S601, the at-time-of-printing start application <NUM> acquires PrintTicket stored in the XPS document. As described with reference to <FIG>, the PrintTicket is data including information indicating print settings and is generated by the configuration module <NUM> based on print settings designated by the user. The PrintTicket can be acquired from the XPS document by calling a predetermined application programming interface (API) of the OS.

Next, in step S602, the at-time-of-printing start application <NUM> acquires PrintCapabilities, which is data including information indicating the capability of the printer driver <NUM>. Then, the at-time-of-printing start application <NUM> checks a name space in the PrintCapabilities to determine the type of the printer driver <NUM> having received the print request from the application. The details of the name space in the PrintCapabilities and the determination method for determining the name space will be described below.

Normally, the PrintTicket also stores name space information equivalent to that in the PrintCapabilities. Thus, the determination in step S602 may be made using the PrintTicket. Since it takes time to acquire the PrintCapabilities, the processing time can be shortened using the PrintTicket depending on the configuration. Further, the printer driver <NUM> may store information for the determination in DriverPropertyBag (not illustrated). The at-time-of-printing start application <NUM> may be configured to acquire the information stored in the DriverPropertyBag and use the information for the determination.

As a result of the determination in step S602, in a case where the printer driver <NUM> having received the print request from the application is the fax driver (YES in step S602), then in step S603, the at-time-of-printing start application <NUM> saves information indicating that the operation mode is a fax driver mode. In the process of step S603 and processes described below, the at-time-of-printing start application <NUM> holds information using, as an example, Local Storage provided by the OS. The overall configuration of information stored in the Local Storage will be described below. Similarly, in step S604, the at-time-of-printing start application <NUM> saves, in the Local Storage, information indicating that the display of a user interface (UI) is enabled.

Then, in step S605, the at-time-of-printing start application <NUM> calls the prescribed API provided by the OS and gives an instruction to display a user interface in the current execution of the at-time-of-printing start application <NUM>. This API is executed, whereby a UI process for the at-time-of-printing start application <NUM> illustrated in <FIG> is called, and the at-time-of-printing start application <NUM> displays a user interface. This is the setup process by the at-time-of-printing start application <NUM> in the fax driver mode.

As a result of the determination in step S602, in a case where the printer driver <NUM> having received the print request from the application is not the fax driver (NO in step S602), then in step S606, the at-time-of-printing start application <NUM> saves information indicating that the operation mode is a printer driver mode.

Next, in step S607, the at-time-of-printing start application <NUM> references the PrintTicket and checks whether a print preview start instruction is present. The specific checking method for checking the PrintTicket will be described below with reference to <FIG>. Alternatively, a print preview start instruction may be achieved by a method using other than the PrintTicket so long as the method can designate the print preview start instruction through the WSDA <NUM> and the PEX <NUM> and reference the print preview start instruction through the at-time-of-printing start application <NUM>. For example, the configuration may be such that UserPropertyBag or QueuePropertyBag provided as the storage location of setting information of the printer driver <NUM> by the OS is used. A "print preview" refers to displaying, on the display unit <NUM>, an image of a printing result to be generated on a sheet surface, based on print settings and print data generated by an application. That is, the fact that "a print preview start instruction is present in the PrintTicket" indicates that the user gives an instruction to display a print preview screen. By viewing the print preview screen, the user can check whether a desired printing result is to be obtained before printing is performed. Then, the user can give an instruction to correct the print settings, delete any page, or stop the printing process, as necessary.

In a case where it is determined in step S607 that a print preview start instruction is not present (NO in step S607), the processing proceeds to step S609. In a case where it is determined in step S607 that a print preview start instruction is present (YES in step S607), then in step S608, the at-time-of-printing start application <NUM> saves information indicating that the print preview is enabled.

Next, in step S609, the at-time-of-printing start application <NUM> checks whether a function extension instruction is present in PropertyBag. As described above, the "PropertyBag" refers to UserPropertyBag or QueuePropertyBag. This function extension is used by the printer vendor to extend a function that can be designated when printing is performed, for example, in a case where a printer driver only has basic functions as in the standard printer driver <NUM>. In a case where PrintTicket including a description for giving an instruction to extend a function is transferred to the standard printer driver <NUM>, this description is information unknown to the standard printer driver <NUM> and therefore is deleted as an improper description. In such a case, a function extension instruction is stored in the PropertyBag, whereby the function extension instruction is maintained without being deleted. Meanwhile, PrintTicket is information included in an XPS document, which is print data, and held with respect to each piece of print data. Thus, the PrintTicket has the advantage of, even in a case where a plurality of print requests are successively made, being able to accurately switch the enabled and disabled states of the print preview or the function extension with respect to each print request. The at-time-of-printing start application <NUM> may be configured to skip the process of step S609, and if a function can be extended, always enable the function extension.

In a case where it is determined in step S609 that a function extension instruction is not present in the PropertyBag (NO in step S609), the processing proceeds to step S613. In a case where it is determined in step S609 that a function extension instruction is present in the PropertyBag (YES in step S609), then in step S610, the at-time-of-printing start application <NUM> acquires the PrintCapabilities. In a case where the PrintCapabilities is already acquired in step S602, the process of step S610 is skipped.

Next, in step S611, the at-time-of-printing start application <NUM> determines whether there is a predetermined function that is not supported by the PrintCapabilities. The "predetermined function" refers to a function that can be edited by the at-time-of-printing start application <NUM> and can be provided as an extension function by the at-time-of-printing start application <NUM>. That is, the at-time-of-printing start application <NUM> determines whether there is a function that is not described in the PrintCapabilities, and can be provided by the at-time-of-printing start application <NUM>. Consequently, the at-time-of-printing start application <NUM> determines whether there is a function that is not supported by the printer driver <NUM>, and can be provided by the at-time-of-printing start application <NUM>. This determination process will be described in detail below with reference to <FIG>.

In a case where it is determined in step S611 that there is not a corresponding function (NO in step S611), the processing proceeds to step S613. In a case where it is determined in step S611 that there is a corresponding function (YES in step S611), then in step S612, the at-time-of-printing start application <NUM> saves the corresponding function as an extension function in the Local Storage.

Next, in step S613, the at-time-of-printing start application <NUM> determines whether the print preview is enabled or an extension function to be provided is present. In a case where the at-time-of-printing start application <NUM> determines that the print preview is enabled or an extension function to be provided is present (YES in step S613), the processing proceeds to step S604. In step S604, the at-time-of-printing start application <NUM> gives an instruction to display a user interface. In a case where the at-time-of-printing start application <NUM> determines that the print preview is not enabled or an extension function to be provided is not present (NO in step S613), the at-time-of-printing start application <NUM> ends the setup process.

As described above, in the setup process for the at-time-of-printing start application <NUM>, it is determined whether it is necessary to start a user interface. In a case where it is necessary, an instruction to start the user interface is given, and information necessary for subsequent processing is stored.

<FIG> are examples of PrintCapabilities of the printer drivers and the fax driver having different configurations. The PrintCapabilities of these drivers mainly have portions necessary for the description and are partially omitted.

<FIG> is examples of PrintCapabilities of the fax driver <NUM>. At the beginning of the PrintCapabilities, there is a "psf:PrintCapabilities" element. As the attributes of the "psf:PrintCapabilities" element, name spaces used in the PrintCapabilities are defined. Normally, in addition to name spaces indicating the definitions of OS standard termed "PrintSchema", name spaces independently defined by the printer vendor providing this printer driver <NUM> are listed here. The PrintCapabilities illustrated in <FIG> include a name space <NUM>, which is independently defined by the printer vendor.

On the other hand, <FIG> is an example of PrintCapabilities of the model-based printer driver <NUM>. PrintCapabilities <NUM> illustrated in <FIG> include a name space <NUM>, which is independently defined by the printer vendor. Further, <FIG> illustrates an example of PrintCapabilities of the common driver <NUM>. <FIG> illustrates an example of PrintCapabilities of the standard printer driver <NUM>.

A name space is used to uniquely determine a function that can be selected, a selection item, and the definition of the function or the selection item. Even if printer drivers <NUM> are provided by the same printer vendor, but if the printer drivers <NUM> are greatly different in a set of functions from each other as in printer functions and fax functions, different values are generally set. Using this, in step S602, it may be determined whether a name space includes the Uniform Resource Locator (URL) "http://www. com/ns/printschema/fax/v100" as illustrated in the name space <NUM> in <FIG>.

<FIG> is an example of PrintTicket generated based on the PrintCapabilities <NUM> of the model-based printer driver <NUM> illustrated in <FIG>. As illustrated in <FIG>, PrintTicket stores the setting values of functions defined in the PrintCapabilities <NUM>. For example, Feature "psk:PageMediaType" indicates a sheet type for use in printing. In the PrintTicket in <FIG>, "psk:Plain", i.e., plain paper, is designated. In the determination process for determining whether a print preview start instruction is present in step S607, it is determined whether the designated value of Feature "ns0000:JobPreview" is "ns0000:ON".

Next, with reference to the PrintCapabilities in <FIG> and <FIG>, the determination process in step S611 is described in detail. <FIG> illustrates a list of predetermined functions that can be provided as extension functions by the at-time-of-printing start application <NUM>, and selection items of the predetermined functions. In this case, the at-time-of-printing start application <NUM> has a page layout function for printing a plurality of pages by laying out the plurality of pages on a single page, and a stamp function for superimposing a designated stamp on a printing result.

In the determination process in step S611, the at-time-of-printing start application <NUM> analyzes the PrintCapabilities and checks whether there is a function indicated by a "function name" in <FIG>. In a case where the printing target is the PrintCapabilities <NUM> of the model-based printer driver <NUM>, Feature "JobNUpAllDocumentsContiguously" and Feature "PageStamp" are present. Thus, the determination result is NO in step S611.

In a case where the printing target is PrintCapabilities <NUM> of the common printer driver <NUM>, the Feature "JobNUpAllDocumentsContiguously" is present, but the Feature "PageStamp" is not present. Thus, the determination result is YES in step S611. In this case, the at-time-of-printing start application <NUM> provides PageStamp, i.e., the stamp function, as an extension function. In a case where the printing target is PrintCapabilities <NUM> of the standard printer driver <NUM>, neither the Feature "JobNUpAllDocumentsContiguously" nor the Feature "PageStamp" is present. Thus, the determination result is YES in step S611. At this time, the at-time-of-printing start application <NUM> provides JobNUpAllDocumentsContiguously and PageStamp, i.e., the layout function and the stamp function, as extension functions.

<FIG> is a diagram illustrating an example of a user interface provided by the WSDA <NUM> in a case where the user selects the model-based printer driver <NUM>. A screen in <FIG> is an example of a setting screen provided by the WSDA <NUM> and is a screen provided before a print request is made by a drawing application. As indicated by an item <NUM>, the model-based printer driver <NUM> supports Feature "JobPreview", which indicates the print preview function. The WSDA <NUM> configures a user interface based on PrintCapabilities acquired from the printer driver <NUM>, and therefore, based on the item <NUM>, displays a control item <NUM> for switching the enabled and disabled states of the print preview. According to the designation by the user, the WSDA <NUM> stores the on or off state of the Feature "JobPreview" in PrintTicket. In the process of step S607, the at-time-of-printing start application <NUM> references this information and determines whether a print preview start instruction is present.

<FIG> is a diagram illustrating an example of a user interface provided by the WSDA <NUM> when the standard printer driver <NUM> is selected as a print destination. A screen in <FIG> is also an example of a setting screen provided by the WSDA <NUM> and is a screen provided before a print request is made by a drawing application. The standard printer driver <NUM> does not support the Feature "JobPreview". In such a case, the WSDA <NUM> displays a control item <NUM> for selecting whether an extension function is to be enabled. At the timing when the user presses an OK button <NUM>, the WSDA <NUM> stores in PropertyBag a value designated on the control item <NUM>. The WSDA <NUM> may be configured to give an instruction to start the print preview in addition to the extension function. In this case, the extension function and the print preview may be able to be designated using different controls, or simultaneously designated using a single control.

The PEX <NUM> can also provide a method for controlling the start of the at-time-of-printing start application <NUM> by processing equivalent to the above processing of the WSDA <NUM>.

If an instruction to display a UI is given in step S605, and after the setup process for the at-time-of-printing start application <NUM> ends, the OS calls a UI process for the at-time-of-printing start application <NUM>. <FIG> is a diagram illustrating a main processing procedure in the UI process by the at-time-of-printing start application <NUM> in the printing system. This processing procedure is an example of the processing of the at-time-of-printing start application <NUM> in the configuration of the MFPUtility <NUM> in <FIG>, for example. In the following description, the at-time-of-printing start application <NUM> may perform each process, but actually, each function is achieved by the CPU <NUM> executing a corresponding program. All the processing is not necessarily sequentially executed in a single process, and there can also be a case where the processing is transferred to the OS once and called by the OS again. The processing flow is merely a flow simply illustrating the main processing of the at-time-of-printing start application <NUM> for convenience. In a case where an instruction to display a UI is not given in step S605, the OS skips the UI process illustrated in <FIG> and calls an editing and ending process described below.

First, in step S701, the at-time-of-printing start application <NUM> reads the operation mode saved in step S603 or S606 from the Local Storage. In step S702, the at-time-of-printing start application <NUM> determines whether the operation mode is the fax driver mode.

In a case where the operation mode is the fax driver mode (YES in step S702), then in step S703, the at-time-of-printing start application <NUM> configures a user interface for the fax driver. The user interface for the fax driver includes a control item allowing the user to designate a transmission destination and a fax number. The details of the user interface for the fax driver will be described below with reference to <FIG>.

In step S704, the at-time-of-printing start application <NUM> receives an input from the user. If an instruction to transmit fax is given on the user interface, then in step S705, the at-time-of-printing start application <NUM> saves in the Local Storage the transmission destination and the fax number designated by the user.

This is the processing of the at-time-of-printing start application <NUM> in the fax driver mode. As described above, in the fax driver mode, the at-time-of-printing start application <NUM> always displays a user interface as an input screen allowing the user to designate the transmission destination and the fax number (see <FIG>). In the fax driver, the transmission destination and the fax number are transmission destination information essential for transmitting fax. Even if the WSDA <NUM> or the PEX <NUM> is configured to allow the user to designate the transmission destination and the fax number, a user interface of the WSDA <NUM> or the PEX <NUM> is not always opened when printing is performed. The at-time-of-printing start application <NUM> allows the user to designate the transmission destination and the fax number, whereby the user can certainly input the destination of the current fax transmission process. Further, a screen of the WSDA <NUM> or the PEX <NUM>, which is displayed only in a case where the user gives an instruction, may also be configured to allow the user to designate the transmission destination and the fax number. In this manner, even in a case where the at-time-of-printing start application <NUM> does not start for some reason, it is possible to provide a method for designating the transmission destination and the fax number. If the WSDA <NUM> or the PEX <NUM> is configured to allow the user to designate the transmission destination and the fax number, the at-time-of-printing start application <NUM> may give an instruction to display a UI only in a predetermined case. That is, in a case where the transmission destination and the fax number are included in the PrintTicket, the at-time-of-printing start application <NUM> gives an instruction to display a UI in step S605. In a case where the transmission destination and the fax number are not included in the PrintTicket, the at-time-of-printing start application <NUM> does not give an instruction to display a UI in step S605. In this manner, the at-time-of-printing start application can be configured to start only in a case where the user forgets to designate the transmission destination and the fax number in the WSDA <NUM> or the PEX <NUM>.

In a case where it is determined in step S702 that the operation mode is not the fax driver mode (NO in step S702), then in step S706, the at-time-of-printing start application <NUM> reads the extension function saved in step S612.

Next, in step S707, the at-time-of-printing start application <NUM> references the information saved in step S608 and determines whether the print preview is enabled. In a case where the print preview is not enabled (NO in step S707), the processing proceeds to a user interface configuration process in step S713. In a case where the print preview is enabled (YES in step S707), then in step S708, the at-time-of-printing start application <NUM> acquires the PrintTicket.

Further, in step S709, based on the PrintTicket, the at-time-of-printing start application <NUM> acquires the PrintCapabilities. Since it takes time to acquire the PrintCapabilities, the configuration may be such that necessary information is saved in the Local Storage in the setup process in <FIG>, and the saved information is used in step S709.

Next, in step S710, the at-time-of-printing start application <NUM> analyzes the acquired PrintCapabilities and searches whether a particular function is supported by the PrintCapabilities. Then, the at-time-of-printing start application <NUM> saves the found function and the setting value described in the PrintTicket, as a driver function in the Local Storage. In this case, as an example, the at-time-of-printing start application <NUM> searches for two functions, namely the layout function and the sheet type setting, as particular functions. The search process is executed by determining whether Feature having a prescribed name is present in the PrintCapabilities. The extension function saved in step S612 indicates a function that the driver does not have, whereas the driver functions saved in step S710 are functions that the driver has. Thus, if these driver functions are enabled in the PrintTicket, the printer driver <NUM> can properly execute processing according to the designation of the driver functions.

Next, in step S711, the at-time-of-printing start application <NUM> acquires the XPS document using the predetermined API of the OS. Further, in step S712, the at-time-of-printing start application <NUM> analyzes the content of the XPS document and displays the XPS document on the display unit <NUM>. In this process, the at-time-of-printing start application <NUM> reflects the setting value set in the PrintTicket on a printing result, whereby it is possible to achieve a more accurate print preview.

The XPS document received by the at-time-of-printing start application <NUM> is generated by the application as the print request source and is data before being processed by the printer driver <NUM>. Accordingly, for example, even if layout printing is designated in the PrintTicket in the XPS document, a layout process is not performed on the XPS document received by the at-time-of-printing start application <NUM>. Taking such a case into account, the at-time-of-printing start application <NUM> displays on the display unit <NUM> a print image reflecting print settings according to a logic equivalent to that implemented by a subsequent driver. If the print settings are changed on a user interface displayed by the at-time-of-printing start application <NUM>, the at-time-of-printing start application <NUM> displays a print image reflecting the changes on the display unit <NUM> again. In a printer driver that is not provided by the printer vendor, such as the standard printer driver <NUM>, it is not clear according to what logic the print settings are reflected on the XPS document. In this case, the at-time-of-printing start application <NUM> skips the reflection of the designated function or reflects the designated function according to an original logic, and then displays, on the display unit <NUM>, information indicating that there is a possibility that the printing result is different. Further, regarding an extension function to be provided by the at-time-of-printing start application <NUM> including also the editing of the XPS document, the at-time-of-printing start application <NUM> may display on the display unit <NUM> a print image reflecting the print settings according to the same logic as the actual editing.

Next, in step S713, the at-time-of-printing start application <NUM> configures a user interface having controls allowing the user to designate the extension function saved in step S612 and the driver function saved in step S710. Items to be displayed as choices of the extension function saved in step S612 are information of "option" in <FIG>, i.e., items supported by the at-time-of-printing start application <NUM>. Items to be displayed as choices of the driver function saved in step S710 are a list of Options of a corresponding function in the PrintCapabilities. For example, to allow the user to designate a sheet type based on information in the PrintCapabilities <NUM>, all Options supported by "psk:PageMediaType" (psk:Plain, ns0000:PhotoPaper, and the like) are listed as choices. Although not illustrated in the PrintCapabilities <NUM>, normally, a "DisplayName" element is present in each Feature and each Option. In the DisplayName, localized appropriate name information is stored. Thus, the at-time-of-printing start application <NUM> displays the names of the DisplayName as choices of each driver function.

In step S714, the at-time-of-printing start application <NUM> receives an input from the user. If an instruction to perform printing is given on the user interface, then in step S715, the at-time-of-printing start application <NUM> saves in the Local Storage the setting value of each function designated by the user. This is the processing of the at-time-of-printing start application <NUM> in the printer driver mode.

The configuration may be such that the processes of steps S708 to S710 are executed even if it is determined in step S707 that the print preview is not enabled. Consequently, the at-time-of-printing start application <NUM> urges the user again to check an important print setting that necessarily needs to be confirmed before printing. If necessary, it is possible to provide the user with a method capable of changing the important print setting.

<FIG> is a diagram illustrating an example of a user interface as an input screen displayed in a case where the at-time-of-printing start application <NUM> operates in the fax driver mode. A display item <NUM> is a control item for the user to designate the transmission destination. A display item <NUM> is a control item for the user to input the fax number. A display item <NUM> is a button for starting an address book. If this button is pressed, the address book is started. The destination is selected on the address book, whereby the transmission destination and the fax number are automatically input. A display item <NUM> is a button for starting fax transmission. The user cannot press this button in the state where the transmission destination and the fax number are not input. A display item <NUM> is a "cancel" button. If the user presses this button, a subsequent fax transmission process is canceled.

With this configuration, in the fax driver mode, the at-time-of-printing start application <NUM> can always display a user interface as an input screen allowing the user to designate the transmission destination and the fax number. In the fax driver, the transmission destination and the fax number are information essential for transmitting fax. The at-time-of-printing start application <NUM> allows the user to designate the transmission destination and the fax number, whereby the user can certainly input the destination of the current fax transmission process.

<FIG> is an example of a user interface for designating an extension function and displayed in a case where the at-time-of-printing start application <NUM> operates in the printer driver mode when the standard printer driver <NUM> operates. In <FIG>, the print preview function is not enabled. Neither the layout print function nor the stamp function is supported by the PrintCapabilities <NUM> of the standard printer driver <NUM>. Thus, in the processes of steps S611 and S612, the at-time-of-printing start application <NUM> saves two functions, namely the layout print function and the stamp function, as extension functions. As a result, these two functions are provided as extension functions. A display item <NUM> is a control item for designating the setting of the layout print function. A display item <NUM> is a control item for designating the setting of the stamp function. A display item <NUM> is a button for starting printing. A display item <NUM> is a "cancel" button. If the user presses this button, a subsequent printing process is canceled. If the operation driver is the common printer driver <NUM>, only the stamp function is displayed as an extension function. This is because the layout function is supported by the PrintCapabilities <NUM> of the common printer driver <NUM>.

With this configuration, the at-time-of-printing start application <NUM> is used in a driver which is provided by Microsoft® similarly to the OS and of which the function cannot be extended by the printer vendor, as in the standard printer driver <NUM>, whereby it is possible to achieve the extension of a print function. Further, information indicating the capability of a driver which operates is determined, and only a missing function is provided as an extension function. Consequently, in a case where there are a plurality of types of printer drivers <NUM> that can be used, it is possible to provide an optimal extension function for each printer driver <NUM>. Further, the user can control whether a function is to be extended with reference to a user interface displayed when printing is performed. Consequently, it is possible to deal with a use case where it is not desirable to display a user interface each time.

<FIG> is an example of a user interface in a case where the at-time-of-printing start application <NUM> operates in the printer driver mode when the model-based printer driver <NUM> operates. The print preview function is enabled. A display item <NUM> is a control item for changing a page to be displayed on the print preview. The user can change the display page using this control item and can also further check the total number of pages to be printed based on the current print data and print settings. A display item <NUM> is a print preview screen representing an image of the printing result of a designated page. A display item <NUM> is a control item for designating the layout print function. A display item <NUM> is a control item for designating a sheet type. The display items <NUM> and <NUM> indicate not extension functions but driver functions. Thus, as described above, selection items are based on the functions of the printer driver <NUM>. A display item <NUM> is a button for starting printing. A display item <NUM> is a "cancel" button. If the user presses this button, a subsequent printing process is canceled. In <FIG>, only driver functions are displayed. However, as a result of the processing in <FIG> and <FIG>, if both a driver function and an extension function are enabled, the at-time-of-printing start application <NUM> displays controls allowing the user to designate all these functions.

With this configuration, based on an XPS document generated by a drawing application and print settings designated by the user, it is possible to achieve a print preview function for displaying a print image close to a printing result before printing. Further, it is also possible for the user to make changes to finally adjust the print settings, while checking a printing result and the number of pages to be printed. With these functions, it is possible to prevent a misprint and also provide a final adjustment method for, for example, performing printing within a desired number of pages.

After the UI process for the at-time-of-printing start application <NUM> in <FIG> ends, the OS calls an editing and ending process for the at-time-of-printing start application <NUM> in <FIG>. If the UI display instruction process in step S605 is not executed, the OS calls the editing and ending process without calling the UI process for the at-time-of-printing start application <NUM> in <FIG>. This processing procedure is an example of the processing by the at-time-of-printing start application <NUM> in the configuration of the MFPUtility <NUM> in <FIG>, for example. In the following description, the at-time-of-printing start application <NUM> may perform each process, but actually, each function is achieved by the CPU <NUM> executing a corresponding program. Further, all the processing is not necessarily sequentially executed in a single process, and there can also be a case where the processing is transferred to the OS once and called by the OS again. The processing procedure is merely a flow simply illustrating the main processing of the at-time-of-printing start application <NUM> for convenience.

In step S801, the at-time-of-printing start application <NUM> reads from the Local Storage the operation mode saved in step S603 or S606 and the UI display information saved in step S604. In a case where it is determined in step S802 that a UI is not displayed (NO in step S802), then in step S806, the at-time-of-printing start application <NUM> acquires the XPS document using the API of the OS. In step S807, the at-time-of-printing start application <NUM> outputs the XPS document without altering the XPS document at all. As described above, even if the at-time-of-printing start application <NUM> does not change the XPS document, the at-time-of-printing start application <NUM> needs to acquire the whole of the XPS document once and output the XPS document. This is the processing of the at-time-of-printing start application <NUM> in a case where a user interface is not displayed. As described above, if it is determined that it is not necessary to display a user interface, the at-time-of-printing start application <NUM> does not display a user interface, and the processing ends.

In a case where it is determined in step S802 that a UI is displayed (YES in step S802), then in step S808, based on the information read in step S801, the at-time-of-printing start application <NUM> determines whether the operation mode is the fax driver mode. In a case where it is determined that the operation mode is the fax driver mode (YES in step S808), then in step S803, the at-time-of-printing start application <NUM> acquires from the Local Storage the transmission destination and the fax number saved in step S705. Next, in step S804, the at-time-of-printing start application <NUM> acquires the PrintTicket using the API of the OS. Further, in step S805, the at-time-of-printing start application <NUM> stores in the PrintTicket the transmission destination and the fax number acquired in step S803.

<FIG> illustrates an example of the PrintTicket that stores the above information. In this case, the transmission destination is stored as JobRecipientName, and the fax number is stored as JobFaxNumber. After editing the PrintTicket, the at-time-of-printing start application <NUM> stores the edited PrintTicket in the XPS document as necessary and then outputs the XPS document, and the processing ends. The fax driver <NUM> references the PrintTicket, acquires the transmission destination and the fax number, and transmits to the printing apparatus <NUM> a job to be transmitted by fax to the designated fax number.

In a case where it is determined in step S808 that the operation mode is not the fax driver mode (NO in step S808), the at-time-of-printing start application <NUM> determines a function to be provided in step S710. Then, in step S809, the at-time-of-printing start application <NUM> reads from the Local Storage the setting value of the driver function designated by the user using the display item <NUM>. Next, in step S810, the at-time-of-printing start application <NUM> determines whether the setting value of the driver function is changed from the initial state.

In a case where it is determined in step S810 that the setting value of the driver function is not changed (NO in step S810), the processing proceeds to step S813. In a case where it is determined in step S810 that the setting value of the driver function is changed (YES in step S810), then in step S811, the at-time-of-printing start application <NUM> acquires the PrintTicket. In step S812, the at-time-of-printing start application <NUM> reflects on the PrintTicket the setting value of the driver function acquired in step S809. The configuration of information to be stored in the Local Storage and the reflection method for reflecting the setting value on the PrintTicket for achieving these processes will be described below. If there are a plurality of driver functions of which the setting values are changed, the at-time-of-printing start application <NUM> performs the reflection process for reflecting the setting values of all the driver functions on the PrintTicket. After reflecting the setting value on the PrintTicket, then in step S813, the at-time-of-printing start application <NUM> acquires the XPS document.

Next, in step S814, the at-time-of-printing start application <NUM> reads, from the Local Storage, the setting value of the extension function to be provided according to the determination in step S612 and designated by the user using, for example, the display item <NUM>. Next, in step S815, the at-time-of-printing start application <NUM> determines whether the setting value of the extension function is designated. In a case where it is determined in step S815 that the setting value of the extension function is not designated (NO in step S815), then in step S817, the at-time-of-printing start application <NUM> outputs the XPS document, and the processing ends.

In a case where it is determined in step S815 that the setting value of the extension function is designated (YES in step S815), then according to the extension function designated by the user and the setting value of the extension function, the at-time-of-printing start application <NUM> edits drawing data in the XPS document. For example, a case is described where a layout print function for laying out two pages on a single page is designated. In this case, the at-time-of-printing start application <NUM> acquires FixedPage, which is the concept of a page in the drawing data in the XPS document, for two pages and places the drawing data in a reduced manner on the FixedPage of a single page. Based on this, the at-time-of-printing start application <NUM> deletes the original FixedPage for two pages from the drawing data and adds newly created FixedPage to the drawing data. Such processing is repeatedly executed on all pages. If there are a plurality of designated extension functions, the at-time-of-printing start application <NUM> generates drawing data reflecting all the designation of the extension functions. Finally, the at-time-of-printing start application <NUM> outputs the XPS document including the edited drawing data, and the processing ends.

As described above, in a case where the setting value of a driver function supported by the printer driver <NUM> is changed, the at-time-of-printing start application <NUM> in this configuration reflects the change on PrintTicket. Then, the at-time-of-printing start application <NUM> entrusts the printer driver <NUM> with an editing process for editing drawing data in an XPS document. Consequently, the at-time-of-printing start application <NUM> can perform high-speed processing without needing to perform an editing process for editing an unnecessary XPS document. Additionally, the function of the printer driver <NUM> is used, and therefore, it is possible to obtain exactly the same result in a case where the function is designated through the WSDA <NUM> and a case where the function is designated through the at-time-of-printing start application <NUM>.

Meanwhile, regarding an extension function that is not supported by the printer driver <NUM>, the at-time-of-printing start application <NUM> itself in this configuration edits drawing data in an XPS document. Consequently, it is possible to provide the user with a function that is not supported by the printer driver <NUM>.

<FIG> is a diagram illustrating an example of information stored in the Local Storage. The stored information includes a name and a value. This example indicates that the at-time-of-printing start application <NUM> operates in the printer driver mode, the stamp function is provided as an extension function, and the layout print function is provided as a driver function. In the process of step S612, information having the name "extension function_PageStamp" and a value of null is added to the Local Storage.

If the stamp function is designated on a user interface of the at-time-of-printing start application <NUM>, the value designated in the process of step S715 is stored as the value of "extension function_PageStamp". In this case, the value is changed to the setting value "Confidential" by the user. Regarding the layout print function as a driver function, in the process of step S710, information having the name "driver function_JobNUpAllDocumentsContiguously" and a value corresponding to an initial value set in the PrintTicket is added. If the designated value of the layout print function is changed on a user interface of the at-time-of-printing start application <NUM>, the value changed in the process of step S715 is stored. In this case, the value is changed to the setting value "ns0000:PagesPerSheet_2" by the user. This name is Option name defined in the PrintCapabilities of the printer driver <NUM>. As described above, based on the prefix of information stored in the Local Storage, it is possible to determine which of an extension function and a driver function each function is.

In the process of step S810, the at-time-of-printing start application <NUM> determines whether a driver function starting with the prefix "driver function_" is present in the Local Storage. In the process of step S812, the at-time-of-printing start application <NUM> reflects Option name stored as a value in the Local Storage as it is on Option name of the PrintTicket. In the process of step S815, the at-time-of-printing start application <NUM> determines whether an extension function starting with the prefix "extension function_" is present in the Local Storage.

As described above, in the present embodiment, the configuration can be such that after a print instruction is given by the user (i.e., after an XPS document is output from a drawing application), and before the printing apparatus <NUM> performs a printing operation, a user interface of the at-time-of-printing start application <NUM> is displayed. Further, in a case where the at-time-of-printing start application <NUM> is uniquely assigned to the printing apparatus <NUM> regardless of the type of the printer driver <NUM>, it is possible to achieve an optimal function extension according to the type of the printer driver <NUM>. If a fax driver is connected, a user interface is displayed as an input screen for inputting a transmission destination and a fax number, which are essential for transmitting fax.

If a printer driver is connected, then according to designation by the user, it is possible to achieve a print preview function for allowing the user to check a printing result on the display unit <NUM> in advance. Further, it is possible to determine a function based on information indicating the capability of the connected printer driver <NUM> and provide a missing function as an extension function. Consequently, even in a case where a connected driver is a standard printer driver provided by Microsoft® together with the OS, and the function of the driver cannot be extended by the printer vendor, the printer vendor can extend an original function using the at-time-of-printing start application <NUM>.

In the present embodiment, print previews in the fax driver mode and the printer driver mode and a function extension are achieved by the at-time-of-printing start application <NUM>, which is a single GUI application. These three functions, however, do not need to be implemented in a combined manner. It goes without saying that the at-time-of-printing start application <NUM> can be configured to have one or two of the three functions.

Based on the present invention, it is possible to provide an appropriate function according to a driver to be used.

Claim 1:
A program of a graphical user interface (GUI) application capable of providing a GUI in a case where a printer driver that does not have a function of providing a GUI is selected, the program, when executed by a computer, causing the computer to execute:
acquiring print data that includes:
drawing data generated by a drawing application; and
setting data including information indicating a print setting,
wherein the print data is output from the drawing application in a case where a print request is output, in response to user instruction, by an operating
system installed on the computer,
acquiring at least either of the setting data and capability data, wherein the capability data includes information indicating a capability of the printer driver;
determining whether first information is included in the at least either of the acquired setting data and the capability data; and
controlling whether to provide or not provide a GUI displaying a first display item in accordance with the determination result of whether or not the first information is included,
wherein, in case of the setting data being acquired, as the first information, information indicating that a print preview screen is to be displayed is included in the setting data, the print preview screen based on the drawing data is provided as the first display item, and wherein in a case where the information indicating that the print preview screen is to be displayed is not included in the setting data, the print preview screen is not provided.