Information processing device, control method, and program

Abstract

To solve the problem in which: when printing is performed by using a printer not designed for print data of a first format generated by first printing software, operability may be reduced.SOLUTION: An information processing apparatus can execute first printing software that receives an instruction from an application and generates print data of a first format, and when instructed to execute printing using a first printing device capable of interpreting the print data of the first format, transmits the print data of the first format generated by the first printing software to the first printing device. When instructed to execute printing using a second printing device incapable of interpreting the print data of the first format, the information processing apparatus receives print data of the first format generated by first printing software in which a print queue for the second printing device is registered and generates print data of a second format that can be interpreted by the second printing device, and transmits the generated print data to the second printing device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a control method, and a program. [Background technology]

[0002] Conventionally, there exists a printing environment in which a personal computer (hereinafter referred to as a PC) is connected to a printer. In this printing environment, Patent Document 1 discloses a technology that allows printing to be performed using a printing function (hereinafter referred to as an OS standard printing function) that is provided as standard in an operating system (hereinafter referred to as an OS), without requiring printer-specific software provided by the printer vendor. Note that printer-specific software is sometimes called a printer driver. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication 2015-508921 Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 does not take into consideration information management when a printer that cannot interpret print data in a predetermined format corresponding to the OS's standard print function is connected to a PC. As a result, there is a risk that operability will be reduced when a user prints using a printer that cannot interpret print data in a predetermined format corresponding to the OS's standard print function. [Means for solving the problem]

[0005] In order to solve the above problems, the program of the present invention comprises: a computer of an information processing device that is capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and that, when instructed to execute printing using a first printing device that can interpret the print data in the first format, transmits the print data in the first format generated by the first printing software to the first printing device; a receiving means for receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to print using a second printing device that cannot interpret the print data in the first format; a generating means for generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received by the receiving means; a transmission means for transmitting the print data in the second format generated by the generation means to the second printing device; and , a control means for executing a process for registering a print queue for the second printing device in the first printing software when the second printing device is not displayed as a candidate for printing device selection on a screen displayed in response to an instruction from the application; Function as. [Effects of the Invention]

[0006] According to the present invention, it is possible to improve the operability of a printing operation using a printer that cannot interpret print data in a first format generated by first printing software. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a diagram showing the overall configuration of a printing system according to an embodiment of the present invention. [Figure 2] FIG. 10 is a diagram illustrating an example of a screen of a print conversion utility. [Figure 3] FIG. 10 is a diagram illustrating an example of a screen of the OS printing system. [Figure 4] FIG. 2 is a diagram illustrating a print setting screen of the OS printing system. [Figure 5] FIG. 10 is a diagram showing a startup process flow of the print conversion utility. [Figure 6] FIG. 10 is a diagram showing a guide dialog provided by the print conversion utility. [Figure 7] FIG. 10 is a diagram showing a startup process flow of the print conversion utility. [Figure 8] FIG. 10 is a diagram showing a guide dialog provided by the print conversion utility. [Figure 9] FIG. 10 is a diagram showing a guide dialog provided by the print conversion utility. [Figure 10] FIG. 10 is a diagram showing a guide dialog provided by the print conversion utility. [Figure 11] FIG. 10 is a diagram showing a startup process flow of the print conversion utility. [Figure 12] FIG. 10 is a diagram showing a guide dialog provided by the print conversion utility. [Figure 13] FIG. 10 is a diagram showing a startup process flow of the print conversion utility. [Figure 14] FIG. 10 is a diagram illustrating a startup processing flow of the uninstaller. [Figure 15] FIG. 2 is a hardware configuration diagram of an information processing device. DETAILED DESCRIPTION OF THE INVENTION

[0008] The following describes in detail preferred embodiments of the present invention with reference to the attached images. Note that the following embodiments do not limit the scope of the present invention, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the present invention.

[0009] <Embodiment 1> FIG. 1 shows the overall configuration of a printing system according to this embodiment. PC01, printer 20, printer 30, and printer 40 are connected via a network 12 and can communicate with each other. In this embodiment, a LAN (Local Area Network) is assumed as the network, but a WAN (Wide Area Network) may also be used. Furthermore, the network connection may be wired or wireless, or a mixture of these. PC01 controls printers 20-40 connected via network 12.

[0010] Although not shown in Fig. 1, an operating system (OS) is built into PC01, and each block within PC01 is managed by the OS. Here, PC01 has the hardware configuration (Fig. 15) that is included in a general information processing device.

