Printing device, printing system and program

Abstract

To provide a technique that can suppress burdens in reconstructing a printing system even when a printing device is renewed.SOLUTION: A CPU, when determining that PJL data included in a printing job obtained through a communication IF or a USB IF match unconverted PJL data registered in conversion-rule data in a flash ROM (S32: Yes) and when determining that the type of converted PDL data that is associated with the unconverted PJL data in the conversion rule matches the type of PDL data established in PJL data conversion processing (S33: Yes), converts the conversion-suspended PJL data for which conversion is suspended into the converted PDL data associated with the unconverted PJL data matching the conversion-suspended PJL data in the conversion rule (S34).SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present disclosure relates to a technique for processing data written in a printer job language (hereinafter referred to as PJL). [Background technology]

[0002] Patent document 1 describes a technology in which a printing device stores new PJL data sent from a PC and the processing corresponding to that new PJL data in a PJL dictionary, and when new PJL data is received from the PC, the printing device performs processing that corresponds to the received new PJL data in the PJL dictionary. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-171757 A Summary of the Invention [Problem to be solved by the invention]

[0004] Printing devices are undergoing changes such as improvements in performance and functionality, as well as diversifying the value they provide. However, in a printing system that includes a printing device, updating the printing device to accommodate the above changes imposes a heavy burden on the printing system in order to reconstruct the printing system.

[0005] Therefore, the present application has been proposed to solve the above problem, and aims to provide technology that does not impose a large burden on the user in reconstructing the printing system even when a printing device is updated. [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, the present application provides a printing device that includes an external interface, a non-volatile memory, and a computer, and the computer acquires a print job having PJL data and PDL data via the external interface and executes a print process in accordance with the acquired print job, and the non-volatile memory stores a conversion rule in which non-target PJL data that is not supported by the printing device is associated with target PDL data that is supported by the printing device, and the computer performs an acquisition process of acquiring the print job via the external interface, and a conversion rule for converting the PDL data acquired by the acquisition process. and in a first case where PJL data included in the acquired print job matches non-target PJL data registered in the conversion rule in the non-volatile memory, a first conversion process is executed to convert the PJL data into target PDL data that is associated with the non-target PJL data that matches the PJL data in the conversion rule, and a print process is executed using the target PDL data that is included in the print job acquired by the acquisition process and that is converted from the non-target PJL data by the first conversion process, without executing a process according to the PJL data itself that is the matched target in the first case.

[0007] The non-volatile memory stores conversion rules that associate non-target PJL data that is not supported by the printing device with target PDL data that is supported by the printing device.The computer acquires a print job having PJL data and PDL data via an external interface, and in a first case in which the PJL data included in the acquired print job matches the non-target PJL data registered in the conversion rules in the non-volatile memory, converts the PJL data into target PDL data that is associated with the non-target PJL data that matches the PJL data in the conversion rules.The computer then executes a print process using the converted target PDL data, and does not execute a process according to the PJL data that matches in the first case. The technology disclosed in this specification can be realized in various forms, for example, in addition to a printing system, it can be realized in the form of a program, a storage medium on which a program is stored, and the like. Effect of the Invention

[0008] According to the printing device and the like of the present application, it is possible to provide a printing device and the like that does not increase the burden of reconstructing the printing system even when the printing device is updated. [Brief description of the drawings]

[0009] [Figure 1] FIG. 2 is an explanatory diagram illustrating a main electrical configuration of the printing device. [Diagram 2] FIG. 10 is an explanatory diagram showing an example of a print job having PCL data before conversion. [Diagram 3] FIG. 11 is an explanatory diagram showing an example of a print job having converted PCL data. [Figure 4] FIG. 11 is an explanatory diagram showing an example of a print job having PCLXL data before conversion. [Diagram 5] FIG. 11 is an explanatory diagram showing an example of a print job having converted PCLXL data. [Figure 6] FIG. 11 is an explanatory diagram illustrating an example of conversion rule data. [Figure 7] 4 is a flowchart showing a main routine executed by a CPU. [Figure 8] 13 is a flowchart showing a PJL data conversion process. [Figure 9] 13 is a flowchart showing a PJL data analysis process. [Figure 10] 13 is a flowchart showing a PJL to PDL conversion process. [Figure 11] 13 is a flowchart showing a converted PDL data embedding process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] A printing device, a printing system, and a program according to an embodiment of the present invention will be described below with reference to the drawings. A main electrical configuration of the printing device will be described with reference to FIG. 1. The printing device 10 includes a print engine 11, a flash ROM 12, an NVRAM 14, an image processing circuit 15, a user IF (abbreviation of interface) 16, a communication IF 17, a USB IF 18, a bus 19, a control unit 20, a RAM 22, and a ROM 23. The print engine 11 is an engine for printing an image on a recording medium such as a sheet, and employs a printing method such as an electrophotographic method, an inkjet method, or a thermal method. The image processing circuit 15 performs RIP (abbreviation of Raster Image Processor) processing on image data related to the PDL unit 31b (FIG. 3) or the PDL unit 33b (FIG. 5), and converts the image data into drawing data, which is raster data corresponding to pixels to be printed on a recording medium such as a sheet. The converted drawing data is output to the print engine 11. The NVRAM 14 is a non-volatile memory for storing print setting information and the like. The user IF 16 is, for example, a touch panel, and has a function of displaying messages and a function of accepting operations by a user. The communication IF 17 is connected to the information processing device 40 via a LAN line L1 so that they can communicate with each other. As a method of communication between the printing device 10 and the information processing device 40, a communication protocol such as Bluetooth (registered trademark) can also be used. The information processing device 40 is, for example, a PC or a smartphone. The USB IF 18 is hardware for communicating with a connected device based on the USB standard.

[0011] The control unit 20 is composed of a CPU 21 and the like. The control unit 20 controls the print engine 11 according to the print setting information stored in the NVRAM 14. The control unit 20 also controls communication with the information processing device 40 via the communication IF 17. The CPU 21 or the control unit 20 including the CPU 21 is an example of a computer of the present invention, and the flash ROM 12 is an example of a non-volatile memory of the present invention. The information processing device 40 is an example of an information processing device of the present invention, and the printing device 10 and the information processing device 40 are an example of a printing system of the present invention. The ROM 23 stores a program 24 that causes the CPU 21 to execute a main routine (FIG. 7) and subroutines (FIGS. 8 to 11) described later. The RAM 22 has a storage area in which the conversion rule data 50 read from the flash ROM 12 is expanded, a work area in which the program 24 read from the ROM 23 is expanded, and the like. The control unit 20, RAM 22, ROM 23, flash ROM 12, NVRAM 14, print engine 11, image processing circuit 15, user IF 16, communication IF 17 and USB IF 18 are interconnected by a bus 19. The communication IF 17 and USB IF 18 are examples of external interfaces of the present invention, and the program 24 is an example of a program of the present invention.