[0011] FIG. 15 is a block diagram showing the hardware configuration of the PC (information processing device) 01. The CPU 301 is a central processing unit that controls the following components. The disk device 302 stores various files, as well as an application program 312, a database 313, and an OS that are read by the CPU 301. The external disk reader 303 is a device for reading information, such as files, stored on an external storage medium such as an SD card. The memory 304 is composed of RAM or the like, and performs temporary storage and buffering of data as needed by the CPU 301. The display unit 305 is composed of, for example, an LCD, and displays various information. The operation unit 306 includes a keyboard, mouse, and the like for a user to perform various input operations. The network communication unit 307 is connected to a network such as the Internet via a network connection unit 308 and performs various communications. The network communication unit 307 supports both wired and wireless LANs. In the case of a wired LAN, the network connection unit 308 is a connector for connecting a wired LAN cable. In the case of a wireless LAN, the network connection unit 308 is an antenna. The network connection unit 308 may have both wired LAN and wireless LAN functions. The USB communication unit 310 is connected to various peripheral devices via a USB connection unit 311 and performs various communications. The above-mentioned units are interconnected by a bus 309. In this embodiment, the OS installed in the PC01 is assumed to be macOS (registered trademark).

[0012] Next, the software configuration of the PC 01 will be described. The PC 01 includes and is capable of executing an application 02, an OS printing system 03, a network (NW) communication control unit 06, a print conversion utility 08, and an uninstaller 11 for the print conversion utility 08. The uninstaller 11 may be incorporated into the print conversion utility 08. The OS printing system 03, including the OS-standard print control unit 04, is a standard module included in the OS. In other words, the user does not need to install the OS printing system 03 and the OS-standard print control unit 04 separately; they are installed when the OS is installed. For this reason, the OS printing system 03, including the OS-standard print control unit 04, is sometimes referred to as OS-standard printing software. The print queue 05 of the printer 30 and the OS-standard print control unit 04 are managed by the OS printing system 03. The print conversion utility 08, including the vendor driver 09, is used to print on a printer that cannot interpret print data in a specified format that conforms to the OS-standard print function, and is installed on the PC 01 at the user's instruction. The OS printing system 03 sequentially processes print requests from the application 02 as jobs. When a user requests printing of application data created by the application 02, the request is submitted to the OS printing system 03 as a print job. When the OS printing system 03 receives the print job, the OS standard printing control unit 04 generates print data in a format conforming to the OS standard printing function. If a printer capable of interpreting print data in a format conforming to the OS standard printing function is selected at the time of the print request from the application 02, the OS printing system 03 sends the print data generated by the OS standard printing control unit 04 to the printer. Therefore, for example, the OS printing system 03 can operate on the PC 01 without an installation process instructed by the user. Note that in this embodiment, the OS standard printing function is also referred to as a predetermined printing function. Note that in this embodiment, a printer that cannot interpret print data in a format conforming to the OS standard printing function is also referred to as an unsupported printer.In addition, printers that can interpret print data in a format that conforms to the OS's standard printing functions are sometimes called supported printers.

[0013] Next, we will explain the process when the printer selected when a print request is made from an application is an unsupported printer. After print data in a format conforming to the OS standard printing function is generated by the OS standard print control unit 04, the OS print system 03 sends the print data to the print conversion utility 08. The print conversion utility 08 then converts the print data into a vendor-specific format and sends it to the printer via the NW communication control unit 06. In other words, the print data generated by the OS standard print control unit 04 and the print data generated by the print conversion utility 08 are different.

[0014] In addition to the above, the print conversion utility 08 can also convert image data 07 specified using a file print screen 70 described later in FIG. 2 into print data in a vendor-specific format and send it to the printer via the NW communication control unit 06.

[0015] Printer 20, printer 30, and printer 40 are configured with a NW communication control unit 21, a print control unit 22, and a printing unit 23. The print control unit 22 receives print data from PC01 via the NW communication control unit 21, and controls the printing unit 23 based on the print data to execute printing. Note that, although this embodiment assumes printing by inkjet printing, other methods such as electrophotography may also be used.

[0016] When a supported printer is selected, the user can easily print without using the print conversion utility 08. On the other hand, when an unsupported printer is selected, the print conversion utility 08 is used to realize the printing process.

[0017] To use the print conversion utility 08 from the application 02, two print queues must be registered: the print queue 05 of the OS standard printing function for receiving print requests from the application 02, and the print queue 10 of the print conversion utility. If these two print queues are not registered, printing cannot be performed from the application 02 using the print conversion utility 08.