[0012] The conversion rule data 50 may be stored in a computer-readable storage medium and provided to the printing device 10 from the storage medium. The program 24 may also be stored in a computer-readable storage medium and provided to the printing device 10 from the storage medium and executed by the CPU 21. A computer-readable storage medium is a non-transitory medium. Non-transitory media include storage media such as CD-ROMs, DVD-ROMs, and USB memories. Non-transitory media are also tangible media. On the other hand, an electrical signal carrying a program downloaded from a server on the Internet is a computer-readable signal medium, which is a type of computer-readable medium, but is not included in a computer-readable non-transitory storage medium. In the following description, the processes such as "judgment," "analysis," "reading," "expansion," "writing," "conversion," "reference," "save," "output," "transmission," "decision," "identification," "acquisition," "control," "setting," and "embedding" represent processes performed by the CPU 21. The processes performed by the CPU 21 also include hardware control via the OS. Note that "obtaining" is used as a concept that does not necessarily require a request. In other words, the process of CPU 21 receiving data without making a request is also included in the concept of "CPU 21 obtaining data." Furthermore, "data" in this specification is represented as a bit string that can be read by a computer. Data that has the same substantial meaning but different formats is treated as the same data. The same applies to "information" in this specification.

[0013] However, when the model of the printing device connected to the information processing device 40 is changed, the printing device may not operate as expected even if a print job is sent from the information processing device 40 to the printing device. One of the reasons for this is the compatibility of PJL data. For example, there are cases where a certain PJL data was supported by a printing device previously connected to the information processing device 40, but is not supported as PJL data by a newly connected printing device, but is supported as PDL data. In such a case, it is conceivable to install a driver that supports the new PJL data in the information processing device 40 in order to control the newly connected printing device, but the system administrator who manages the printing system wants to avoid changing the system program as much as possible because it may be a factor that hinders the normal operation of the system and requires a lot of effort. Therefore, the inventor of the present application has created a technology that allows the PJL data that was previously sent from the information processing device to the printing device to be converted into PDL data and used without changing the system program, even when the model of the printing device connected to the information processing device is changed. In order to use this technique, the printing device 10 of this embodiment stores conversion rule data 50 for converting PJL data into PDL data in the flash ROM 12 (FIG. 1). The conversion rule data 50 will be described later.

[0014] Next, the main routine executed by the CPU 21 of the control unit 20 will be described with reference to FIG. 7. The following describes the process executed by the CPU 21 when the print job 30 (FIG. 2) or the print job 32 (FIG. 4) transmitted from the information processing device 40 (FIG. 1) is received. The CPU 21 executes each process of the main routine (FIG. 7) and the subroutines (FIGS. 8 to 11) according to the program 24 (FIG. 1) stored in the ROM 23. In the following description, the steps of the process executed by the CPU 21 are abbreviated as S. Also, the PJL data acquired by the printing device 10 from the information processing device 40 is called acquired PJL data. Also, the PJL data that matches the acquired PJL data and is registered in the conversion rule data 50 is called pre-conversion PJL data. Also, the PJL data associated with the pre-conversion PJL data in the conversion rule data 50 is called post-conversion PJL data, and the PDL data associated with the pre-conversion PJL data is called post-conversion PDL data. Moreover, the converted PJL data and the converted PDL data are both data supported by the printing device 10.

[0015] The CPU 21 executes a data reception process to receive data transmitted from the information processing device 40 via an external interface such as the communication IF 17 and the USB IF 18 (FIG. 1) (S1), and judges whether a print job has been received (S2). An example of a print job is shown in FIG. 2 and FIG. 4. The print job 30 shown in FIG. 2 has a PJL section 30a composed of at least one PJL data, and a PDL section 30b composed of at least one PDL (short for Page Description Language) data. The data D1 "EC%-12345X@PJL" written at the beginning of the print job 30 is an opening command indicating that the PJL section 30a starts from the next line. Each PJL data constituting the PJL section 30a indicates the name of the creator of the print job 30, the name of the print job 30, print setting information, etc. The print setting information includes print setting information such as paper size, print direction, designation of color or monochrome printing, number of copies to be printed, and print quality. For example, the acquired PJL data D2 "@PJL SET MEDIASIZE=LETTER" indicates an instruction to set the paper size to "LETTER." "@PJL ENTER LANGUAGE=PCL" written on the last line of the PJL section 30a is PJL data indicating that the PJL section 30a ends and the PDL section 30b written in PCL (short for Printer Command Language) begins on the next line. PJL data D4 written after the PDL section 30b "EC%-12345X@PJL EOJ NAME="office-PDF(A&A4)_1Page.pdf"" is PJL data indicating the end of the print job 30. PJL data D5 "EC%-12345X" written on the next line after the PJL data D4 is PJL data indicating a break in the print job 30. 4 has a PJL section 32a and a PDL section 32b written in PCLXL. Note that, in addition to PCL and PCLXL, other page description languages ​​include PS (short for Post Script).CPU 21 determines that a print job has been received by determining that PJL data D1 exists in the received data and that data indicating that it is a print job exists after PJL data D1 (S2: Yes in FIG. 7). The data indicating that it is a print job may be either PJL data existing in PJL section 30a (FIG. 2) or PJL section 32a (FIG. 4). CPU 21 may also determine that a print job has been received by determining that data indicating PDL data exists in the received data (S2: Yes). The data indicating PDL data may be either PDL data existing in PDL section 30b (FIG. 2) or PDL section 32b (FIG. 4). When the CPU 21 determines that a print job has been received (S2: Yes), it determines whether or not the conversion rule data 50 (FIG. 6) has been read from the flash ROM 12 (FIG. 1) and loaded in the RAM 22 (S3), and when the determination is negative (S3: No), it executes a process of reading the conversion rule data 50 from the flash ROM 12 and loading it in the RAM 22 (S4). Next, the CPU 21 executes a PJL data conversion process (S5) that converts the acquired PJL data included in the print job received from the information processing device 40 in S1 into converted PJL data or converted PDL data. This PJL data conversion process is executed in a subroutine of this main routine (FIG. 8), and the process contents will be described later.

[0016] Next, after executing the PJL data conversion process (S5), the CPU 21 executes the RIP process according to the print job received from the information processing device 40 in S1 (S6), and executes print control according to the data generated by the RIP process (S7). The PJL data conversion process (S5) is performed based on the conversion rule data 50 (FIG. 6) stored in the flash ROM 12. Since the print control (S7) is executed after executing the PJL data conversion process (S5), the instruction contents indicated by the converted PJL data or the converted PDL data converted by the PJL data conversion process can be reflected in the print control. In detail, if the converted PJL data or the converted PDL data converted by the PJL data conversion process is data instructing a change in the setting contents of the print function, the CPU 21 changes the setting contents of the print function according to the instruction, executes print control based on the changed setting contents and the PDL part of the print job received in S1 (S7), and ends the main routine. Furthermore, when the CPU 21 determines that a print job has not been received (S2: No), it determines whether or not conversion rule data 50 (FIG. 6) has been received (S8). Here, if PJL data D1 (FIGS. 2 and 4) is present in the received data and data indicating that it is conversion rule data 50 is present after the PJL data D1, the CPU 21 determines that conversion rule data 50 has been received (S8: Yes), stores the received conversion rule data 50 in the flash ROM 12 (FIG. 1) (S9), and ends the main routine. Although the data indicating that it is conversion rule data 50 is not shown in FIGS. 2 and 4, it may be PJL data. In this way, the CPU 21 executes a conversion rule acquisition process (S1) that acquires the conversion rule data 50 via external interfaces (FIG. 1) such as the communication IF 17 and the USB IF 18, and a storage process (S9) that stores the conversion rule data 50 acquired by the conversion rule acquisition process in the flash ROM 12. After storing the conversion rule data 50 in the flash ROM 12 by the storage process, the CPU 21 executes a PJL data conversion process (FIG. 8) that converts pre-conversion PJL data into converted PJL data or converted PDL data using the stored conversion rule data 50.As a result, after storing the conversion rule data 50 in the flash ROM 12, the CPU 21 executes conversion of the acquired PJL data into converted PJL data or converted PDL data according to the stored conversion rule data 50, and can execute print control (S7) using the converted PJL data or converted PDL data. In other words, by simply executing the simple process of acquiring and storing the conversion rule data 50, it is possible to make the PJL data that was not supported before storing the conversion rule data 50 into a state where it can be supported. Furthermore, if the CPU 21 determines that the conversion rule data 50 has been read into the RAM 22 (S3: Yes), it executes the PJL data conversion process (S5) without executing the process of reading the conversion rule data 50 (S4). Furthermore, if the CPU 21 determines that the conversion rule data 50 has not been received (S8: No), it ends the main routine without executing the process of storing the conversion rule data 50 (S9). S1 executed by the CPU 21 is an example of the acquisition process or conversion rule acquisition process of the present invention. Moreover, S6 is an example of a generating process, S7 is an example of a printing process, and S9 is an example of a storing process.

[0017] Next, the PJL data conversion process executed by the CPU 21 in S5 of the main routine (FIG. 7) will be described with reference to FIG. 8. The CPU 21 analyzes the print job received in S1 of the main routine (FIG. 7) in order from the beginning. Taking FIG. 2 and FIG. 4 as an example, the print job is analyzed line by line from the first line. The CPU 21 then determines whether the position it is attempting to analyze is the end of the print job (S10), and if it determines that it is not the end (S10: No), it determines whether the next data to be analyzed is PJL data (S11). Here, if the CPU 21 determines that it is PJL data (S11: Yes), it acquires one PJL data from the PJL portion constituting the print job (S12). Since the CPU 21 analyzes the PJL data in order from the first PJL data, when executing S12 for the first time, it acquires the first PJL data (S12). Next, the CPU 21 judges whether the PJL data acquired in S12 is PJL data for which conversion is permitted (S13). A list of PJL data for which conversion is prohibited is stored in the flash ROM 12, and the CPU 21 permits conversion if the PJL data acquired in S12 is not included in the list. For example, PJL data that instructs uploading a file stored in the printing device 10 onto a network, PJL data that instructs deleting a file, etc. can be included in the list of PJL data for which conversion is prohibited. In this way, when the printing device 10 is connected to a network such as the Internet, it is possible to prevent attacks from malicious parties, such as file uploads and file deletions. In other words, the security of the printing device 10 can be improved.

[0018] Here, if the CPU 21 determines that the PJL data is permitted to be converted (S13: Yes), it executes a PJL data analysis process (S14). This PJL data analysis process is executed in a subroutine (FIG. 9) described later. Next, the CPU 21 determines whether or not the PJL data "ENTER LANGUAGE" indicating the end of the PJL section has been detected (S15), and if it determines that it has not been detected (S15: No), it returns to S10 and executes S10 to S14. The CPU 21 repeatedly executes S10 to S14 until it makes a positive determination in S15, and if it determines that the PJL data "ENTER LANGUAGE" has been detected (S15: Yes), it determines the type of PDL data constituting the PDL section (S16). That is, since the PJL data "ENTER LANGUAGE" indicates the type of PDL data, the CPU 21 can determine the type of PDL data by analyzing the detected PDL data "ENTER LANGUAGE" (S16). For example, the PJL data in the last line of the PJL section 30a shown in FIG. 2 is "@PJL ENTER LANGUAGE=PCL", which indicates that the type of PDL data is PCL, so the CPU 21 determines the type of PDL data to be PCL (S16). In this way, the CPU 21 analyzes the PJL data constituting the PJL section of the acquired print job in the order in which the PJL data is arranged, and executes a type determination process to determine the type of target PDL data based on the analysis result of the PJL data indicating the type of PDL data. Therefore, the CPU 21 can determine the type of PDL data by analyzing the PJL section before analyzing the PDL section. Also, if the CPU 21 determines that the next data is not PJL data (S11: No), it executes a PDL data type determination process (S17), executes a PJL→PDL conversion process (S18), and ends the PJL data analysis process. In S17, the CPU 21 executes a PDL data type determination process (S17) to determine the type of the converted PDL data by analyzing at least one PDL data constituting the PDL portion of the acquired print job, for example, the PDL data of the first line.If the print job does not have a PJL section and has only a PDL section, it is determined that the next data is not PJL data (S11: No). Also, if the print job has a PJL section and a PDL section, but does not have the PJL data "ENTER LANGUAGE" at the end of the PDL section, it is also determined that the next data is not PJL data (S11: No).

[0019] Next, the CPU 21 executes a PJL→PDL conversion process for converting the non-target PJL data into the target PDL data (S18), and ends the PJL data analysis process. The PJL→PDL conversion process in S18 is executed in a subroutine (FIG. 10) described later. If the CPU 21 determines that the PJL data is not permitted to be converted (S13: No), it executes S15 without executing the PJL data analysis process (S14) for the PJL data that is the subject of the determination. The PDL data type determination process executed in S17 may be rephrased as an auto-emulation process. In this way, the CPU 21 can determine the type of the converted PDL data even if the print job does not have a PJL part and has only a PDL part, or if the print job has a PJL part but does not have the PJL data "ENTER LANGUAGE". If the CPU 21 determines that the print job is at the end (S10: Yes), it ends the PJL data analysis process. S16 executed by the CPU 21 is an example of a type determination process of the present invention.