[0018] The print conversion utility 08 can also generate print data for image data 07 specified using the file print screen 70 in Fig. 2. When printing image data specified using the file print screen 70, it is necessary to register the print queue 10 of the print conversion utility, but it is not necessary to register the print queue 05 of the OS standard print function.

[0019] When the print conversion utility 08 is installed, the print conversion utility uninstaller 11 is also installed at the same time. To uninstall the print conversion utility 08, the uninstaller 11 is started to perform the uninstallation process.

[0020] In this embodiment, printer 20 is a supported printer, and printers 30 and 40 are unsupported printers. That is, printer 20 can interpret print data generated by the OS standard print control unit 04. Therefore, when printing from application 02 to printer 30, both print queue 05 of the OS standard print function and print queue 10 of the print conversion utility must be registered. That is, when printing is instructed to printer 30 using application 02, print data is sent to printer 30 via OS print system 03 and print conversion utility 08. That is, printers 30 and 40 can interpret print data generated by the print conversion utility 08.

[0021] An example of a process for a user to register the print queue 10 of the print conversion utility 08 will now be described.

[0022] FIG. 2 shows an example of a screen provided by the print conversion utility 08. The printer list screen 50 displays the names 51 of printers registered in the print conversion utility 08, a "Print File" button 52 for directly printing image data 07, and a "Settings" button 53 for configuring the printer. The printer list screen 50 also displays an "Add" button 54 for registering a printer and a "Delete" button 55 for deleting a printer. When the user presses the "Print File" button 52, the file print screen 70 is displayed. The user presses the "Browse" button 71 to specify the image data 07 to be printed. Then, when the user presses the "Print" button 73, the print conversion utility 08 converts the image data 07 into print data in a vendor-specific format and sends it to the printer 30. When the "Cancel" button 72 is pressed, the file print screen 70 is closed without printing.

[0023] When the "Settings" button 53 on the printer list screen 50 is pressed, the print conversion utility 08 opens a printer settings screen 80. When the "Add" button 54 is pressed, the print conversion utility 08 displays a printer registration screen 60.

[0024] The printer registration screen 60 has a printer list 61, which displays information about unsupported printers connected to PC01. In this embodiment, printer 30 and printer 40 are displayed. The print conversion utility 08 stores printer information about unsupported printers in advance. Of the printers included in the printer information, unsupported printers connected to PC01 are displayed in the printer list 61. The print conversion utility 08 may also acquire capability information about printers connected to PC01 and determine unsupported printers from the capability information.

[0025] When the user presses the "Register" button 63, the selected printer is registered in the print conversion utility 08. In this embodiment, printer 30 is already registered in the print conversion utility 08. When a printer is registered in the print conversion utility 08, the print conversion utility 08 acquires capability information from the printer that is the target of operation. When the OS printing system 03 sends a capability information acquisition request to the print conversion utility 08, the print conversion utility 08 receives the capability information acquisition request. Therefore, the print conversion utility 08 adds support information (support information) for OS standard printing functions that it has internally generated based on the capability information acquired from the printer to the capability information that it sends back to the OS printing system 03, and then sends the response to the OS printing system 03. At this point, the print queue 10 of the print conversion utility 08 is registered.

[0026] Furthermore, although the print conversion utility 08 can also register the print queue 05 of the OS standard printing function in the OS print system, in this embodiment the print conversion utility 08 does not register the print queue 05 in the OS print system 03. The OS print system 03 registers the print queue 05. This will be explained in detail later. When the "Delete" button 55 is pressed, the print queue 10 of the print conversion utility for the selected printer is deleted from the print conversion utility 08. The printer name, etc. are also deleted from the printer list.

[0027] Next, the process by which the OS printing system 03 registers a print queue 05 will be described. FIG. 3 shows a printer list screen 90 provided by the OS printing system 03. The OS printing system 03 has a printer list 91 for adding and deleting available printers. The OS printing system 03 displays all printers selectable for printing in the printer list 91. When a user selects a printer in the printer list 91 and presses the "Delete" button 93, the OS printing system 03 deletes the print queue of the selected printer and also deletes the name of the selected printer from the printer list 91. When a user presses the "Add" button 92, the OS printing system 03 displays a printer registration screen 95. The OS printing system 03 displays supported printers connected to the PC 01 via the network in a registered printer list 96. The OS printing system 03 obtains capability information, including the printer name and compatibility with OS standard printing functions, from the connected printers 20-40 or print conversion utility 08. The OS printing system 03 then displays the names of the supported printers and their connection methods in the registered printer list 96. In this embodiment, the printer 30 is the target of operation of the print conversion utility 08, and the print conversion utility 08 responds to the OS printing system 03 with capability information in which "print conversion utility" has been added to the name acquired from the printer 30. Note that, although "print conversion utility" is described as the added identification information in this embodiment, other information may also be added. Note that by the print conversion utility 08 responding with the capability information of the printer 30, which is an unsupported printer, the OS printing system 03 identifies the printer 30 as a display target in the registered printer list 96, which will be described later.

[0028] Based on the capability information acquired from the print conversion utility 08, the OS printing system 03 displays "Printer 30 (Print Conversion Utility 08)" as the name of the printer 30 and "Network" as the connection method in the registered printer list 96. When the user selects a printer in the registered printer list 96 and presses the "Register" button 98, the OS printing system 03 creates and registers a print queue 05 of the OS standard printing function of the selected printer. The OS printing system 03 then displays the selected printer in the printer list 91 and closes the printer registration screen 95. When the user presses the "Cancel" button 97, the OS printing system 03 closes the printer registration screen 95 without registering the printer. In this embodiment, the print queue of the supported printer 20 and the print queue 05 of the printer 30 to which print data is sent via the print conversion utility 08 are registered in the OS printing system 03.

[0029] FIG. 4 shows the print setting screen of the OS printing system 03. The OS printing system 03 has a print setting screen 100 used when printing application data created by the application 02. The user can set the printer to print on using the printer selection menu 101. The OS printing system 03 displays available printers added to the printer list screen 90 in FIG. 3 as selectable printers. In this embodiment, printer 20, which is a supported printer, and printer 30, to which print data is sent via the print conversion utility 08, are registered as available printers, and these are displayed as selection candidates in the printer selection menu 101. The user can set the number of copies to print in the copy setting field 102. The user can set the pages to print using the page setting radio button 103 and the page specification field 104. The user can set the paper size to use for printing on the paper size setting menu 105. The user can set one of the paper sizes available for the printer selected in the printer selection menu 101: A4, A5, L size, or postcard. When the user presses the print button 107, a print job based on the settings on this screen is submitted to the OS printing system 03 and this screen is closed. When the user presses the cancel button 106, the print job is not submitted to the OS printing system 03 and this screen is closed.

[0030] Next, we will explain the process of notifying the user to register the print queue again when the print queue 05 registered in the OS print system 03 for the printer 30 to which print data is sent via the print conversion utility 08 is deleted by the user.

[0031] Fig. 5 is a flowchart showing the execution process of the print conversion utility 08. The flowcharts described herein are realized by the CPU 301 reading and executing a program related to the flowchart from the memory 304. The flowchart in Fig. 5 starts when the user starts the print conversion utility 08. The print conversion utility 08 is started when the user operates the icon for the print conversion utility 08 on the screen of the PC 01.

[0032] The print conversion utility 08 obtains (S01) the total number (A) of printers registered in the print conversion utility 08. In S02, the print conversion utility 08 initializes the index number (n=1), and in S03 starts a loop for the total number of printers.

[0033] In S04, the print conversion utility 08 determines whether the DeviceURI of the nth printer is registered in the print queue 05 of the OS standard printing function. For example, the print conversion utility 08 acquires the DeviceURIs of all print queues registered in the OS print system 03 from the OS print system 03. S04 is realized by determining whether the DeviceURI of the nth printer is included in the DeviceURI acquired from the OS print system 03. If it is determined that the DeviceURI of the nth printer is not included in the DeviceURI acquired from the OS print system 03, the print conversion utility 08 determines that the print queue 05 of the OS standard printing function is not registered, and proceeds to S05. Note that although the DeviceURI is described as the information to be used, other identification information may also be used. For example, a UUID may be used.

[0034] The print conversion utility 08 informs the user that the print queue 05 of the OS standard print function has not been registered, that printing can only be performed from image data 07 specified using the file print screen 70 of FIG. 2, and guides the user through the procedure for registering the print queue 05 of the OS standard print function (S05). Specifically, the print conversion utility 08 displays the guide dialog 110 of FIG. 6. Note that the information guided in S05 does not need to be all of this information. For example, it is sufficient if at least the operating procedure for registering the print queue 05 of the OS standard print function is guided. Alternatively, the user may be guided only through the procedure for registering the print queue 05 of the OS standard print function.

[0035] When the print conversion utility 08 recognizes that the OK button has been pressed on the screen of FIG. 6 (S06), it increments the index number (S07) and returns the process from S08 to S03.

[0036] It should be noted that the user may be notified of the registration of the print queue 05 by executing the process of FIG. 5 when the print queue 05 is not registered in the OS print system 03 to begin with.