[0020] Next, the PJL data analysis process executed by the CPU 21 in S14 (FIG. 8) of the PJL data conversion process will be described with reference to FIG. 9. The CPU 21 reads out the pre-conversion PJL data constituting the first conversion rule, that is, the conversion rule with conversion rule number 1, from the conversion rule data 50 read out from the flash ROM 12 and expanded in the RAM 22 (S20). Here, the conversion rule data 50 will be described with reference to FIG. 6. The conversion rule data 50 is data for converting acquired PJL data that is not supported by the printing device 10 into converted PJL data or converted PDL data. As shown in the figure, the conversion rule data 50 is configured by associating conversion rule numbers 1 to 10 with pre-conversion PJL data, converted PJL data, converted PCL data, and converted PCLXL data. The converted PCL data and converted PCLXL data are converted PDL data, respectively.

[0021] The CPU 21 judges whether the PJL data acquired in S12 (FIG. 8) of the PJL data conversion process matches the pre-conversion PJL data read from the conversion rule with conversion rule number 1 in S20 (S21). If the CPU 21 judges that they match (S21: Yes), it judges whether the pre-conversion PJL data judged in S21 is associated with the post-conversion PJL data in the conversion rule judged in S21 (S22). That is, it judges whether the post-conversion PJL data capable of converting the pre-conversion PJL data exists in the conversion rule. If the CPU 21 judges that the post-conversion PJL data is associated with the pre-conversion PJL data judged in S21 (S22: Yes), it converts the acquired PJL data into the post-conversion PJL data that is associated with the pre-conversion PJL data that matches the acquired PJL data in the conversion rule in accordance with the conversion rule judged in S21 (S23). For example, the acquired PJL data D2 "@PJL SET MEDIASIZE=LETTER" constituting the PJL section 30a of the print job 30 shown in Fig. 2 is converted into the converted PJL data D2a "@PJL SET PAPER=LETTER" as shown in Fig. 3. In this way, the CPU 21 acquires a print job via an external interface such as the communication IF 17 and the USB IF 18, and in the first case where the acquired PJL data included in the acquired print job matches the pre-conversion PJL data registered in the conversion rule data 50 in the flash ROM 12, and in the second case where the pre-conversion PJL data matching the acquired PJL data is associated with the converted PJL data in the conversion rule with the conversion rule number 1, the CPU 21 executes a process of converting the acquired PJL data into the converted PJL data associated with the pre-conversion PJL data matching the acquired PJL data in the conversion rule with the conversion rule number 1 (S20 to S23).Therefore, even if the print job acquired from the information processing device 40 contains acquired PJL data that is not supported by the printing device 10, the acquired PJL data can be converted into converted PJL data that is supported by the printing device 10, so the administrator of the printing system does not need to install a driver that supports the new PJL data in the information processing device 40, and therefore the burden of reconstructing the printing system is not large.

[0022] Next, CPU 21 analyzes the converted PJL data converted in S23, generates data for executing the RIP process S6 (FIG. 7) according to the analysis result (S27), and ends the PJL data analysis process. If CPU 21 determines that the converted PJL data is not associated with the pre-conversion PJL data determined in S21 in the conversion rule determined in S21 (S22: No), CPU 21 stores the pre-conversion PJL data of the conversion rule determined in S21 in RAM 22 (FIG. 1) as pending conversion PJL data (S24), and ends the PJL data analysis process. In this way, when the CPU 21 judges that the converted PJL data is not associated with the pre-conversion PJL data judged in S21 in the conversion rule judged in S21 (S22: No), it executes a reservation process to reserve the conversion of the pre-conversion PJL data to the converted PDL data until the type of PDL data is judged in S33 (FIG. 10) of the PJL->PDL conversion process executed after the PJL data analysis process. In other words, if there is a conversion rule having pre-conversion PJL data that matches the acquired PJL data, but the converted PJL data is not associated with the pre-conversion PJL data, the conversion is reserved and temporarily stored in the RAM 22 for the judgment process (S32 in FIG. 10) in the PJL->PDL conversion process executed after the PJL data conversion process. In this way, by suspending the conversion until the type of PDL data is judged, it is possible to prevent erroneous conversion to a different type of converted PDL data. Furthermore, since the PDL section follows the PJL section, by determining the type of PDL data before analyzing the PDL section, the converted PDL data can be incorporated into the PDL section in the converted data embedding process (S35 in Figure 10) described below, in the correct position according to the type of PDL data.

[0023] Furthermore, if the CPU 21 determines that the PJL data acquired in S12 (FIG. 8) of the PJL data conversion process does not match the pre-conversion PJL data read from the conversion rule with conversion rule number 1 in S20 (S21: No), it determines whether the conversion rule having the pre-conversion PJL data read in S20 is the last conversion rule of the conversion rule data 50, that is, whether the end of the conversion rules has been reached (S26), and if it determines that the end of the conversion rules has not been reached (S26: No), it reads the pre-conversion PJL data constituting the next conversion rule from the conversion rule data 50 in the RAM 22 (S25). Next, the CPU 21 executes S21 to S23 on the read pre-conversion PJL data. Furthermore, if the CPU 21 determines that it has reached the end of the conversion rule (S26: Yes), it executes an analysis process for the acquired PJL data that was the subject of the determination in S21, that is, the PJL data acquired in S12 (FIG. 8) of the PJL data conversion process (S27), and ends the PJL data analysis process. S23 executed by the CPU 21 is an example of the second conversion process of the present invention, and S24 is an example of the reservation process of the present invention.