[0037] As described above, in this embodiment, the print conversion utility 08 determines whether a print queue 05 of the OS standard print function corresponding to a printer managed by the print conversion utility 08 is registered. If it is determined that a print queue 05 of the OS standard print function corresponding to a printer managed by the print conversion utility 08 is not registered, the print conversion utility 08 guides the user through the procedure for registering the print queue 05 of the OS standard print function. In other words, step S07 is executed when an unsupported printer (e.g., printer 30) managed by the print conversion utility 08 is not displayed as a selection candidate in the selection menu 101 of the print setting screen 100 displayed in response to an instruction from the application 02. The user can easily register the print queue 05 of the OS standard print function by following this guidance. As a result, both the print queue 10 of the print conversion utility 08 and the print queue 05 of the OS print system are registered, and the user can print using the printer 30.

[0038] <Embodiment 2> Next, a second embodiment of the present invention will be described. In the first embodiment, when the print queue 05 of the printer to which print data is sent via the print conversion utility is not registered in the OS print system 03, the user had to manually register the print queue 05 in the OS print system 03 according to the procedure in Fig. 6. Taking this into consideration, in the second embodiment, a process for registering the print queue 05 without the user having to perform a manual operation will be described.

[0039] Note that this embodiment will be described with respect to differences from embodiment 1. Also, in this embodiment, it is assumed that the print conversion utility 08 can register, in the OS print system 03, the print queue 05 for the OS print system 03 of the printer registered using the printer registration screen of the print conversion utility 08 in FIG.

[0040] 7 is a diagram showing the startup process flow of the print conversion utility 08 in this embodiment. Note that S22 to S25 and S35 to S36 are the same as S01 to S04 and S07 to S08 in FIG.

[0041] If the print conversion utility 08 determines in S25 that the DeviceURI of the n-th printer is not registered in the OS printing system 03, the process proceeds to S26. The print conversion utility 08 then informs the user that the print queue 05, which is a standard printing function of the OS, is not registered and asks whether the user wants to register the print queue 05 in the OS printing system. Specifically, the print conversion utility 08 displays the information dialog 120 shown in FIG. 8.

[0042] The print conversion utility 08 accepts a user selection in the information dialog 120 of FIG. 8 (S27) and determines whether the "OK" button 122 has been pressed (S28). If the "OK" button 122 has been pressed, the print conversion utility 08 registers the print queue 05 of the OS standard printing function of the target printer in the OS printing system (S29). Specifically, the print conversion utility 08 notifies the OS printing system 03 of the DeviceURI of the nth printer and instructs the OS printing system 03 to register the print queue of the nth printer. This processing registers the print queue of the nth printer (e.g., print queue 05) in the OS printing system 03. In other words, the print conversion utility 08 displays a screen for confirming that the nth printer is to be registered in the OS printing system 03. If the user instructs on this confirmation screen to register the nth printer, the print conversion utility 08 issues an instruction to the OS printing system 03 to register the print queue of the nth printer in the OS printing system 03.

[0043] On the other hand, if it is determined in S28 that the cancel button 121 has been pressed (S28-No), the print conversion utility 08 asks in S30 whether to delete the print queue 10 of the print conversion utility of the target printer. Specifically, the print conversion utility 08 displays the information dialog 130 shown in FIG. 9.

[0044] The print conversion utility 08 accepts a user selection in the guide dialog 130 of Fig. 9 (S31), and determines whether the "OK" button 122 has been pressed (S32). If it is determined that the "OK" button 132 has been pressed, the print conversion utility 08 deletes the print queue 10 of the print conversion utility for the nth printer in S33. In other words, the print conversion utility 08 removes the nth printer, which is currently managed as a managed printer, from the list of managed printers.

[0045] On the other hand, if it is determined in S32 that the "Cancel" button 131 has been pressed, then in S34 the print conversion utility 08 notifies the user that printing is only possible from the image data 07 specified using the file print screen 70 of FIG. 2. Specifically, the print conversion utility 08 displays the information dialog 140 of FIG. 10. If the user presses the "OK" button 141 in the information dialog 140, the process proceeds to S35. Note that a cancel button may also be displayed in FIG. 10. If the cancel button is pressed here, the print conversion utility 08 may execute the process again from S26. After S35 is completed, the process of FIG. 7 returns from S36 to S24, and the above-described process is performed for the next target printer.