[0024] Here, an example of converting acquired PJL data into converted PJL data will be described. The conversion rule with conversion rule number 1 is configured by associating pre-conversion PJL data "@PJL SET MEDIASIZE=LETTER" with post-conversion PJL data "@PJL SET PAPER=LETTER". Both the pre-conversion PJL data "@PJL SET MEDIASIZE=LETTER" and the post-conversion PJL data "@PJL SET PAPER=LETTER" indicate the instruction "specify the paper size as letter size". When the acquired PJL data included in the print job 30 (FIG. 2) acquired from the information processing device 40 matches the pre-conversion PJL data "@PJL SET MEDIASIZE=LETTER", the CPU 21 (FIG. 1) converts the acquired PJL data into post-conversion PJL data "@PJL SET PAPER=LETTER" that is associated with the pre-conversion PJL data "@PJL SET MEDIASIZE=LETTER" that matches the acquired PJL data in the conversion rule with conversion rule number 1. This enables the CPU 21 to execute a process for "specifying the paper size as letter size", which is the instruction content indicated by the acquired PJL data, that is, the pre-conversion PJL data "@PJL SET MEDIASIZE=LETTER". FIG. 2 shows the print job 30 before conversion by the conversion rule data 50, and FIG. 3 shows the print job after conversion. The acquired PJL data D2 "@PJL SET PAPER=LETTER" included in the PJL section 30a of the print job 30 shown in FIG. 2 has been converted to the converted PJL data D2a "@PJL SET PAPER=LETTER" as shown in FIG. 3. The acquired PJL data D2 before conversion has been deleted from the PJL section 31a. The conversion rule with conversion rule number 8 is a combination of the pre-conversion PJL data "@PJL SET ORGOUTBIN=TRAY5" and the converted PJL data " <esc>&l5G" and the converted PCLXL data "MediaDestination_UB(5=eExternalBin2". <esc>&l5G" both indicate an instruction to "discharge printed paper to tray 5," and the converted PCLXL data "MediaDestination_UB(5=eExternalBin2" indicates an instruction to "discharge printed paper to external tray 2." If the acquired PJL data included in print job 30 acquired from information processing device 40 matches pre-conversion PJL data "@PJL SET ORGOUTBIN=TRAY5" and the type of page description language of the PDL part constituting print job 30 is PCL, CPU 21 converts the acquired PJL data into the converted PCL data "@PJL SET ORGOUTBIN=TRAY5" that matches the acquired PJL data in conversion rule number 8. <esc>&l5G". This enables the CPU 21 to execute the instruction indicated by the acquired PJL data, i.e., the pre-conversion PJL data "@PJL SET ORGOUTBIN=TRAY5", which is to "discharge printed paper to tray 5". The acquired PJL data D3 "@PJL SET ORGOUTBIN=TRAY5" included in the PJL section 30a of the print job 30 shown in FIG. 2 is converted into the converted PCL data D3a " <esc>&l5G". Note that the acquired PJL data D3 before conversion has been deleted from the PJL section 31a.

[0025] Furthermore, if the acquired PJL data included in the print job 30 acquired from the information processing device 40 matches the pre-conversion PJL data "@PJL SET ORGOUTBIN=TRAY5" and the type of page description language of the PDL part constituting the print job 30 is PCLXL, the CPU 21 converts the acquired PJL data to post-conversion PCLXL data "MediaDestination_UB(5=eExternalBin2" which is associated with the pre-conversion PJL data "@PJL SET ORGOUTBIN=TRAY5" which matches the acquired PJL data in the conversion rule of conversion rule number 8. As a result, the CPU 21 converts the acquired PJL data, i.e., the pre-conversion PJL data "@PJL SET The instruction content indicated by "ORGOUTBIN=TRAY5" "discharge printed paper to tray 5" can be converted to the instruction content indicated by the converted PCLXL data "MediaDestination_UB(5=eExternalBin2" "discharge printed paper to external tray 2" and executed. FIG. 4 shows print job 32 before conversion using conversion rule data 50, and FIG. 5 shows print job 33 after conversion. The acquired PJL data D3 "@PJL SET As shown in FIG. 5, "ORGOUTBIN=TRAY5" has been converted into converted PCLXL data "MediaDestination_UB(5=eExternalBin2". Note that the acquired PJL data D3 before conversion has been deleted from PJL section 33a. The pre-conversion PJL data is an example of non-target PJL data of the present invention. The post-conversion PJL data is an example of target PJL data of the present invention, and the post-conversion PCL data and post-conversion PCLXL data are examples of target PDL data of the present invention. PJL section 30a (FIG. 2), PJL section 31a (FIG. 3), PJL section 32a (FIG. 4) and PJL section 33a (FIG. 5) are each examples of PJL sections of the present invention. PDL section 30b (FIG. 2), PDL section 31b (FIG. 3), PDL section 32b (FIG. 4) and PDL section 33b (FIG. 5) are each examples of PDL sections of the present invention.

[0026] Next, the PJL to PDL conversion process executed by the CPU 21 in S18 (FIG. 8) of the PJL data conversion process will be described with reference to FIG. 10. The CPU 21 reads out the top conversion pending PJL data from among the conversion pending PJL data temporarily stored in the RAM 22 in S23 (FIG. 9) of the PJL data analysis process (S30), refers to the top conversion rule of the conversion rule data 50 (S31), and judges whether or not the conversion pending PJL data read out from the RAM 22 in S30 matches the pre-conversion PJL data of the conversion rule referred to in S31 (S32). If the CPU 21 judges that they match (S32: Yes), it judges whether or not the type of post-conversion PDL data associated with the conversion rule referred to in the judgment of S32 matches the type of PDL data determined in S16 (FIG. 8) of the PJL data conversion process for the pre-conversion PJL data that was the subject of the judgment of S32 (S33). If the CPU 21 judges that they match (S33: Yes), it converts the pending conversion PJL data for which the judgment in S32 was positive into the converted PDL data for which the judgment in S33 was positive (S34). For example, the acquired PJL data D3 "@PJL SET ORGOUTBIN=TRAY5" shown in FIG. 2 is converted into the converted PDL data D3a " <esc>&l15G". Furthermore, CPU 21 stores the converted PDL data converted in S34 in RAM 22 for use in a converted PDL data incorporation process described later (S34). Next, CPU 21 executes a converted PDL data incorporation process (FIG. 11) described later (S35). Next, CPU 21 determines whether the conversion pending PJL data read from RAM 22 in S30 is the conversion pending PJL data at the end of the conversion pending PJL data stored in RAM 22, that is, whether the end of the conversion pending PJL data has been reached (S36), and if it is determined that the end has not been reached (S36: No), it reads the next conversion pending PJL data from RAM 22 (S37), and executes S31 to S36 to convert the conversion pending PJL data to converted PDL data (S34) and execute the converted PDL data incorporation process (S35). Furthermore, if the CPU 21 judges in S32 that the pending conversion PJL data read from the RAM 22 does not match the pre-conversion PJL data of the conversion rule referenced in S31 (S32: No), it judges whether the conversion rule referenced in S31 is the terminal conversion rule of the conversion rule data 50 (S37), and if it judges in S32 that it is not the terminal conversion rule (S37: No), it refers to the next conversion rule (S38) and executes S32.

[0027] That is, the CPU 21 refers to all conversion rules registered in the conversion rule data 50 until it judges that the conversion pending PJL data read from the RAM 22 matches the pre-conversion PJL data of the conversion rule referred to in S31 (S32: Yes). If the CPU 21 judges that the conversion rule is at its end (S33: No), it judges whether the conversion rule is at its end (S37). If the CPU 21 judges that the conversion rule is at its end (S37: Yes), it judges whether the conversion pending PJL data has been reached (S36), and if the CPU 21 judges that the conversion pending PJL data has not been reached (S36: No), it reads the next conversion pending PJL data from the RAM 22 (S36). If the CPU 21 judges that the conversion pending PJL data has been reached (S36: Yes), it ends the PJL to PDL conversion process. In other words, the CPU 21 refers to all the conversion rules for each conversion pending PJL data stored in RAM 22, and if it determines that the conversion pending PJL data read from RAM 22 matches the pre-conversion PJL data of the conversion rule referenced in S31 (S32: Yes) and that the type of converted PDL data associated with the conversion rule referenced in the determination of S32 matches the type of PDL data determined in S16 (Figure 8) of the PJL data conversion process (S33: Yes), it converts the conversion pending PJL data to converted PDL data (S34) and executes a converted PDL data embedding process (S35). As described above, the CPU 21 executes an acquisition process (S1 in FIG. 7) to acquire a print job via an external interface (FIG. 1) such as the communication IF 17 and the USB IF 18, and if the acquired PJL data included in the print job acquired by the acquisition process matches the pre-conversion PJL data registered in the conversion rule data 50 (FIG. 6) in the flash ROM 12 (FIG. 1), the CPU 21 executes a conversion process (S34) to convert the acquired PJL data into post-conversion PDL data that is associated with the pre-conversion PJL data that matches the acquired PJL data in the conversion rule data 50.Then, CPU 21 executes print control (S7 in FIG. 7) using the PDL data converted by the conversion process, which is the acquired PJL data included in the print job acquired by the acquisition process, and does not execute processing according to the PJL data itself that is the subject of the positive determination of a match in the determination of S32. The PJL → PDL conversion process executed by CPU 21 is an example of the first conversion process of the present invention.

[0028] Next, the converted PDL data incorporation process executed by the CPU 21 in S35 (FIG. 10) of the PJL to PDL conversion process will be described with reference to FIG. 11. When the PDL section is made up of PCL data, the PCL standard stipulates that newly added PCL data should be incorporated at the beginning of the PDL section, so the converted PCL data is incorporated at the beginning of the PDL section 31b, as shown in FIG. 3. Also, under the PCL standard, when the PDL section is made up of PCL data, the instructions of each piece of PCL data arranged on the first page are carried over to the second and subsequent pages. For example, if converted PCL data D3a " <esc>When "&l15G" is incorporated, the instruction indicated by the converted PCL data D3a, "discharge the printed paper to tray 5", is carried over to the second page and onwards. The CPU 21 determines whether the type of PDL data determined in S16 of the PJL data conversion process is PCL or not (S40), and if it is determined that it is PCL (S40: Yes), it incorporates the converted PDL data stored in the RAM 22 in S34 (FIG. 10) of the PJL->PDL conversion process at the beginning of the PDL section (S41). In other words, when the type of converted PDL data is PCL, by incorporating the converted PDL data at the beginning of the PDL section, it is possible to carry over the instruction indicated by the incorporated converted PDL data to the next page and onwards. For example, as shown in FIG. 3, when the converted PDL data D3a " <esc>&l15G" is incorporated at the beginning of the PDL section 31b. Next, the CPU 21 executes S36 (FIG. 10) of the PJL → PDL conversion process, and if it determines that the end of the conversion pending PJL data has not been reached (S36: No), it executes S37, converts the conversion pending PJL data to converted PDL data, and executes the converted PDL data incorporation process (S35). In other words, the CPU 21 converts the conversion pending PJL data to converted PDL data and incorporates the converted converted PDL data into the PDL section for each conversion pending PJL data stored in the RAM 22.

[0029] In the PDL standard, when multiple PDL data are arranged in the PDL section, the PDL data arranged later in the analysis order is given priority. For example, if PDL data indicating the instruction "discharge printed paper to tray 5" is arranged in the PDL section, and PDL data indicating the instruction "discharge printed paper to tray 1" is arranged after that, the instruction "discharge printed paper to tray 5" is not executed, but the instruction "discharge printed paper to tray 1" is executed, because the later PDL data has priority. Since this instruction is inherited from the next page onwards, the next and subsequent pages of paper are also discharged to tray 1. If the CPU 21 determines that the type of PDL data determined in S16 (FIG. 8) of the PJL data conversion process is not PCL, that is, PCLXL (S40: No), it sets the incorporation position of the converted PDL data, that is, the converted PCLXL data, to the first page of the PDL section (S42). The embedding position of the converted PCLXL data is defined by the PCLXL standard, and is set to a specified position in a PCLXL data group having the same attribute as that of the converted PCLXL data (S42). For example, in the example shown in Fig. 5, a PCLXL data group having the same attribute, PCLXL data "Orientation_UB (0 = ePortraitOrientation)" to PCLXL data "SimplexPageMode_UB (0 = eSimplexFrontSide)", is arranged in the PCLXL data "BeginPage[3]" constituting the PDL section 33b. In the example shown in the figure, the next line of the PCLXL data "SimplexPageMode_UB (0 = eSimplexFrontSide)" is set to the specified position where the converted PCLXL data D3b is embedded.

[0030] Next, the CPU 21 judges whether or not PDL data corresponding to the same setting item exists in the embedding position of the converted PCLXL data set in S42 (S43), and if it is judged that no PDL data exists (S43: No), the converted PDL data is embedded in the embedding position set in S42 (S44). For example, as shown in FIG. 5, the converted PCLXL data D3b "MediaDestination_UB (5=eExternalBin2)" is embedded in the next line of the PCLXL data "SimplexPageMode_UB (0=eSimplexFrontSide)". "SimplexPageMode_UB" is PCLXL data corresponding to the setting item of print side, and "Orientation_UB" is PCLXL data corresponding to the setting item of print orientation. Next, the CPU 21 judges whether or not it is the last page (S45), and if it is judged that it is not the last page (S45: No), the embedding position of the converted PCLXL data is set to the next page of the PDL part (S46). That is, if the type of the converted PDL data is PCLXL, the converted PCLXL data must be incorporated into each page of the PDL section, so the incorporating position of the converted PCLXL data is set to the next page of the PDL section (S46). Next, CPU 21 executes S43 and S44, and if it determines that it is the end page (S45: Yes), it executes S36 (FIG. 10) of the PJL to PDL conversion process, and if it determines that the end of the conversion pending PJL data has not been reached (S36: No), it executes S37, converts the conversion pending PJL data to converted PDL data (S34), and executes the converted PDL data incorporating process (S35).That is, the print job is configured to include a PDL section for each page for a plurality of pages, and the position where the converted PCLXL data converted from the PJL data by the conversion process of S34 (FIG. 10) is incorporated into the PDL section is specified by the standard of the PCLXL data, and if there is no PCLXL data with the same setting items as the target PCLXL data at the specified embedding position (S43: No), the CPU 21 embeds the converted PCLXL data converted from the PJL data by the conversion process of S34 into the specified embedding position of the PDL section when analyzing the PDL section for each page, and if there is PCLXL data with the same setting items as the converted PCLXL data at the embedding position (S43: Yes), the CPU 21 does not embed the converted PCLXL data converted from the PJL data by the conversion process of S34 into the specified embedding position of the PDL section when analyzing the PDL section for each page. In this way, the CPU 21 can embed the converted PCLXL data into the specified position of the PDL section in accordance with the standard of the PCLXL data. Furthermore, by performing RIP processing in S6 on PCLXL data supported by the printing device 10, printing can be performed according to instructions of the print job. The embedded processing executed by the CPU 21 is an example of the embedded processing of the present invention.

[0031] Then, by executing the above-mentioned embedding process, a print job in which the converted PDL data is embedded in the PDL section is completed, and the CPU 21 executes RIP processing on the print job (S6 in FIG. 7), and executes print control according to the data generated by the RIP processing (S7). When the CPU 21 executes the process of embedding the converted PDL data in the PDL section by the embedding process, the CPU 21 deletes from the PJL section the acquired PJL data that matches the pre-conversion PJL data that was the subject of the judgment in S32 (FIG. 10) of the PJL→PDL conversion process, and therefore does not execute a process according to the acquired PJL data itself. Note that, when the CPU 21 determines in S32 (FIG. 10) of the PJL→PDL conversion process, it is not essential to delete from the PJL section the acquired PJL data that matches the pre-conversion PJL data that was the subject of the judgment in S32 (FIG. 10). This is because PDL data takes precedence over PJL data according to the PDL standard. When converted PJL data indicating the same instruction content as the converted PDL data exists, if the converted PDL data is arranged in a PDL section that exists after the PJL section, the instruction content indicated by the converted PDL data arranged in the PDL section is applied with priority. For example, when converted PJL data indicating the instruction content "discharge printed paper to tray 5" exists in the PJL section, if converted PDL data indicating the instruction content "discharge printed paper to tray 1" is arranged in the PDL section, the instruction content "discharge printed paper to tray 5" indicated by the converted PJL data is not executed, and the instruction content "discharge printed paper to tray 1" indicated by the converted PDL data is executed. The above-mentioned embedding process completes the print job in which the converted PDL data is incorporated in the PDL section. Then, the CPU 21 can execute the RIP process (S6) and print control (S7) according to the completed print job.That is, according to the printing device 10 of the present embodiment, even if the print job acquired from the information processing device 40 via the communication IF 17 or the USB IF 18 includes PJL data that is not supported by the printing device 10, the PJL data can be converted into PJL data or PDL data that is supported by the printing device 10, so that printing can be performed according to the print job acquired from the information processing device 40. The CPU 21 RIPs (S5 in FIG. 7) the print job having the converted PJL data converted in S23 of the above-mentioned PJL data analysis process, and executes print control according to the RIP-processed data (S7). In addition, the CPU 21 does not execute processing according to the PJL data itself before conversion. The converted PCL data or the converted PCLXL data is an example of converted PDL data.

[0032] As described above, the printing device 10 includes the communication IF 17 and the USB IF 18, the flash ROM 12, and the CPU 21. The CPU 21 is a printing device that acquires a print job (30, 32) having PJL data and PDL data via the communication IF 17 or the USB IF 18, and executes print control (S7) in accordance with the acquired print job. The flash ROM 12 stores conversion rule data 50 in which pre-conversion PJL data and post-conversion PDL data are associated with each other. The CPU 21 executes an acquisition process (S1) for acquiring a print job via the communication IF 17 or the USB IF 18, and an acquired PDL data included in the print job acquired by the acquisition process. In a first case (S32: Yes) in which the PJL data matches pre-conversion PJL data registered in conversion rule data 50 in flash ROM 12, a first conversion process (S34) is executed to convert the PJL data into converted PDL data that is associated with the pre-conversion PJL data that matches the PJL data in conversion rule data 50, and print control (S7) is executed using the converted PDL data that is included in the print job acquired by the acquisition process and that is converted from the pre-conversion PJL data by the first conversion process, and processing according to the acquired PJL data that matched in the first case is not executed. The converted PCL data and the converted PCLXL data are examples of converted PDL data.

[0033] As described above, according to the printing device 10, printing system (10, 40), and program 24 of the present embodiment, even if the print job acquired from the information processing device 40 contains acquired PJL data that is not supported by the updated printing device when the printing device is updated, the acquired PJL data is PDL data supported by the updated printing device, and the instruction contents indicated by the acquired PJL data are converted into converted PDL data suitable for the updated printing device, and printing control can be executed using the converted PDL data. Therefore, according to the printing device 10, printing system (10, 40), and program 24 of the above-mentioned embodiment, it is possible to provide a printing device, printing system, and program that do not increase the burden of reconstructing the printing system even when the printing device is updated.

[0034] Other Embodiments In the above-described embodiment, processing for a print job in which the PDL section is composed of PCL data or PCLXL data was described, but the technology disclosed in this specification can also be applied to print jobs in which the PDL section is composed of PDL data other than PCL data or PCLXL data, for example, PS data. [Explanation of symbols]

[0035] 10 printing device, 12 flash ROM, 17 communications IF, 18 USB IF, 20 control unit, 21 CPU, 22 RAM, 24 program, 30 to 33 print job, 30a, 31a, 32a, 33a PJL unit, 30b, 31b, 32b, 33b PDL unit, 40 information processing device, 50 conversion rule data, D2, D3 acquired PJL data, D2a converted PJL data, D3a, D3b converted PDL data.< / esc> < / esc> < / esc> < / esc> < / esc> < / esc> < / esc>

Claims

1. The device includes an external interface, a non-volatile memory, and a computer, the computer is a printing device that acquires a print job having PJL data and PDL data via the external interface and executes a print process in accordance with the acquired print job, The non-volatile memory includes: a conversion rule is stored in which non-target PDL data that is not supported by the printing device is associated with target PDL data that is supported by the printing device; The computer includes: an acquisition process for acquiring the print job via the external interface; a first conversion process for converting the PJL data included in the print job acquired by the acquisition process into the target PDL data associated with the non-target PJL data that matches the PJL data in the conversion rule in the non-volatile memory in a first case where the PJL data matches the non-target PJL data registered in the conversion rule in the non-volatile memory; executing the printing process using target PDL data obtained by converting the non-target PJL data into target PDL data included in the print job obtained by the obtaining process; A printing device characterized in that in the first case, processing according to the PJL data itself that is the subject of the match is not executed.

2. The conversion rules include: Furthermore, the non-target PJL data is associated with target PJL data that is supported by the printing device, The computer includes: In the first case, and in a second case where the target PJL data is associated with non-target PJL data matching the PJL data in the conversion rule, a second conversion process is executed to convert the PJL data into target PJL data that is associated with the non-target PJL data matching the PJL data in the conversion rule; using target PJL data, which is included in the print job acquired by the acquisition process, and which is converted from the non-target PJL data by the second conversion process, in the print process; 2. The printing apparatus according to claim 1, wherein in the second case, processing is not executed according to the PJL data itself that is the subject of the match.

3. The print job is A PDL section made up of at least one PDL data is arranged after a PJL section made up of at least one PJL data, The computer includes: a type determination process for analyzing the PJL data constituting the PJL portion of the print job acquired by the acquisition process in the order of arrangement of the PJL data, and determining the type of the target PDL data supported by the printing device based on the analysis result of the PJL data indicating the type of the PDL data; a generation process for generating data for printing based on the type determined by the type determination process and the PDL data constituting the PDL portion; executing the printing process according to the data generated by the generation process; The computer includes: In the first case, when the target PJL data is not associated with the non-target PJL data that matches the target PJL data in the conversion rule, a reservation process is executed to reserve the conversion of the PJL data to the target PDL data by the first conversion process until the type is determined by the type determination process; In the first conversion process, After determining the type of the target PDL data by the type determination process, if the PJL data reserved by the reservation process matches the non-target PJL data registered in the conversion rule in the non-volatile memory and the type of the target PDL data associated with the non-target PJL data matches the type determined by the type determination process, convert the PJL data that is the matched target in this case into the target PDL data associated with the non-target PJL data that matches the PJL data in the conversion rule for this case, execute an embedding process for embedding the target PDL data converted from the PJL data by the first conversion process into the PDL section; executing the printing process using the PDL section including the PDL data incorporated into the PDL section by the incorporating process; 3. The printing apparatus according to claim 2, wherein processing is not performed according to the PJL data itself that is the subject of the match in the first conversion processing.

4. The print job is A PDL section configured by at least one PDL data is arranged after a PJL section configured by at least one PDL data, and the computer a type determination process for determining a type of the target PDL data supported by the printing device by analyzing at least one PDL data constituting the PDL portion of the print job acquired by the acquisition process; a generation process for generating data for printing based on the type determined by the type determination process and the PDL data constituting the PDL portion; executing the printing process according to the data generated by the generation process; The computer includes: In the first case, when the target PJL data is not associated with the non-target PJL data that matches the target PJL data in the conversion rule, a reservation process is executed to reserve the conversion of the PJL data to the target PDL data by the first conversion process until the type is determined by the type determination process; In the first conversion process, After determining the type of the target PDL data by the type determination process, if the PJL data reserved by the reservation process matches the non-target PJL data registered in the conversion rule in the non-volatile memory and the type of the target PDL data associated with the non-target PJL data matches the type determined by the type determination process, convert the PJL data that is the matched target in this case into the target PDL data associated with the non-target PJL data that matches the PJL data in the conversion rule for this case, execute an embedding process for embedding the target PDL data converted from the PJL data by the first conversion process into the PDL section; executing the printing process using the PDL section including the PDL data incorporated into the PDL section by the incorporating process; 3. The printing apparatus according to claim 2, wherein processing is not performed according to the PJL data itself that is the subject of the match in the first conversion processing.

5. The embedding process includes:

5. The printing apparatus according to claim 3, wherein the target PDL data converted by the first conversion process is incorporated at the beginning of the PDL portion.

6. The print job includes a PDL portion for each page for a plurality of pages, an embedding position for embedding the target PDL data converted from the PJL data by the first conversion process into the PDL section is specified by a standard of the PDL data; The embedding process includes:

6. A printing device according to claim 3, wherein, if PDL data having the same setting items as the target PDL data is not present at the embedding position, the target PDL data converted from PJL data by the first conversion process is embedded in the embedding position of the PDL part when the PDL part is analyzed for each page, and, if PDL data having the same setting items as the target PDL data is present at the embedding position, the target PDL data converted from PJL data by the first conversion process is not embedded in the embedding position of the PDL part when the PDL part is analyzed for each page.

7. The computer includes: a conversion rule acquisition process for acquiring the conversion rule via the external interface; a storage process for storing the conversion rule acquired by the conversion rule acquisition process in the non-volatile memory; 7. The printing device according to claim 1, wherein after the conversion rule is stored in the non-volatile memory by the storage process, the first conversion process is executed using the stored conversion rule.

8. The present invention includes a printing device having an external interface, a non-volatile memory, and a computer, and an information processing device, the computer is a printing system that acquires a print job having PJL data and PDL data via the external interface and executes a print process in accordance with the acquired print job, The non-volatile memory includes: a conversion rule is stored in which non-target PDL data that is not supported by the printing device is associated with target PDL data that is supported by the printing device; The computer includes: An acquisition process for acquiring the print job; a conversion process for converting the PJL data included in the print job acquired by the acquisition process into the target PDL data associated with the non-target PJL data that matches the target PJL data in the conversion rule when the PJL data included in the print job acquired by the acquisition process matches the non-target PJL data registered in the conversion rule in the non-volatile memory; execute the print process using target PDL data obtained by converting the non-target PJL data into target PDL data, the target PDL data being included in the print job obtained by the acquisition process; A printing system characterized in that when the PJL data included in the print job acquired by the acquisition process matches the non-target PJL data registered in the conversion rule in the non-volatile memory, processing according to the matching target PJL data itself is not executed.

9. The device includes an external interface, a non-volatile memory, and a computer, a program executed by the computer of a printing device, the computer acquiring a print job having PJL data and PDL data via the external interface and executing a print process according to the acquired print job, The non-volatile memory includes: a conversion rule is stored in which non-target PDL data that is not supported by the printing device is associated with target PDL data that is supported by the printing device; The computer includes: An acquisition process for acquiring the print job; a conversion process for converting the PJL data included in the print job acquired by the acquisition process into the target PDL data associated with the non-target PJL data that matches the target PJL data in the conversion rule when the PJL data included in the print job acquired by the acquisition process matches the non-target PJL data registered in the conversion rule in the non-volatile memory; executing the printing process using target PDL data obtained by converting the non-target PJL data into target PDL data, the target PDL data being included in the print job obtained by the obtaining process; A program characterized in that, when the PJL data included in the print job acquired by the acquisition process matches the non-target PJL data registered in the conversion rule in the non-volatile memory, processing according to the matching target PJL data itself is not executed.

Images