[0046] As described above, if the print queue 05 of an unsupported printer managed by the print conversion utility 08 is not registered in the OS print system 03, the print conversion utility automatically registers the print queue 05 in the OS print system 03. Therefore, according to this embodiment, the convenience of the operation of registering the print queue 05 in the OS print system 03 can be improved. Furthermore, if the user does not select to register the print queue 05, the print queue 10 of the print conversion utility 08 is deleted. If deletion is not performed, a message is displayed indicating that only image data specified using the file print screen 70 in FIG. 2 can be printed. These processes reduce the user's operational burden on the print queue 10 of the print conversion utility 08.

[0047] <Embodiment 3> Next, a third embodiment of the present invention will be described. In this embodiment, a process for not leaving the print queue 05 of the OS standard print function after deleting the print queue 10 from the print conversion utility 08 will be described. Specifically, the print conversion utility 08 guides the user to delete the print queue 05 of the OS standard print function. Note that in this embodiment, differences from the above-described embodiments will be described.

[0048] FIG. 11 shows the startup process flow of the print conversion utility 08 in this embodiment. In S41, the print conversion utility 08 displays the printers currently registered in the print conversion utility 08 on the printer list screen 50. When the print conversion utility 08 detects in S42 that the user has pressed the "Delete" button 55 for the printer selected on the printer list screen 50, it displays the information dialog 130 of FIG. 9 in S43. If the print conversion utility 08 determines that the user has pressed the "OK" button 132 on the information dialog 130 (S43-Yes), the print conversion utility 08 deletes the print queue 10 for the printer selected on the printer list screen 50 and proceeds to S45. In S45, the print conversion utility 08 determines whether a print queue 05 of the OS standard printing function corresponding to the printer deleted in S44 exists in the OS printing system 03. For example, the print conversion utility 08 obtains the DeviceURIs of all print queues registered in the OS printing system 03 from the OS printing system 03. Then, step S45 is realized by determining whether the DeviceURI of the printer selected to be deleted is included in the DeviceURI acquired from the OS printing system 03.

[0049] If a print queue 05 of the OS standard printing function exists in the OS printing system 03, the print conversion utility 08 instructs the user in S46 to delete the print queue 05 of the OS standard printing function. Specifically, the print conversion utility 08 displays a guide dialog 150 for the OS standard printing function in FIG. 12. When the user presses the OK button 151 on the guide dialog 150, the print conversion utility 08 closes the guide dialog 150. In other words, when the print queue 10 of an unsupported printer is deleted (removed from management), the print conversion utility 08 executes processing to remove information about that printer (print queue 05) from the OS printing system 03.

[0050] As described above, in this embodiment, when a print queue 10 registered in the print conversion utility 08 is deleted by the user, the user is prompted to delete the print queue 05 of the OS standard print function that corresponds to the printer to be deleted. This allows the user to easily delete the print queue 05 of the OS standard print function.

[0051] <Embodiment 4> Next, a fourth embodiment of the present invention will be described. In the third embodiment, when a print queue 10 is deleted from the print conversion utility, the user is prompted to delete the print queue 10 of the OS standard print function corresponding to the deleted print queue 10. In this embodiment, when a print queue 10 of the print conversion utility 08 is deleted, the print conversion utility 08 automatically deletes the print queue 05 of the OS standard print function corresponding to the deleted print queue 10. In other words, the user is not prompted to delete the print queue 05 of the OS standard print function. Note that this embodiment will be described in terms of differences from the above-described embodiments. FIG. 13 is a diagram showing the startup process flow of the print conversion utility 08 in this embodiment. Steps S50 to S55 and S57 are the same as steps S40 to S45 and S47 in FIG. 11, and therefore will not be described here.

[0052] If the print conversion utility 08 determines in S55 that a print queue 05 of the OS standard printing function corresponding to the deleted print queue 10 exists, the process proceeds to S56. In S56, the print conversion utility 08 deletes the print queue 05 of the OS standard printing function corresponding to the deleted print queue 10. Specifically, the print conversion utility 08 sends the DeviceURI of the printer to be deleted and a deletion instruction for the print queue 05 of the printer to be deleted to the printing system. This process deletes the print queue 05 of the printer to be deleted from the OS printing system 03. Note that, in this embodiment, the process of deleting the print queue 05 has been described, but it is sufficient that the print queue 05 is no longer managed by the OS printing unit 13. Therefore, the print conversion utility 08 may instruct the OS printing system 03 to remove the print queue 05 from the management list. In other words, when the print queue 10 of an unsupported printer is deleted (removed from the management list), the print conversion utility 08 executes a process to remove information about that printer (print queue 05) from the OS printing system 03.

[0053] As described above, in this embodiment, when a print queue 10 registered in the print conversion utility is deleted by a user, the print queue 05 of the OS standard printing function that corresponds to the deleted print queue 10 is automatically deleted. This reduces the amount of user operation required to delete the print queue 05.

[0054] <Embodiment 5> Next, a fifth embodiment of the present invention will be described. In this embodiment, when uninstalling the print conversion utility 08, the print queue 10 of the OS standard print function to which print data was sent via the print conversion utility 08 is deleted. Note that in this embodiment, differences from the above-described embodiments will be described.

[0055] 14 is a diagram showing the startup processing flow of the uninstaller 11 of the print conversion utility 08 in this embodiment. When the user starts the uninstaller 11 of the print conversion utility 08, the process proceeds to S60, where the startup processing begins.

[0056] In S61, the uninstaller 11 obtains the total number (A) of printers registered in the print conversion utility 08, and in S62 starts a loop for the total number of printers. In S63, the uninstaller 11 determines whether the Device URI of the nth printer is registered in the print queue 05 of the OS standard printing function. For example, the print conversion utility 08 obtains the Device URIs of all print queues registered in the OS print system 03 from the OS print system 03. Then, S63 is realized by determining whether the Device URI of the nth printer is included in the Device URI obtained from the OS print system 03.

[0057] If the uninstaller 11 determines that the print queue 05 of the OS standard print function corresponding to the nth printer is registered (S63-Yes), it deletes the print queue 05 of the OS standard print function of printer (n) (S64). After S64 is executed, or if the determination in S63 is No, the process in FIG. 14 proceeds to S65.

[0058] The above process is repeated for the total number of printers acquired. When Loop 1 ends, the process proceeds to S67, where the uninstaller 11 uninstalls the print conversion utility 08.

[0059] As described above, in this embodiment, when the print conversion utility 08 is uninstalled, the uninstaller 11 deletes the print queue 05 of the OS standard print function that corresponds to the printer to which print data is sent via the print conversion utility. This process has the effect of reducing the possibility that an unnecessary print queue 05 of the OS standard print function will remain.

[0060] <Other embodiments> The present invention can also be realized by supplying software (programs) that realize the functions of the above-described embodiments to a system or device via a network or various storage media, and having the computer in the system or device read and execute the programs. In this case, the programs and the storage media storing the programs constitute the present invention. The computer in the system or device is, for example, a CPU or MPU. [Explanation of symbols]

[0061] 03 OS printing system 08 Print Conversion Utility

Claims

1. a computer of an information processing device that is capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and that, when instructed to execute printing using a first printing device that can interpret the print data in the first format, transmits the print data in the first format generated by the first printing software to the first printing device; a receiving means for receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to execute printing using a second printing device that cannot interpret the print data in the first format; a generating means for generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received by the receiving means; a transmitting means for transmitting the print data in the second format generated by the generating means to the second printing device; a control means for executing a process for registering a print queue for the second printing device in the first printing software when the second printing device is not displayed as a candidate for printing device selection on a screen displayed in response to an instruction from the application; A program to function as a

2. The control means executes a first process for controlling the registration of a print queue for the second printing device in the first printing software as a process for registering the print queue for the second printing device in the first printing software.

2. The program according to claim 1 .

3. The first process is a process of instructing the first printing software to register a print queue for the second printing device in the first printing software.

3. The program according to claim 2.

4. 4. The program according to claim 2, wherein the control means executes the first process after displaying a screen for confirming that the second printing device is to be registered in the first printing software.

5. The program according to any one of claims 1 to 4, characterized in that the control means executes a second process of controlling to display an operating procedure for registering a print queue for the second printing device in the first printing software as a process for registering a print queue for the second printing device in the first printing software.

6. The computer of the information processing device, a management means for managing printing devices that cannot interpret print data in the first format, including the second printing device, as management targets; 6. The program according to claim 1, further functioning as:

7. a computer of an information processing device that is capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and that, when instructed to execute printing using a first printing device that can interpret the print data in the first format, transmits the print data in the first format generated by the first printing software to the first printing device; a receiving means for receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to execute printing using a second printing device that cannot interpret the print data in the first format; a generating means for generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received by the receiving means; a transmitting means for transmitting the print data in the second format generated by the generating means to the second printing device; a management means for managing printing devices that cannot interpret print data in the first format, including the second printing device, as management targets; A program to function as a

8. The computer of the information processing device, an exclusion means for excluding the second printing device, which is managed by the management means as a management target, from the management target when a user instructs not to register the second printing device in the first printing software; 8. The program according to claim 6, further functioning as:

9. the management means manages print queues of the printing devices to be managed; A program according to any one of claims 6 to 8, characterized in that the sending means sends the print data in the second format to the second printing device when a print queue for the second printing device registered in the first printing software and a print queue for the second printing device managed by the management means exist in the information processing device.

10. The computer of the information processing device, a notification means for adding predetermined identification information to the name of a printing device that cannot interpret print data in the first format and notifying the first printing software of the name; 10. The program according to claim 1, further functioning as:

11. a computer of an information processing device that is capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and that, when instructed to execute printing using a first printing device that can interpret the print data in the first format, transmits the print data in the first format generated by the first printing software to the first printing device; a receiving means for receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to execute printing using a second printing device that cannot interpret the print data in the first format; a generating means for generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received by the receiving means; a transmitting means for transmitting the print data in the second format generated by the generating means to the second printing device; a notification means for adding predetermined identification information to the name of a printing device that cannot interpret print data in the first format and notifying the first printing software of the name; A program to function as a

12. 12. The program according to claim 1, wherein the second format is a format specific to a vendor of a printing device.

13. a computer of an information processing device that is capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and that, when instructed to execute printing using a first printing device that can interpret the print data in the first format, transmits the print data in the first format generated by the first printing software to the first printing device; a receiving means for receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to execute printing using a second printing device that cannot interpret the print data in the first format; a generating means for generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received by the receiving means; a transmitting means for transmitting the print data in the second format generated by the generating means to the second printing device; A program for functioning as The second format is a format specific to a vendor of a printing device.

14. 14. The program according to claim 1, wherein the first printing software is OS-standard printing software that is standard for an operating system (OS) that runs on the information processing apparatus.

15. 15. The program according to claim 1, wherein the program is included in second printing software that is different from the first printing software.

16. A computer-readable storage medium storing the program according to any one of claims 1 to 15.

17. An information processing device capable of executing first printing software that generates print data in a first format in response to instructions from an application, and that, when instructed to print using a first printing device that can interpret the print data in the first format, transmits the print data in the first format generated by the first printing software to the first printing device, characterized in that the information processing device has each means described in any one of claims 1 to 15.

18. A control method for an information processing device capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and transmitting the print data in the first format generated by the first printing software to a first printing device that can interpret the print data in the first format when an instruction to execute printing using the first printing device is received, the method comprising: a receiving step of receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to print using a second printing device that cannot interpret the print data in the first format; a generating step of generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received in the receiving step; a transmitting step of transmitting the print data in the second format generated in the generating step to the second printing device; a control step of executing a process for registering a print queue for the second printing device in the first printing software when the second printing device is not displayed as a selection candidate for the printing device on a screen displayed in response to an instruction from the application; a function of specific software different from the first printing software.

19. A control method for an information processing device capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and transmitting the print data in the first format generated by the first printing software to a first printing device that can interpret the print data in the first format when an instruction to execute printing using the first printing device is received, the method comprising: a receiving step of receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to print using a second printing device that cannot interpret the print data in the first format; a generating step of generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received in the receiving step; a transmitting step of transmitting the print data in the second format generated in the generating step to the second printing device; a management step of managing printing devices that cannot interpret print data in the first format, including the second printing device, as management targets; a function of specific software different from the first printing software.

20. A control method for an information processing device capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and transmitting the print data in the first format generated by the first printing software to a first printing device that can interpret the print data in the first format when an instruction to execute printing using the first printing device is received, the method comprising: a receiving step of receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to print using a second printing device that cannot interpret the print data in the first format; a generating step of generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received in the receiving step; a transmitting step of transmitting the print data in the second format generated in the generating step to the second printing device; a notification step of adding predetermined identification information to the name of the printing device that cannot interpret the print data in the first format and notifying the first printing software of the name; a function of specific software different from the first printing software.

21. A control method for an information processing device capable of executing first printing software that generates print data in a first format in response to an instruction from an application, and transmitting the print data in the first format generated by the first printing software to a first printing device that can interpret the print data in the first format when an instruction to execute printing using the first printing device is received, the method comprising: a receiving step of receiving the print data in the first format generated by the first printing software in which a print queue for the second printing device is registered when a command is issued to print using a second printing device that cannot interpret the print data in the first format; a generating step of generating print data in a second format that can be interpreted by the second printing device based on the print data in the first format received in the receiving step; a transmitting step of transmitting the print data in the second format generated in the generating step to the second printing device; as a function of specific software different from the first printing software, The second format is a vendor-specific format for the printing device.

2. A method for controlling an information processing apparatus comprising:

Images