JP2010128962A - Information processing apparatus, method of controlling the same, printing control system, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a mechanism for enabling even a printer with a small amount of memory to appropriately print archive data (XPS data) including resource files. <P>SOLUTION: In a host computer 100 communicatively connected with a printer 200, a CPU 101 acquires archive data including a file of print data (FP) describing information about a page to be printed by the printer 200 and resource files referred to from FP, divides the FP file, reflects divided FP files in the archive data, and includes information on the number of references from FP to the resource files in the archive data. The FP file is divided according to the information on the number of references. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information processing apparatus communicably connected to a printer and a control method thereof, a print control system including the information processing apparatus and the printer, and a computer for executing the control method of the information processing apparatus. Regarding the program.

  An information processing apparatus such as a personal computer (hereinafter referred to as “PC”) is a basic information that is commonly used by many application software such as input / output functions such as keyboard input and image output, and disk or memory management. Provide functionality. In order to provide such a function, an information processing apparatus has an operating system (hereinafter referred to as “OS”) that is software for managing the entire computer system. Examples of this OS include Windows (registered trademark) _XP, Windows_2000, Windows_Vista, etc., manufactured by Microsoft Corporation.

  There are various document file formats that allow a user to browse various documents using an information processing apparatus such as a PC. One of them is a document file format called XML_Paper_Specification (hereinafter referred to as “XPS”). There is. Here, in the above-mentioned Windows_Vista, XPS is used not only as a document file format but also as a print spool file format. Note that data according to the XPS format is referred to as “XPS data”, and a file whose data is in the XPS format is referred to as “XPS file”. XML (Extensible Markup Language) is one of markup languages for describing the meaning and structure of documents and data, and is called a structured document. Other structured documents include HTML and SGML.

  Here, when printing is performed in a system including an information processing device such as a PC and an output device such as a printer, when an application receives a print execution command from a user, an OS that is running the application, and Then, a printing command issuance process corresponding to the printing system provided by the OS is performed.

  For example, an application running on an OS such as Windows_XP or Windows_2000 described above issues a print command in accordance with a print system format called a GDI print path provided by the OS. Here, GDI is an abbreviation for Graphics_Device_Interface. On the other hand, in Windows_Vista described above, a printing system called XPS print path is newly provided in addition to the GDI print path described above.

Next, the format of XPS data will be described.
XPS data is data having a format in which a plurality of files are included in one file in the ZIP compression format. Examples of the file included here include an XML file, a JPEG file, a PNG file, a TIFF file, an HD_Photo file, and a font file. Here, XML is an abbreviation for Extensible_Markup_Language, JPEG is an abbreviation for Joint_Photographic_Experts_Group, PNG is an abbreviation for _, F is an abbreviation for _, and _ is an abbreviation for _, and _m is an abbreviation for _, and

  Here, in the XML file described above, various information for forming a document is described in the XML format. Each piece of information described is divided into a plurality of XML files. Here, in XPS, one document is divided into several bundles such that one document is composed of multiple or one document bundles, and one document is composed of multiple or one page bundles. Has been considered.

  JPEG, PNG, TIFF, and HD_Photo are formats for representing an image, respectively, and these files are hereinafter collectively referred to as “image files”. These image files and font files are also included in the XPS data as many as necessary for composing the document. Each file included in the XPS data is referred to as a “part”. That is, one XPS data includes a plurality of parts.

FIG. 23 is a schematic diagram showing an example of an image of the structure of XPS data.
Here, each part included in the XPS data can be referred to another part, and by repeating this reference, one part of the document information is formed due to the property that all parts are related. The Hereinafter, each part included in the XPS data shown in FIG. 23 will be described.

a) _rels /. rels:
The part that is the starting point of the document. It has a reference to b) FixedDocumentSequence which will be described later.

b) Fixed Document Sequence (FDS):
It is a part in which configuration information of one document is described. C) has a reference to FixedDocument, described below. One data can include a plurality of documents. That is, the FDS can have references to multiple FixedDocuments.

c) Fixed Document (FD):
This is a part for arranging and bundling a plurality of pages existing in one document in page order. That is, it is a part in which configuration information of one document is described, and has a reference to d) FixedPage described later. One document can have a plurality of pages. That is, the FD can have references to multiple FixedPages.

d) FixedPage (FP):
It is a part that describes the drawing contents of one page. You can have references to image files and font files as needed. For example, if there is an image drawing on the page, it will have a reference to the image file.

e) FixedPage. rels (FP.rels):
d) A part in which reference information to parts related to the FixedPage is described. The reference destination is, for example, an image file, a font file, a print ticket file to be described later in which print setting information is described, or the like. This FP. rels is one per FixedPage, or FP. rels itself does not exist.

f) Print ticket:
This is a file in which settings of printing conditions described according to a predefined XML schema format are described. Hereinafter, an XML schema format defined in advance for performing print settings is referred to as a “print schema”, and an XML file in which printing conditions are described according to the print schema is referred to as a “print ticket”.

  FIG. 24 is a schematic diagram showing an example of the logical structure of the reference relationship of each part included in the XPS data shown in FIG. FIG. 25 is a schematic diagram showing an example of a reference relationship based on the description of the XML file.

Next, details of the print ticket will be described.
FIG. 26 is a schematic diagram showing an example of a print ticket based on the description of the XML file.

  The route tag of the print ticket is <PrintTicket> shown in FIG. A <Feature> tag exists as a child element of the root tag. The <Feature> tag has “name” as an essential attribute. The value of “name” indicates the function of the printer to be printed. For example, there is a value for the page size designation function. As the value of “name”, a value defined in the print schema may be used, or a value uniquely defined by the vendor may be used. The XML namespace to which the print schema belongs is “http://schemas.microsoft.com/windows/2003/08/printing/printschemaframework” and “http://schemas.microsoft. 08 / printing / printschemewords ".

  In addition, the <Feature> tag usually has one <Option> tag as a child element. This <Option> tag indicates the setting of the function specified by the parent <Feature> tag, and has the attribute “name” as the <Feature> tag, and sets the function with this attribute value. . The attribute value at this time is a value defined in a print schema or a vendor-specific schema. For example, if the upper <Feature> tag is a page size designation function, a value such as “A4” is expected to be entered. Normally, there is only one <Option> tag as a child element of one <Feature> tag. Also, the <Option> tag has <ScoredProperty> as a child element. At this time, the <Option> tag may have a plurality of <ScoredProperty>.

  The <ScoredProperty> tag indicates a part of the setting of the function specified by the <Option> tag that is the parent element, has “name” as a required attribute, and specifies a part of the setting. The attribute value includes a value defined in a print schema or a vendor-specific schema. For example, if the upper <Option> tag is “A4”, values such as width and height are expected to be entered. This <ScoredProperty> tag has one <Value> tag as a child element.

  The <Value> tag contains a specific value of the content specified by the “name” attribute of the <ScoredProperty> tag. For example, if the “name” attribute value of the upper <ScoredProperty> tag is a width, a specific numerical value such as “247000” is entered.

  By the way, in Windows_Vista, it has been described that XPS can be used not only as a document file format but also as a format of a print spool file. In this case, when the above-described XPS print path is used, the OS usually provides The printing system that automatically generates a print spool file in the XPS file format. Here, it is possible for the user to create and spool arbitrary XPS data, and it is also possible to spool XPS data created by MXDW described later.

  When XPS data is used as print data, ZIP-compressed data is transmitted from an information processing device such as a PC to an output device such as a printer via a network. At this time, transmission data (XPS data) is generally not sent all at once, but is generally divided into several parts and sent to an output device. Then, the output device performs processing for analyzing the received XPS data in order to perform printing processing after performing processing for receiving XPS data. In general, the output device can perform reception processing and analysis processing of already received XPS data in parallel.

  By the way, as one of the functions of Windows_Vista, there is an application for generating an XPS file called Microsoft_XPS_Document_Writer (hereinafter referred to as “MXDW”). When an XPS file is generated by this MXDW, normally, a file data part having information of “_rels / .rels”, a file data part having information of “Fixed Document Sequence (FDS)”, and information of “Fixed Document (FD)” As shown in FIG. 27, the data of the file data part having “FixedPage (FP)” and the data of the file data part having “FixedPage (FP)” are respectively “FixedPage (FP)” → “FixedDocument (FD)” (2713, 2714) → “FixedDocumentSequence (FDS)” (2715) → “_rels / .rels” (2716). Hereinafter, this order is referred to as “data order”. FIG. 27 is a schematic diagram showing an example of the data order of the XPS file normally generated by MXDW.

  Here, when XPS data is used as print data, as described above, the XPS data is divided into several parts and transmitted to the output device. At this time, in the XPS data arranged in the above-mentioned data order, after the transmission is started, after all the file data parts having the information “FixedPage (FP)”, “FixedDocument (FD)”, and “FixedDocumentSequence (FDS)” are transmitted. , The file data portion having the information “_rels / .rels” is transmitted to the output device.

  Here, as described above, since “_rels / .rels” is a part that is a starting point of a document, the output device receives the XPS until the file data portion having the information “_rels / .rels” is received. Data analysis cannot be started. As a result, XPS data reception processing and XPS data analysis processing cannot be performed in parallel, and the overall print throughput is reduced. Even if there is a file data part having information “_rels / .rels” at the beginning of XPS data, the file data part having information “FixedDocumentSequence (FDS)” to be referred to next is the last. If the data order is in the tail or the like, the XPS data analysis process must be interrupted until the file data portion is received. In this case, the overall print throughput is reduced. Resulting in.

  By the way, there is a specification called interleaving that divides one part into a plurality of parts in XPS, and it is possible to create data in accordance with the interleaving specification by setting MXDW (for example, Non-Patent Document 1). Non-Patent Document 2). XPS data conforming to this specification is called “piece data”. That is, in XPS data, the meaningful minimum unit is “parts”, but the minimum unit as physical data is “pieces”.

  Converting normal XPS data into data conforming to the interleaving specification is called interleaving. FIG. 28 is a schematic diagram showing an example of part data when the XPS data shown in FIG. 25 is interleaved. In the interleaving shown in FIG. 28, each part is divided until a reference to the next part exists. FIG. 29 is a schematic diagram illustrating an example of an XPS data configuration when interleaved. FIG. 30 is a schematic diagram showing an example of the data order of the XPS file when interleaved.

  Here, the above-described print throughput is reduced by rearranging the parts divided as shown in FIG. 28 in the order of data such that the reference destination data is arranged immediately after each reference part as shown in FIG. The problem to be solved is possible. In FIG. 28 to FIG. 30, there are places where the relationship parts and the print ticket are omitted, but the drawings are only simplified and actually exist. For example, / Documents / 1 / Page / 1. The relationship part of fpage and the print ticket referenced from the relationship part exist between 3003 and 3004 in FIG.

  As shown in FIG. 30, the reason why the print throughput is reduced by rearranging the data in such a way that the reference destination data is arranged immediately after each reference unit can be solved by the output device. This is because the file data portion having the part information is received in order, so that the analysis processing of the file data portion can be performed immediately after receiving the file data portion.

  For example, in the example illustrated in FIG. 29, the output device receives a file data portion having information on the first part of “_rels / .rels” divided into two. Here, the output device needs to analyze the part first, but since it has already received the file data part having the information of the part, it can immediately start analyzing the part.

  Subsequently, the output device receives a file data portion having information on the first part of “Fixed Document Sequence (FDS)” divided into n pieces. Here, the output device needs to analyze the part next, but since the file data part having the information of the part has already been received, the analysis of the part can be started immediately.

  Subsequently, the output device receives the file data portion having the information of the first part of “Fixed Document (FD)” in which the configuration information of the first document divided into i pieces is described. Here, the output device needs to analyze the part next, but since the file data part having the information of the part has already been received, the analysis of the part can be started immediately.

  Subsequently, the output device receives a file data portion having information of “FixedPage (FP)” in which page information of the first page of the first document is described. Here, the output device needs to analyze the part next, but since the file data part having the information of the part has already been received, the analysis of the part can be started immediately. As a result, the first page of the first document can be printed.

  Subsequently, the output device receives a file data portion having information on the second part of “Fixed Document (FD)” in which the configuration information of the first document divided into i pieces is described. Here, the output device needs to analyze the part next, but since the file data part having the information of the part has already been received, the analysis of the part can be started immediately.

  Subsequently, the output device receives a file data portion having information of “FixedPage (FP)” in which page information of the second page of the first document is described. Here, the output device needs to analyze the part next, but since the file data part having the information of the part has already been received, the analysis of the part can be started immediately. As a result, the second page of the first document can be printed.

  Thereafter, similarly, the part can be analyzed immediately after receiving the file data portion, and the problem that the print throughput is reduced is solved.

  Next, the structure of the ZIP compressed data and the data search method will be described.

  The ZIP compressed data has a data portion called Local_File_Header or file data. Here, there is always a Local_File_Header immediately before the file data, and a set of the Local_File_Header and the file data constitutes information of one file of the decompressed data. In other words, one file of decompressed data can be decompressed by one set of Local_File_Header and file data. Hereinafter, a combination of Local_File_Header and file data is collectively referred to as a “file data portion”. If there are a plurality of files in the decompressed data, a plurality of file data portions are listed. FIG. 31 is a schematic diagram showing an example of the configuration of the ZIP compressed data.

  By the way, in the ZIP compression, it is possible to perform compression while maintaining the directory structure of the decompressed data, but even if a certain file exists in the upper hierarchy in the directory structure at the time of decompressed data, the file that constitutes the file at the time of compression The data part is not always in front of the data. In other words, there is no relationship between the hierarchical position on the directory structure at the time of decompression and the position of the file data portion at the time of compression.

Next, a method for acquiring part data from XPS when the XPS part name is known will be described.
In the internal structure of Local_File_Header shown in FIG. 31, the head data is binary data “PK34”, and then the data name and data size of the file data paired with the Local_File_Header are described at a predetermined position. Therefore, the binary data “PK34” is searched in order from the beginning, and after the search, the data name of the file data existing at the specified position is searched and acquired and determined. As a result, the part data must be the desired part data. For example, the binary data “PK34” of the Local_File_Header existing behind by the data size is searched again from the previously searched position. The above-described processing is repeated until the desired part data can be acquired.

XML Paper Specification (XPS Specification and Reference Guide) “17.1 Interleaving Optimization”, Internet <URL: http: // www. ecma-international. org / memento / TC46-availabledocs. Documents that can be downloaded from htm> “9.1.4 Interleaving” of Office Open XML Part 2 (Open Packaging Convections), Internet <URL: http: // www. ecma-international. org / publications / standards / Ecma-376. Documents that can be downloaded from htm>

  When FixedPage (FP) in the XPS file created by MXDW refers to a plurality of image files, as shown in FIG. 32, regardless of whether or not created using the interleave function, FP ( The image file is arranged in front of 3210).

  FIG. 33 is a schematic diagram showing an example of the FP (3210) shown in FIG. Specifically, FIG. 33 shows the contents of “/Documents/1/Page/1.fpage” shown in the FP (3210) of FIG. As shown in FIG. 33, the FP (3210) refers to “/Resource/Image/1.jpeg” twice, refers to “/Resource/Image/2.jpeg” once, and “/ Resource / Image”. /3.jpeg "is referenced twice and" /Resource/Image/4.jpeg "is referenced once. When such data is transmitted to the printer (output device), the above-described image file must be held until the FixedPage (FP) processing starts, and printing cannot be performed with a printer having a small storage area. there is a possibility.

  Therefore, the interleaving described in Non-Patent Document 1 and Non-Patent Document 2 is also applied to FixedPage (FP), and the FP shown in FIG. 33 is referred to an image file as shown in FIG. It is possible to divide the image file and arrange an image file to be referred to immediately, create an XPS file as shown in FIG. 35, and send it to the printer. By this method, the printer side performs processing at the same time as receiving the image file, and deletes the image file from the storage area upon completion of the processing, so that even a printer with a small storage area can be printed.

  However, with this method, there is a problem of a decrease in throughput (printing speed) due to an increase in the decompression processing of the ZIP compressed file due to an increase in the number of FP divisions. Further, since it is possible to refer to the same image file a plurality of times from the FP, if it is divided and transmitted for each reference location of the image file and deleted at the end of processing on the printer side, it is shown in FIG. When the image file needs to be transmitted a plurality of times as in 3507 and 3511 and the transmission efficiency of the network line is low, a decrease in throughput becomes a problem.

  Therefore, a method is conceivable in which an image file to be referred to is temporarily stored in the memory of the printer, and the same image file is read from the memory as needed by the printer.

  However, in this case, for example, when XPS data having a large number of image files is directly printed in a low-cost printer having a small memory capacity, the memory may be over. When the memory is over, the printer, for example, performs processing such as reducing the resolution of the image file to perform printing, so that there is a problem that an appropriate printed matter expected by the user cannot be obtained. It was.

  The present invention has been made in view of such problems, and provides a mechanism that can appropriately print archive data (XPS data) including a resource file even in a printer having a small memory capacity. The purpose is to do.

  An information processing apparatus according to the present invention is an information processing apparatus that is communicably connected to a printer. The information processing apparatus is referred to based on a page configuration data file in which document configuration information is described, and the page configuration data. An archive data acquisition unit for acquiring archive data including a file of print target data in which information of a page to be printed is described, and a resource file referred to based on the print target data, and a file of the print target data A division unit for dividing, an attribute information file for storing attributes used when printing the print target data, including a reference count for referring to the resource file by the print target data, and the division unit The print target data file, the page configuration data file, and the previous And a archive data generation means for generating an archive data including the resource file.

  A print control system according to the present invention is a print control system including an information processing apparatus and a printer, and the information processing apparatus includes a page configuration data file in which document configuration information is described, and the page configuration data. Data for obtaining archive data including a file of print target data referred to on the basis of information and a page of print target data described in the printer, and a resource file referred to based on the print target data An attribute for storing attributes used when printing the print target data, including an acquisition unit, a dividing unit for dividing the file of the print target data, and a reference count for referring to the resource file by the print target data; An information file and a file of the print target data divided by the dividing means. , Archive data generation means for generating archive data including the page configuration data file and the resource file, and the printer sequentially receives the archive data generated by the archive data generation means Receiving means; and deleting means for deleting the resource file included in the archive data received by the receiving means in accordance with the number of times the attribute information file included in the archive data is referenced.

  An information processing apparatus control method according to the present invention is a control method for an information processing apparatus that is communicably connected to a printer, and is based on a page configuration data file in which document configuration information is described and the page configuration data. An archive data acquisition step of acquiring archive data including a file of print target data referred to and describing information of a page to be printed in the printer, and a resource file referred to based on the print target data; A division step for dividing a file of print target data; an attribute information file for storing attributes used when printing the print target data, including a reference count for referring to the resource file with the print target data; The file to be printed divided by the dividing step, and the file It has a file over di configuration data and archive data generation step of generating an archive data including the resource file.

  A program of the present invention is a program for causing a computer to execute a control method of an information processing apparatus connected to a printer so as to be communicable, a file of page configuration data in which document configuration information is described, and the page configuration Archive data acquisition step of acquiring archive data including a file of print target data referred to based on data and describing information of a page to be printed in the printer, and a resource file referred to based on the print target data An attribute information file for storing attributes used when printing the print target data, including a dividing step of dividing the file of the print target data, and a reference count for referring to the resource file with the print target data And the mark divided by the dividing step And file of the target data, and the file of the page configuration data is intended to be executed by a computer and archive data generation step of generating an archive data including the resource file.

  According to the present invention, even a printer with a small memory capacity can appropriately print archive data including a resource file.

  The best mode (embodiment) for carrying out the present invention will be described below with reference to the drawings. In the following embodiment of the present invention, an example in which XPS data (XPS file) is applied as archive data (archive file) in which a plurality of data (files) are combined into one data (file) will be described. .

  FIG. 1 is a schematic diagram illustrating an example of a schematic configuration of a print control system 10 according to an embodiment of the present invention. The print control system 10 according to the embodiment of the present invention may be a single device or a system composed of a plurality of devices as long as the function of the present invention is executed. The present invention can also be applied to a system in which processing is performed by being connected via a network such as a WAN. In other words, the print control system 10 shown in FIG. 1 (in the following description, the print control system shown in FIG. 1 is referred to as “print control system 10-1”) is an example, and it depends on the application and purpose. Needless to say, there are various configuration examples.

  A print control system 10-1 shown in FIG. 1 includes a host computer (client computer) 100 corresponding to an information processing apparatus, a printer 200 corresponding to an output apparatus (printing apparatus), and a network that connects these apparatuses so that they can communicate with each other. 300.

  As shown in FIG. 1, the host computer 100 includes a CPU 101, a RAM 102, a ROM 103, a system bus 104, an input controller (hereinafter referred to as “input C”) 105, a video controller (hereinafter referred to as “VC”) 106, a memory. A controller (hereinafter referred to as “MC”) 107, a communication interface (hereinafter referred to as “communication I / F”) 108, a keyboard (hereinafter referred to as “KB”) 109, a CRT display (hereinafter referred to as “CRT”). ) 110 and an external memory 111.

  The CPU 101 controls each device connected to the system bus 104 based on a program or the like stored in the ROM 103 or the external memory 111, and controls the operation of the host computer 100 in an integrated manner.

  The RAM 102 functions as a main memory, work area, and the like for the CPU 101. The CPU 101 implements various operations by loading a program necessary for execution of processing into the RAM 102 and executing the program.

  The ROM 103 includes a BIOS (Basic Input / Output System) and an operating system program (hereinafter referred to as OS), which are control programs for the CPU 101, and various programs necessary for the CPU 101 to realize the functions of the host computer 100 according to the present embodiment. Etc. are stored. Note that these programs may be stored in the external memory 111. The OS used in this embodiment is assumed to be, for example, Windows_Vista (manufactured by Microsoft), but is not limited to this.

  The system bus 104 connects the CPU 101, the RAM 102, the ROM 103, the input C105, the VC 106, the MC 107, and the communication I / F 108 so that they can communicate with each other.

  The input C105 controls input from a pointing device (not shown) such as a KB 109 or a mouse.

  The VC 106 controls display on a display device such as the CRT 110. The display device may be a CRT or other display device such as a liquid crystal display.

  The MC 107 is connected via an adapter to a hard disk (HD), floppy disk (registered trademark FD) or PCMCIA card slot for storing a boot program, browser software, various applications, font data, user files, editing files, various data, and the like. To control access to an external memory 111 such as a compact flash (registered trademark) memory connected thereto.

  The communication I / F 108 controls communication with an external device (in the example illustrated in FIG. 1, the printer 200) via the network 300. For example, the communication I / F 108 can perform Internet communication using TCP / IP and data transmission / reception with the printer 200.

  Note that the CPU 101 enables display on the CRT 110 by executing outline font rasterization processing on a display information area in the RAM 102, for example. Further, the CPU 101 enables a user instruction with a mouse cursor (not shown) on the CRT 110.

  The printer 200 includes a CPU 201, a RAM 202, a ROM 203, a system bus 204, a communication interface (hereinafter referred to as “communication I / F”) 205, a printing unit interface (hereinafter referred to as “printing unit I / F”) 206, a memory controller. (Hereinafter, referred to as “MC”) 207, a printing unit 208, an operation unit 209, and an external memory 210.

  The CPU 201 controls each device connected to the system bus 204 based on a program or the like stored in the ROM 203 or the external memory 210, and comprehensively controls the operation of the printer 200. For example, the CPU 201 performs a process of outputting an image signal as output information to a printing unit (for example, a printer engine) 208 based on a program stored in the ROM 203 or the external memory 210.

  The RAM 202 functions as a main memory, work area, and the like for the CPU 201. The RAM 202 is also used as an output information expansion area, environment data storage area, NVRAM, and the like. The CPU 201 implements various operations by loading a program or the like necessary for executing the processing into the RAM 202 and executing the program. The RAM 202 is configured so that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown).

  The ROM 203 is provided with a font ROM 203a, a program ROM 203b, and a data ROM 203c. The font ROM 203a stores various font data used for generating the output information. In the program ROM 203b, various programs necessary for the CPU 201 to realize various functions of the printer 200 are stored. The data ROM 203c stores, for example, various data (including various information) necessary for the CPU 201 to perform various processes, and is used by the host computer 100 in the case of the printer 200 without the external memory 210. Information to be stored is also stored.

  The system bus 204 connects the CPU 201, RAM 202, ROM 203, communication I / F 205, printing unit I / F 206, MC 207, and operation unit 209 so that they can communicate with each other.

  The communication I / F 205 controls communication with an external device (in the example illustrated in FIG. 1, the host computer 100) via the network 300.

  A printing unit I / F 206 controls communication with the printing unit 208.

  The MC 207 controls access to the external memory 210 such as a hard disk (HD) or an IC card. The external memory 210 is connected as an option and stores font data, an emulation program, form data, and the like. Further, the number of external memories 210 is not limited to one. For example, a plurality of external memories 210 may be provided, and a plurality of external memories storing an optional font card, a program for interpreting a printer control language having a different language system, etc. in addition to the built-in font can be connected. It may be configured. Further, the external memory 210 may have, for example, an NVRAM (not shown) and store printer mode setting information from the operation unit 209.

  The operation unit 209 includes, for example, an operation panel, a switch for operating the operation panel, an LED display, and the like, and is operated by a user.

  In this embodiment, the print data supported by the printer 200 is assumed to be XPS data. However, the print data is not limited to this as long as the data has a similar file format.

FIG. 2 is a schematic diagram illustrating a modified example of the schematic configuration of the print control system 10 according to the embodiment of the present invention.
A print control system 10-2 shown in FIG. 2 includes a host computer 100 (specifically, 100-1 to 100-4) shown in FIG. 1 and a printer 200 (specifically, 200-1 to 200-1) shown in FIG. 200-2) and the network 300 shown in FIG. 1, in addition to the local interface 301 and the print server computer 400.

  In this case, the communication I / F 108 of the host computer 100 (100-1 to 100-4) has the function of a network interface card (NIC). The printer 200 (200-1 to 200-2) is connected to the print server computer 400 via a local interface 301 such as Centronics or USB, and is connected to the network 300 via the print server computer 400. Alternatively, a form directly connected to the network 300 may be used. Note that the communication I / F 205 of the printer 200 (specifically, 200-1) directly connected to the network 300 has a function of a network interface card (NIC).

  When a print job is transmitted from each host computer 100 to the printer 200 (specifically, 200-2) connected to the network 300 via the print server computer 400, first, each host computer 100 A print job is transmitted to the print server computer 400. Then, the print server computer 400 transmits the print job transmitted from each host computer 100 to the printer 200 via a print subsystem (not shown) of the print server computer 400. Accordingly, each host computer 100 can transmit a print job to the printer 200 via the print server computer 400.

  Further, when a print job is transmitted from each host computer 100 to the printer 200 (specifically, 200-1) directly connected to the network 300, each host computer 100 is directly connected to the network 300. A print job is transmitted to the existing printer 200.

  Next, the functional configuration of the print control function using the GDI print path described above by the host computer 100 will be described.

FIG. 3 is a schematic diagram illustrating an example of a functional configuration of a print control function using a GDI print path by the host computer 100 of the print control system 10 according to the embodiment of the present invention.
As shown in FIG. 3, the host computer 100 includes an application 131, a GDI 132, a user interface driver 133, a spooler 134, an EMF spool file 135, a print processor 136, a printer graphic as print control functions when using the GDI print path. A driver 137 and a language monitor 138 are configured.

  Here, the application 131, the GDI 132, the user interface driver 133, the spooler 134, the print processor 136, and the printer graphics driver 137 are composed of, for example, the CPU 101 and the program stored in the ROM 103 or the external memory 111 shown in FIG. The Further, the EMF spool file 135 is configured in, for example, the external memory 111 shown in FIG. The language monitor 138 includes, for example, the CPU 101 and the program stored in the ROM 103 or the external memory 111 and the communication I / F 108 shown in FIG.

  The application 131 sets print conditions for the printer 200 via the GDI 132. More specifically, for example, the application 131 sets the size of the paper used for printing, sets whether to print in reverse order, sets whether to perform bookbinding printing that performs printing in the form of bookbinding, and the like. Processing for setting various printing conditions is performed. Further, the application 131 issues a drawing command such as a document or a photographic image to the printer 200 via the GDI 132 or the like to instruct printing execution. Hereinafter, in the description of FIG. 3 and the like, the document / image data and the drawing command notified to the spooler 134 via the GDI 132 when the drawing command is issued are collectively referred to as “print data”.

  The GDI 132 performs processing related to the GDI print path based on an instruction from the application 131 or the like.

  The user interface driver 133 changes the printing conditions notified via the GDI 132 to contents suitable for the printer 200, and performs a process of determining the final printing conditions. Further, the user interface driver 133 performs processing for notifying the spooler 134 of the finally determined printing conditions via the GDI 132.

  The spooler 134 stores the print data and print conditions notified via the GDI 132 in the EMF spool file 135.

  The print processor 136 acquires the print data stored in the EMF spool file 135 via the spooler 134, and processes the print data in units of one page.

  The printer graphics driver 137 acquires print data processed by the print processor 136 via the GDI 132 and converts the print data into PDL data that can be printed out by the printer 200.

  The language monitor 138 performs bi-directional communication with the printer 200 to acquire information about the printer 200 and display it on the CRT 110. The language monitor 138 supplies the PDL data generated by the printer graphics driver 137 to the printer 200. Note that the language monitor 138 can employ different transfer methods depending on the memory capacity of the printer 200 and the configuration of the engine controller.

  Next, a series of operations in the print control function using the GDI print path will be described.

  First, in accordance with an operation instruction from the user, the application 131 issues a print condition setting and print execution instruction for an arbitrary document or photo image.

  When the GDI 132 receives a print execution instruction from the application 131, the GDI 132 notifies the user interface driver 133 of the setting contents of the print conditions in the printer 200 and the print start event.

  When the user interface driver 133 receives a notification of the setting contents of the printing conditions in the printer 200 from the GDI 132, the user interface driver 133 refers to the setting contents of the notified printing conditions and determines whether the setting contents can be printed out in the printer 200. Judging. Here, when the user interface driver 133 determines that the setting content of the printing condition notified from the GDI 132 is not the setting content that can be printed out by the printer 200, the setting content that can be printed out by the printer 200. In such a manner, the setting contents of the printing conditions are updated (including partly updated), and the printing conditions are determined.

  Subsequently, the application 131 issues a drawing command for document / image data via the GDI 132.

  When the spooler 134 receives the print data generated when the drawing command is issued by the application 131 and the print condition determined by the user interface driver 133, the spooler 134 displays the notified print data and print condition in the EMF spool file 135. To store.

  The print processor 136 acquires print condition setting contents and print data from the EMF spool file 135 via the spooler 134. Subsequently, the print processor 136 processes the setting contents of the printing conditions and the print data in units of one page via the GDI 132, and supplies them to the printer graphics driver 137. Here, when the GDI 132 supplies print data from the print processor 136 to the printer graphics driver 137, the GDI 132 performs a process of converting a drawing command included in the print data into a graphics drawing command.

  The printer graphics driver 137 interprets the printer 200 from print data supplied from the print processor 136 via the GDI 132 on the basis of the graphics rendering command generated by the GDI 132 and the print condition settings notified from the GDI 132. PDL data that can be generated is generated.

  The language monitor 138 supplies (sends) the PDL data supplied from the printer graphics driver 137 to the printer 200 via an interface used to transmit PDL data from the host computer 100 to the printer 200.

  The printer 200 (for example, the CPU 201) interprets the PDL data supplied from the language monitor 138, and performs a process of printing out print image data on paper.

  Next, the functional configuration of the print control function using the XPS print path described above by the host computer 100 will be described.

  FIG. 4 is a schematic diagram illustrating an example of a functional configuration of a print control function using an XPS print path by the host computer 100 of the print control system 10 according to the embodiment of the present invention. Here, in FIG. 4, the same reference numerals are given to configurations having the same functions as those shown in FIG.

  As shown in FIG. 4, the host computer 100 includes an application 131, a WPF (Windows_Presentation_Foundation) print support 141, a user interface driver 133, a spooler 134, an XPS spool file 142, as print control functions when using the XPS print path. A filter pipeline manager 143, a layout filter 144, a rendering filter 145, and a language monitor 138 are configured.

  Here, the application 131, the WPF print support 141, the user interface driver 133, the spooler 134, the filter pipeline manager 143, the layout filter 144, and the rendering filter 145 are stored in, for example, the CPU 101 and the ROM 103 or the external memory 111 shown in FIG. The program is composed of. Further, the XPS spool file 142 is configured in, for example, the external memory 111 shown in FIG. The language monitor 138 includes, for example, the CPU 101 and the program stored in the ROM 103 or the external memory 111 and the communication I / F 108 shown in FIG.

  The application 131 performs processing for creating XPS data via the WPF print support 141. The application 131 performs processing for setting a document such as a document or a photographic image, a printing condition, and a drawing command for XPS data. Hereinafter, in the description of FIG. 4 and the like, a document such as a document or a photographic image included in the XPS data and a drawing command are collectively referred to as “print data”. Further, the application 131 instructs printing execution via the WPF print support 141.

  The WPF print support 141 performs a process of configuring (creating) XPS data based on an instruction from the application 131. Further, the WPF print support 141 performs a process of taking out the setting contents of the printing conditions from the XPS data and notifying the user interface driver 133 of the settings. Further, the WPF print support 141 performs processing for setting the setting contents of the printing conditions determined by the user interface driver 133 in the XPS data. Further, the WPF print support 141 performs processing for notifying the spooler 134 of XPS data.

  The user interface driver 133 changes the printing conditions notified from the WPF printing support 141 to contents suitable for the printer 200, and performs a process of determining final printing conditions. Further, the user interface driver 133 performs processing for notifying the WPF print support 141 of the finally determined printing conditions.

  The spooler 134 stores the XPS data notified from the WPF print support 141 in the XPS spool file 142.

  The filter pipeline manager 143 first acquires the XPS data stored in the XPS spool file 142 via the spooler 134. The filter pipeline manager 143 performs processing for converting the acquired XPS data into PDL data that can be printed out by the printer 200 via the layout filter 144 and the rendering filter 145.

  The layout filter 144 performs processing for editing print data and page configuration in XPS data.

  The rendering filter 145 performs processing for converting print data in the XPS data edited by the layout filter 144 into PDL data that can be printed out by the printer 200. However, in the embodiment of the present invention, the XPS data is used as print data, the XPS data is transmitted to the printer 200, and the printer 200 generates image data to be drawn from the XPS data. Therefore, the rendering filter 145 is not used. That is, processing is performed without passing through the rendering filter 145 (XPS data direct printing). For this reason, the rendering filter 145 may be omitted.

  The language monitor 138 performs bi-directional communication with the printer 200 to acquire information about the printer 200 and display it on the CRT 110. The language monitor 138 supplies the XPS data notified from the filter pipeline manager 143 to the printer 200. Note that the language monitor 138 can employ different transfer methods depending on the memory capacity of the printer 200 and the configuration of the engine controller.

Here, the part data included in the XPS data described above will be described again.
As described above, the XPS data includes the following parts a) to f), which have the following references, respectively.

a) _rels /. rels:
The part that is the starting point of the document. It has a reference to b) FixedDocumentSequence which will be described later.

b) Fixed Document Sequence (FDS):
It is a part in which configuration information of one document is described. C) has a reference to FixedDocument, described below. One data can include a plurality of documents. That is, the FDS can have references to multiple FixedDocuments.

c) Fixed Document (FD):
This is a part for arranging and bundling a plurality of pages existing in one document in page order. That is, it is a part in which configuration information of one document is described, and has a reference to d) FixedPage described later. One document can have a plurality of pages. That is, the FD can have references to multiple FixedPages.

d) FixedPage (FP):
It is a part that describes the drawing contents of one page. You can have references to external resource files such as image files and font files as needed. For example, if there is an image drawing on the page, it will have a reference to the image file.

e) FixedPage. rels (FP.rels):
d) A part in which reference information to parts related to the FixedPage is described. The reference destination is, for example, an image file, a font file, a print ticket file to be described later in which print setting information is described, or the like.

f) Print ticket:
This is a file in which settings of printing conditions described according to a predefined XML schema format are described. Hereinafter, an XML schema format defined in advance for performing print settings is referred to as a “print schema”, and an XML file in which printing conditions are described according to the print schema is referred to as a “print ticket”. In other words, the print ticket is an attribute information file that stores attributes used for printing.

  Here, as described above, an example of the logical structure of the reference relationship of each part included in the XPS data is shown in FIG. 24, and the reference relationship based on the description of the XML file is described above. As shown in FIG. 25, an example is shown.

  Next, a series of operations in the print control function using the XPS print path will be described.

  First, the application 131 performs processing for reading an arbitrary document or a document such as a photographic image in accordance with an operation instruction from the user. Note that the arbitrary document described above includes XPS data created in advance.

  Subsequently, the application 131 creates XPS data in accordance with an operation instruction from the user, and sets a document such as a document or a photographic image, a printing condition, and a drawing command in the XPS data. Note that when the previously created XPS data is read, the application 131 does not create new XPS data, and the printing conditions and drawing commands included in the read XPS data are in accordance with an operation instruction from the user. Edit it.

  Subsequently, the application 131 issues a print execution instruction using the XPS data in accordance with an operation instruction from the user.

  When receiving the print execution instruction from the application 131, the WPF print support 141 takes out the print ticket in the XPS data and notifies the user interface driver 133 of the print ticket as the setting contents of the print condition.

  When the user interface driver 133 receives a notification of the setting contents of the printing conditions in the printer 200 from the WPF printing support 141, the user interface driver 133 refers to the setting contents of the notified printing conditions, and the setting contents can be printed out in the printer 200. Determine whether or not. Here, if the user interface driver 133 determines that the setting contents of the printing conditions notified from the WPF print support 141 are not the setting contents that can be printed out by the printer 200, the printing can be performed by the printer 200. The setting contents of the printing conditions are updated (including partly updated) so that the setting conditions become correct, and the printing conditions are determined. Subsequently, the user interface driver 133 updates the print ticket according to the determined printing conditions and notifies the WPF print support 141 of the print ticket.

  The WPF print support 141 sets the print ticket notified from the user interface driver 133 as XPS data, and notifies the spooler 134 of the XPS data.

  Upon receiving notification of XPS data from the WPF printing support 141, the spooler 134 stores the notified XPS data in the XPS spool file 142. It is also possible to notify arbitrary XPS data from the application 131 to the spooler 134 without using the WPF print support 141. That is, it is also possible to notify XPS data created by MXDW. Subsequently, the spooler 134 notifies the filter pipeline manager 143 of a print start event.

  When the filter pipeline manager 143 receives a print start event notification from the spooler 134, the filter pipeline manager 143 acquires the XPS data stored in the XPS spool file 142 via the spooler 134. Subsequently, the filter pipeline manager 143 notifies the layout filter 144 of the XPS data.

  The layout filter 144 acquires print data and a print ticket from the notified XPS data. Subsequently, the layout filter 144 edits the print data and the page configuration of the XPS data based on the print condition setting contents described in the print ticket. Note that the editing contents of the print data and the page configuration include bitmap composition (watermark), page composition (assignment), page order change (reverse order), and the like. Subsequently, the layout filter 144 notifies the filter pipeline manager 143 of the XPS data after finishing the editing of the print data and the page configuration.

  Subsequently, the filter pipeline manager 143 notifies the rendering filter 145 of the XPS data notified from the layout filter 144.

  The rendering filter 145 acquires print data and a print ticket from the XPS data notified from the filter pipeline manager 143. Subsequently, the rendering filter 145 generates PDL data that can be interpreted by the printer 200 from the print data based on the print condition settings described in the acquired print ticket, and sends the PDL data to the filter pipeline manager 143. Notice.

  Subsequently, the filter pipeline manager 143 supplies the PDL data notified from the rendering filter 145 to the language monitor 138.

  The language monitor 138 supplies (transmits) the PDL data supplied from the filter pipeline manager 143 to the printer 200 via an interface used for transmitting PDL data from the host computer 100 to the printer 200.

  The printer 200 (for example, the CPU 201) interprets the PDL data supplied from the language monitor 138, and performs a process of printing out print image data on paper. The processing in this embodiment is particularly effective when processing XPS data as PDL data in the printer 200 having a small storage area.

  Next, a processing procedure of print control processing using the XPS print path by the host computer 100 will be described.

  FIG. 5 is a flowchart illustrating an example of a processing procedure of print control processing using the XPS print path by the host computer 100 of the print control system 10 according to the embodiment of the present invention. In the following description, processing in the layout filter 144 will be mainly described.

  First, in step S101 in FIG. 5, when the filter pipeline manager 143 receives notification of a print start event from the spooler 134, the XPS created by the MXDW stored in the XPS spool file 142 via the spooler 134. Process to get data. The filter pipeline manager 143 notifies the layout filter 144 of the acquired XPS data.

  Subsequently, in step S102, the layout filter 144 analyzes the XPS data notified from the filter pipeline manager 143, and prints based on the setting contents of the printing conditions described in the print ticket in the XPS data. Data editing and XPS data page configuration editing are performed. Here, the layout filter 144 edits XPS data that can be processed by the printer 200 having a small storage area.

  Subsequently, in step S103, the layout filter 144 performs a process of notifying the filter pipeline manager 143 of XPS data after the editing (generation).

  Thereafter, the filter pipeline manager 143 performs processing for notifying the rendering filter 145 of the XPS data notified from the layout filter 144. The rendering filter 145 generates PDL data that can be interpreted by the printer 200 from the XPS data notified from the filter pipeline manager 143, and notifies the filter pipeline manager 143 of the PDL data. Here, since the printer 200 according to the present embodiment uses XPS data as print data, the rendering filter 145 does not particularly process the XPS data processed by the layout filter 144.

  Then, the filter pipeline manager 143 supplies the print data (XPS data) notified from the rendering filter 145 to the language monitor 138. The language monitor 138 then sends the print data (XPS data) supplied from the filter pipeline manager 143 to the printer 200 via the interface used to transmit PDL data from the host computer 100 to the printer 200. Send (sending step). When transmitting print data (XPS data) to the printer 200, the XPS data is transmitted to the printer 200 in units of segmented data (packets) so that the printer 200 can immediately execute print processing. To do. That is, the printer 200 can execute printing while streaming the data.

Next, details of the XPS data analysis / editing process in step S102 of FIG. 5 will be described.
FIG. 6 is a flowchart illustrating an example of a detailed processing procedure of XPS data analysis / edit processing in step S102 of FIG.

  In the process of step S102 of FIG. 5, first, in step S201 of FIG. 6, the layout filter 144 determines whether there is unprocessed “_rels / .rels” part data. Here, it is determined whether or not there is unprocessed “_rels / .rels” part data. Since the “_rels / .rels” part data is in the XML format as described above, the end tag of the root element is Judgment is made based on whether or not it is unprocessed. Specifically, for example, in the XPS file shown in FIG. 27, when the end element of </ Relationships> described in 2702 is detected, it is determined that the processing of the “_rels / .rels” part data is finished. Note that the end tag of the root element is always present in the last piece. Further, when the interleaving is not performed, there is only one “_rels / .rels” part data. Thereafter, the same method is used to determine whether or not all XML part data has been analyzed (processed).

  If there is no unprocessed “_rels / .rels” part data as a result of the determination in step S201 (that is, if all parts data has been analyzed (processed)), the process of the flowchart in FIG. To do. That is, the process of step S102 in FIG.

  On the other hand, if there is unprocessed “_rels / .rels” part data as a result of the determination in step S201, the process proceeds to step S202.

  In step S202, the layout filter 144 determines whether all unprocessed “_rels / .rels” part data has been acquired. Here, if all of the “_rels / .rels” part data has been acquired, if interleaved, the last piece name when searching for part data (or piece data) in XPS data, which will be described later, is used. Is “/_rels/.rels/[i].last.piece” (i is a serial number starting with 0, and if one part is interleaved into three parts, i of the last piece is 2), the piece data is acquired from the contents of Local_File_Header, and when the piece name data is acquired, it is determined that all pieces are acquired. Thereafter, the same method is used to determine whether or not all parts data has been acquired. If the interleave is not performed, there is only one piece of “_rels / .rels” part data, so that the process of step S203 described later is performed only once.

  If all the unprocessed “_rels / .rels” part data has not been acquired as a result of the determination in step S202, the process proceeds to step S203.

  In step S203, the layout filter 144 searches for the next “_rels / .rels” part data or piece data, and expands and acquires it. At this time, in the present embodiment, a method of searching for Local_File_Header from the head of data is adopted as the search method. Further, the data name in the Local_File_Header to be searched at this time is “_rels / .rels” or “_rels / .rels / [i] .piece” when interleaved. Hereinafter, unless otherwise specified, this method is adopted as a method for searching for part data or the like in XPS data. In this embodiment, a general ZIP data expansion method is adopted as the expansion method, and the expanded data is stored in a form in which various files are written to the external memory 111 while maintaining the directory structure. . Hereinafter, this method is adopted as a decompression method for parts data or the like in XPS data.

  If the process of step S203 is completed, or if it is determined in step S202 that all unprocessed “_rels / .rels” part data has been acquired, the process proceeds to step S204.

  Subsequently, in step S <b> 204, the layout filter 144 analyzes the acquired next “_rels / .rels” part data (piece data) and performs a process of acquiring the FDS data name in the XPS data. Here, as described above, the “_rels / .rels” part data (piece data) is a file described in the XML format. In this embodiment, a general XML file analysis is used as the analysis method. The method shall be adopted. Hereinafter, when a file described in the XML format is analyzed, a general XML file analysis method is adopted as in this example.

  Further, the layout filter 144 performs a process of adding “_rels / .rels” part data (piece data) to the XPS data. That is, the processing here is to convert the already compressed “_rels / .rels” part data (piece data) into the original XPS data in order to generate new XPS data using the original XPS data. It is a process to add. The “_rels / .rels” part data (piece data) added to the XPS data is, for example, 701 in FIG. Here, since “_rels / .rels” part data (piece data) is the first part data (piece data), it is arranged (added) at the head of the XPS data as shown in FIG.

  In step S205, the layout filter 144 determines whether the FDS data name has been acquired in step S204.

  As a result of the determination in step S205, if the FDS data name can be acquired in step S204, the process proceeds to step S206.

  In step S206, the layout filter 144 performs the FDS process.

  When the process of step S206 is completed, or when it is determined in step S205 that the FDS data name could not be acquired, the process returns to step S201, and the processes after step S201 are performed again.

  Through the processes of steps S201 to S206 shown in FIG. 6, the XPS data analysis / editing process in step S102 of FIG. 5 is performed.

Next, details of the FDS processing in step S206 of FIG. 6 will be described.
FIG. 8 is a flowchart illustrating an example of a detailed processing procedure of FDS processing in step S206 of FIG.

  In the process of step S206 in FIG. 6, first, in step S301 in FIG. 8, the layout filter 144 determines whether or not unprocessed FDS part data exists.

  As a result of the determination in step S301, when there is no unprocessed FDS part data (that is, when all parts data has been analyzed (processed)), the process of the flowchart in FIG. That is, the process of step S206 in FIG.

  On the other hand, if it is determined in step S301 that there is unprocessed FDS part data, the process proceeds to step S302.

  In step S302, the layout filter 144 determines whether all unprocessed FDS part data has been acquired.

  If all the unprocessed FDS parts data has not been acquired as a result of the determination in step S302, the process proceeds to step S303.

  In step S303, the layout filter 144 searches for the next FDS part data or piece data, and expands and acquires it.

  When the process of step S303 is completed, or when it is determined in step S302 that all unprocessed FDS part data has been acquired, the process proceeds to step S304.

  Subsequently, in step S304, the layout filter 144 analyzes the acquired next FDS part data (piece data), and performs a process of acquiring one FD data name in the XPS data.

  The layout filter 144 performs processing for adding FDS part data (piece data) to XPS data. In other words, the processing here is to use the FDS part data (piece data) that has already been compressed in order to generate new XPS data by using the FDS part data (piece data) of the original XPS data. This process is added to the XPS data. The FDS part data (piece data) added to the XPS data is, for example, 702 in FIG. Here, as shown in FIG. 7, the FDS part data (piece data) is arranged (added) after 701 which is the “_rels / .rels” part data (piece data) added in step S204 of FIG. )

  Subsequently, in step S305, the layout filter 144 determines whether or not the FD data name has been acquired in step S304.

  As a result of the determination in step S305, if the data name of the FD can be acquired in step S304, the process proceeds to step S306.

  In step S306, the layout filter 144 performs the FD processing.

  When the process of step S306 is completed, or when it is determined in step S305 that the data name of the FD has not been acquired, the process returns to step S301, and the processes after step S301 are performed again.

  The FDS process in step S206 in FIG. 6 is performed through the processes in steps S301 to S306 shown in FIG.

Next, details of the FD processing in step S306 in FIG. 8 will be described.
FIG. 9 is a flowchart illustrating an example of a detailed processing procedure of the FD processing in step S306 in FIG.

  In the process of step S306 in FIG. 8, first, in step S401 of FIG. 9, the layout filter 144 determines whether or not unprocessed FD part data exists.

  As a result of the determination in step S401, when there is no unprocessed FD part data (that is, when all parts data has been analyzed (processed)), the process of the flowchart in FIG. That is, the process of step S306 in FIG.

  On the other hand, if there is unprocessed FD part data as a result of the determination in step S401, the process proceeds to step S402.

  In step S402, the layout filter 144 determines whether all unprocessed FD part data has been acquired.

  If all the unprocessed FD part data has not been acquired as a result of the determination in step S402, the process proceeds to step S403.

  In step S403, the layout filter 144 searches for the next FD part data or piece data and expands and acquires it.

  If the process in step S403 is completed, or if it is determined in step S402 that all unprocessed FD part data has been acquired, the process proceeds to step S404.

  Subsequently, in step S404, the layout filter 144 analyzes the acquired next FD part data (piece data) and performs a process of acquiring one FP data name in the XPS data.

  The layout filter 144 performs a process of adding FD part data (piece data) to XPS data. In other words, the processing here is performed by using the original compressed FD part data (piece data) to generate new XPS data using the FD part data (piece data) of the original XPS data. This process is added to the XPS data. The FD part data (piece data) added to the XPS data is, for example, 703 in FIG. Here, as shown in FIG. 7, the FD part data (piece data) is arranged (added) after 702 which is the FDS part data (piece data) added in step S304 of FIG.

  Subsequently, in step S405, the layout filter 144 determines whether or not the FP data name has been acquired in step S404.

  As a result of the determination in step S405, if the FP data name can be acquired in step S404, the process proceeds to step S406.

  In step S406, the layout filter 144 performs the FP process.

  If the process of step S406 is completed, or if the result of determination in step S405 is that the FP data name could not be acquired in step S404, the process returns to step S401, and the processes after step S401 are performed again.

  The FD process in step S306 in FIG. 8 is performed through the processes in steps S401 to S406 shown in FIG.

Next, details of the FP process in step S406 of FIG. 9 will be described.
FIG. 10 is a flowchart illustrating an example of a detailed processing procedure of FP processing in step S406 of FIG.

  In the process of step S406 of FIG. 9, first, in step S501 of FIG. 10, the layout filter 144 searches for FP part data and expands and acquires it. At this time, the FP created by MXDW is not normally interleaved.

  Subsequently, in step S502, the layout filter 144 analyzes the FP part data acquired in step S501, obtains the reference count of the external resource to be referenced, and creates an external resource reference list (external resource reference count list). I do.

  In step S503, the layout filter 144 edits the print ticket and includes it in the XPS data.

  Subsequently, in step S504, the layout filter 144 performs FP division processing.

  Through the processes in steps S501 to S504 shown in FIG. 10, the FP process in step S406 in FIG. 9 is performed.

Next, details of the external resource reference count list creation processing in step S502 of FIG. 10 will be described.
FIG. 11 is a flowchart showing an example of a detailed processing procedure of the external resource reference number list creation processing in step S502 of FIG.

  In the process of step S502 of FIG. 10, first, in step S601 of FIG. 11, the layout filter 144 analyzes the FP part data acquired in the process of step S501 of FIG. 10, and detects (extracts) a drawing command. I do.

  Subsequently, in step S602, the layout filter 144 determines whether or not the drawing command detected (extracted) in step S601 includes a reference to an external resource such as image data or font data.

  As a result of the determination in step S602, if the drawing command detected in step S601 includes an external resource reference, the process proceeds to step S603.

  In step S603, the layout filter 144 determines whether the external resource name related to the external resource detected in step S602 is already included in the external reference resource list.

Here, the external reference resource list will be described.
FIG. 12 is a schematic diagram illustrating an example of the external reference resource list according to the embodiment of this invention. The external reference resource list shown in FIG. 12 is created, for example, when the FP as shown in FIG. 33 described above is analyzed.

  The external reference resource list shown in FIG. 12 is created by the layout filter 144 and stored in the external memory 111, for example. Also, as shown in FIG. 12, in the external reference resource list, the external resource name, the number of references, and the referenced flag are set for each external resource. The referenced flag is an area used in the FP division process in step S504 in FIG.

Here, it returns to description of FIG. 11 again.
As a result of the determination in step S603, if the external resource name related to the external resource detected in step S602 is already included in the external reference resource list shown in FIG. 12, the process proceeds to step S604.

  In step S604, the layout filter 144 performs a process of incrementing the reference count of the external resource name in the external reference resource list shown in FIG.

  On the other hand, as a result of the determination in step S603, if the external resource name related to the external resource detected in step S602 is not included in the external reference resource list shown in FIG. 12, the process proceeds to step S605.

  In step S605, the layout filter 144 performs processing for adding the newly detected external resource name to the external reference resource list shown in FIG.

  When the process of step S604 or step S605 is completed, or when it is determined in step S602 that the drawing command does not include a reference to an external resource, the process proceeds to step S606.

  In step S606, the layout filter 144 determines whether the analysis has been performed up to the end of the FP part data currently being processed. If the result of this determination is that analysis has not yet been performed up to the end of the FP part data currently being processed, the process returns to step S601, and the processing from step S601 is performed again.

  On the other hand, as a result of the determination in step S606, if the analysis is performed up to the end of the FP part data currently being processed, the processing of the flowchart in FIG. That is, the process of step S502 in FIG.

Next, details of the print ticket editing process in step S503 in FIG. 10 will be described.
FIG. 13 is a flowchart illustrating an example of a detailed processing procedure of the print ticket editing process in step S503 of FIG.

  In the process of step S503 of FIG. 10, first, in step S701 of FIG. 13, the layout filter 144 determines whether there is a print ticket associated with FP (FixedPage) part data.

  If the result of determination in step S701 is that there is no print ticket associated with FP part data, the process proceeds to step S702.

  In step S702, the layout filter 144 creates a print ticket and includes it in the XPS data.

  If the process in step S702 is completed, or if it is determined in step S701 that there is a print ticket associated with the FP part data, the process proceeds to step S703.

  In step S703, the layout filter 144 uses the contents of the external reference resource list created in step S502 of FIG. 10 as child elements one layer below the <PrintTicket> root tag as shown in FIG. > The tag 1401 is inserted.

  Here, FIG. 14 is a schematic diagram illustrating an example of a print ticket according to the embodiment of the present invention. As described above, the layout filter 144 reflects the contents of the external reference resource list created in step S <b> 502 of FIG. 10 in the <Feature> tag 1401. Here, the information of “external resource name” and “reference count” in the external reference resource list shown in FIG. 12 is reflected. Specifically, information of “external resource name” is reflected in 1402 of <Feature> tag 1401 shown in FIG. 14, and information of “reference count” is reflected in 1403 of <Feature> tag 1401.

  Here, a general XML analysis module having an interface such as DOM is used to insert the <Feature> tag 1401. The method of expressing the information of the external reference resource list in the print ticket may be any method as long as the information of the external reference resource list shown in FIG. 12 can be uniquely restored.

  Through the processes in steps S701 to S703 shown in FIG. 13, the print ticket editing process in step S503 in FIG. 10 is performed.

Next, details of the FP division processing in step S504 in FIG. 10 will be described.
FIG. 15 is a flowchart illustrating an example of a detailed processing procedure of the FP division processing in step S504 of FIG.

  In the process of step S504 in FIG. 10, first, in step S801 in FIG. 15, the layout filter 144 performs a process of acquiring the limit memory amount of the printer 200. This limit memory amount value is held as a fixed value in the printer driver.

  Subsequently, in step S802, the layout filter 144 secures an area corresponding to the memory amount (total) of the external resources, for example, in the storage area of the external memory 111, and sets the value of the area (total external resource memory amount) to 0. Set to.

  Subsequently, in step S803, the layout filter 144 secures an area corresponding to the memory amount (total) of the FP data being processed, for example, in the storage area of the external memory 111, and the value of the area (total processing FP memory amount) ) Is set to 0.

  The area secured in steps S802 and S803 is used during the FP division process.

  Subsequently, in step S804, the layout filter 144 performs a process of detecting (acquiring) one drawing command.

  Subsequently, in step S805, the layout filter 144 performs processing for adding the XML data amount from the detection start time to the detection end time in step S804 to the total processing FP memory amount.

  Subsequently, in step S806, the layout filter 144 determines whether or not the drawing command detected in step S804 refers to an external resource.

  As a result of the determination in step S806, if the drawing command detected in step S804 refers to an external resource, the process proceeds to step S807.

  In step S807, the layout filter 144 determines whether the external resource detected in step S806 exists in the external resource reference list. Here, when the external resource does not exist in the external resource reference list, it means that the external resource has already been added to the XPS data.

  If it is determined in step S807 that the external resource detected in step S806 exists in the external resource reference list, the process proceeds to step S808.

  In step S808, the layout filter 144 decrements the reference count of the external resource in the external reference resource list, and sets the referenced flag to ON.

  Subsequently, in step S809, the layout filter 144 determines whether the reference count of the external resource in the external reference resource list is zero.

  As a result of the determination in step S809, when the reference count of the external resource in the external reference resource list is 0, the process proceeds to step S810.

  In step S810, the layout filter 144 performs FP division processing based on the drawing command currently being detected. Specifically, the FP piece data is expanded, the portion from the expanded data to the drawing command currently being detected is extracted, and the extracted data is created as divided FP piece data (part data). More specifically, the FP is divided from the position where the previous FP was divided to the drawing command currently being detected, and this is created as FP piece data (part data). Then, the layout filter 144 compresses the created FP piece data and adds it to the XPS data.

  Here, the FP piece data created in step S810 is initially after the FD part data (piece data) added in step S404 in FIG. 9 and after 704 and 705 in FIG. 7 are added. 7 is arranged and added as 706 in FIG. Further, the FP piece data created next is arranged and added as 709 in FIG. 7 after the external resource added in step S811, which is a subsequent process.

  Subsequently, in step S811, the layout filter 144 searches the external reference resource list from the top, and converts the currently detected external resource to XPS data immediately after the divided FP piece data (eg, 706 in FIG. 7). to add. For example, in the example shown in FIG. 7, the currently detected external resources are arranged and added as 707 and 708 in FIG.

  Subsequently, in step S812, the layout filter 144 performs a process of deleting from the head of the external reference resource list to the currently detected external resource from the external reference resource list.

  Subsequently, in step S813, the layout filter 144 sets the total external resource memory amount to zero.

  Subsequently, in step S814, the layout filter 144 sets the total processing FP memory amount to zero.

  If it is determined in step S809 that the number of references to the external resource in the external reference resource list is not 0, the process proceeds to step S815.

  In step S815, the layout filter 144 performs processing to add the detected external resource memory amount (specifically, the amount of memory after expansion of the external resource) to the external resource memory amount total. At this time, the amount of memory after expansion of the external resource to be added is described in the ZIP header, and is referred to.

  When the process of step S815 is completed, when it is determined in step S806 that the drawing command detected in step S804 does not refer to the external resource, or in step S807, the external resource detected in step S806 is included in the external resource reference list. If it is determined that it does not exist, the process proceeds to step S816.

  In step S816, the layout filter 144 determines whether the sum of the processing FP memory amount and the external resource memory amount exceeds the limit memory amount of the printer 200 acquired in step S801.

  As a result of the determination in step S816, if the sum of the processing FP memory amount and the external resource memory amount exceeds the limit memory amount of the printer 200 acquired in step S801, the process proceeds to step S817.

  In step S817, the layout filter 144 performs the same processing as in step S810, that is, performs FP division based on the drawing command currently detected, compresses the FP piece data created by the division, and generates XPS data. Add to Note that the XPS data to be added is data divided at a position that does not exceed the limit memory amount of the printer 200 acquired in step S801.

  Subsequently, when proceeding to step S818, the layout filter 144 searches the external reference resource list from the top, and continues all the external resources whose referenced flags are ON immediately after the FP piece data added in step S817. To add to the XPS data.

  Subsequently, in step S819, the layout filter 144 searches the external reference resource list from the top, and performs a process of deleting all external resources for which the referenced flag is ON from the external reference resource list.

  Subsequently, in step S820, the layout filter 144 sets the same processing as in step S813, that is, sets the total external resource memory amount to zero.

  Subsequently, in step S821, the layout filter 144 sets the processing similar to that in step S814, that is, the total processing FP memory amount to 0.

  When the process of step S814 is completed, when the process of step S821 is completed, or in step S816, it is determined that the total of the processing FP memory amount and the external resource memory amount does not exceed the limit memory amount of the printer 200. If so, the process proceeds to step S822.

  In step S822, the layout filter 144 determines whether the analysis has been performed up to the end of the FP part data currently being processed. If the result of this determination is that analysis has not yet been performed up to the end of the FP part data currently being processed, processing returns to step S804, and processing from step S804 onward is performed again.

  On the other hand, if the result of determination in step S822 is that analysis has been performed up to the end of the FP part data currently being processed, the process proceeds to step S823.

  In step S823, the layout filter 144 adds a portion (processing portion) not added to the XPS data to the XPS data as the last FP piece data. Thereafter, the process of the flowchart in FIG. That is, the process of step S504 in FIG. Thus, a print ticket (attribute information file) that stores attributes used when printing an FP part (print target data), including the number of times the resource file is referred to by the FP part (print target data), is divided. The archive data including the FP piece data (print target data) file, the FD part (page configuration data) file, and the resource file created by the above is generated.

  In FIG. 15, by performing the processing of steps S810 and S811, or steps S818 and S819, XPS data obtained by dividing the FP part data is generated, and XPS data can be directly printed even by a low-cost printer with a small amount of memory. Become.

FIG. 16 is a schematic diagram illustrating an example of the FP divided by the layout filter 144 illustrated in FIG. 4 according to the embodiment of this invention.
When the FP shown in FIG. 33 is divided using the external reference resource list shown in FIG. 12, if the limit memory amount of the printer 200 is never exceeded, the result is as shown in FIG. Then, this is arranged in the XPS data as shown in FIG. In this case, the last FP piece data added in step S823 is, for example, “/Document/1/Page/1.Fpage/[3].Last.” Indicated by 1604 in FIG. 16 and 713 in FIG. “Piece”. Further, if the value of the limit memory amount of the printer 200 is small, it may be divided for each reference location as shown in FIGS.

  FIG. 17 is a flowchart illustrating an example of a processing procedure of print control processing using an XPS print path by the printer 200 of the print control system 10 according to the embodiment of the present invention.

First, in step S <b> 901 in FIG. 17, the CPU 201 of the printer 200 receives XPS data from the host computer 100. The received XPS data is data transmitted by the host computer 100 in units of fragmented data (packets) so that the printer 200 can immediately perform printing processing. Further, according to the reception of the data stream, the segmented data is sequentially stored and stored in the storage area (for example, the external memory 210) of the printer 200 (data stream).
Note that the data stream in step S901 is performed while executing the process in step S902 described later. In step S902, the data stream is sequentially read from the storage area of the printer 200 (for example, the external memory 210). Note that the processing in step S902 waits for processing when a unit (one file (part)) that can be executed by each processing is not received (cannot be read).

  In step S902, the CPU 201 of the printer 200 analyzes the XPS data acquired in step S901, and performs XPS data printing processing.

Next, the details of the XPS data analysis / printing process in step S902 of FIG. 17 will be described.
FIG. 18 is a flowchart illustrating an example of a detailed processing procedure of XPS data analysis / print processing in step S902 of FIG.

  In the process of step S902 of FIG. 17, first, in step S1001 of FIG. 18, the CPU 201 of the printer 200 determines whether or not unprocessed “_rels / .rels” part data exists.

  If there is no unprocessed “_rels / .rels” part data as a result of the determination in step S1001 (that is, if all parts data has been analyzed (processed)), the process of the flowchart in FIG. 18 ends. To do. That is, the process of step S902 in FIG.

  On the other hand, as a result of the determination in step S1001, if unprocessed “_rels / .rels” part data exists, the process proceeds to step S1002.

  In step S1002, the CPU 201 of the printer 200 determines whether all unprocessed “_rels / .rels” part data has been acquired.

  If all the unprocessed “_rels / .rels” part data has not been acquired as a result of the determination in step S1002, the process proceeds to step S1003.

  In step S1003, the CPU 201 of the printer 200 searches for the next “_rels / .rels” part data or piece data, expands and acquires it.

  When the process of step S1003 is completed, or when it is determined in step S1002 that all unprocessed “_rels / .rels” part data has been acquired, the process proceeds to step S1004.

  In step S <b> 1004, the CPU 201 of the printer 200 analyzes the next acquired “_rels / .rels” part data (piece data), and performs processing for acquiring the FDS data name in the XPS data. Here, as described above, the “_rels / .rels” part data (piece data) is a file described in the XML format. In this embodiment, a general XML file analysis is used as the analysis method. The method shall be adopted. Hereinafter, when a file described in the XML format is analyzed, a general XML file analysis method is adopted as in this example.

  In step S1005, the CPU 201 of the printer 200 determines whether the FDS data name has been acquired in step S1004.

  If it is determined in step S1005 that the FDS data name has been acquired in step S1004, the process advances to step S1006.

  In step S1006, the CPU 201 of the printer 200 performs the FDS process.

  When the process of step S1006 is completed, or when it is determined in step S1005 that the FDS data name could not be acquired, the process returns to step S1001, and the processes after step S1001 are performed again.

  Through the processes of steps S1001 to S1006 shown in FIG. 18, the XPS data analysis / print process in step S902 of FIG. 17 is performed. That is, the process of FIG. 18 is the same as the process of FIG. 6 performed by the layout filter 144 of the host computer 100.

Next, details of the FDS processing in step S1006 of FIG. 18 will be described.
FIG. 19 is a flowchart illustrating an example of a detailed processing procedure of FDS processing in step S1006 of FIG.

  In step S1006 of FIG. 18, first, in step S1101 of FIG. 19, the CPU 201 of the printer 200 determines whether or not unprocessed FDS part data exists.

  If there is no unprocessed FDS part data as a result of the determination in step S1101 (that is, if all parts data has been analyzed (processed)), the processing of the flowchart in FIG. That is, the process of step S1006 in FIG.

  On the other hand, if it is determined in step S1101 that there is unprocessed FDS part data, the process advances to step S1102.

  In step S1102, the CPU 201 of the printer 200 determines whether all unprocessed FDS part data has been acquired.

  If all the unprocessed FDS parts data has not been acquired as a result of the determination in step S1102, the process proceeds to step S1103.

  In step S1103, the CPU 201 of the printer 200 searches for the next FDS part data or piece data, and decompresses and acquires the data.

  When the process of step S1103 is completed, or when it is determined in step S1102 that all unprocessed FDS part data has been acquired, the process proceeds to step S1104.

  Subsequently, in step S1104, the CPU 201 of the printer 200 analyzes the acquired next FDS part data (piece data) and performs a process of acquiring one FD data name in the XPS data.

  Subsequently, in step S1105, the CPU 201 of the printer 200 determines whether or not the FD data name has been acquired in step S1104.

  If it is determined in step S1105 that the FD data name has been acquired in step S1104, the process advances to step S1106.

  In step S1106, the CPU 201 of the printer 200 performs the FD processing.

  When the process of step S1106 is completed, or when it is determined in step S1105 that the FD data name could not be acquired, the process returns to step S1101 and the processes after step S1101 are performed again.

  Through the processes of steps S1101 to S1106 shown in FIG. 19, the FDS process in step S1006 of FIG. 18 is performed. That is, the process of FIG. 19 is the same as the process of FIG. 8 performed by the layout filter 144 of the host computer 100.

Next, details of the FD processing in step S1106 of FIG. 19 will be described.
FIG. 20 is a flowchart illustrating an example of a detailed processing procedure of the FD processing in step S1106 of FIG.

  In the process of step S1106 of FIG. 19, first, in step S1201 of FIG. 20, the CPU 201 of the printer 200 determines whether or not unprocessed FD part data exists.

  As a result of the determination in step S1201, when there is no unprocessed FD part data (that is, when all the part data has been analyzed (processed)), the process of the flowchart in FIG. That is, the process of step S1106 in FIG.

  On the other hand, if there is unprocessed FD part data as a result of the determination in step S1201, the process proceeds to step S1202.

  In step S1202, the CPU 201 of the printer 200 determines whether all unprocessed FD part data has been acquired.

  If all the unprocessed FD part data has not been acquired as a result of the determination in step S1202, the process proceeds to step S1203.

  In step S1203, the CPU 201 of the printer 200 searches for the next FD part data or piece data, and expands and acquires it.

  If the process of step S1203 is completed, or if it is determined in step S1202 that all unprocessed FD part data has been acquired, the process proceeds to step S1204.

  Subsequently, in step S1204, the CPU 201 of the printer 200 analyzes the acquired next FD part data (piece data), and performs a process of acquiring one FP data name in the XPS data.

  In step S1205, the CPU 201 of the printer 200 determines whether or not the FP data name has been acquired in step S1204.

  If it is determined in step S1205 that the FP data name has been acquired in step S1204, the process advances to step S1206.

  In step S1206, the CPU 201 of the printer 200 performs the FP process.

  When the process of step S1206 is completed, or when it is determined in step S1205 that the FP data name could not be acquired, the process returns to step S1201, and the processes after step S1201 are performed again.

  Through the processes in steps S1201 to S1206 shown in FIG. 20, the FD process in step S1106 in FIG. 19 is performed. That is, the process of FIG. 20 is the same as the process of FIG. 9 performed by the layout filter 144 of the host computer 100.

Next, details of the FP process in step S1206 of FIG. 20 will be described.
FIG. 21 is a flowchart illustrating an example of a detailed processing procedure of FP processing in step S1206 of FIG.

  In the process of step S1206 in FIG. 20, first, in step S1301 in FIG. 21, the CPU 201 of the printer 200 searches for and acquires the print ticket 3505 associated with the FP part data, for example, as shown in FIG. A safe external reference resource list. Since the print ticket 3505 is received by the printer 200 prior to the FP parts data, an external reference resource list as shown in FIG. 12 can be created at this timing.

  Subsequently, in step S1302, the CPU 201 of the printer 200 determines whether there is unprocessed FP part data. When the FP parts are divided, each FP part data has the subscripts [1] [2] [3]... [I] added to the data name of the FP acquired in step S1204. That is, even when an FP part is divided, it is possible to determine whether or not there is unprocessed FP part data using the FP data name.

  If there is no unprocessed FP part data as a result of the determination in step S1302 (that is, if all parts data has been analyzed (processed)), the processing of the flowchart in FIG. That is, the process of step S1206 in FIG.

  On the other hand, if there is unprocessed FP part data as a result of the determination in step S1302, the process proceeds to step S1303.

  In step S1303, the CPU 201 of the printer 200 determines whether all unprocessed FP part data has been acquired.

  If it is determined in step S1303 that all unprocessed FP part data has not been acquired, the process advances to step S1304.

  In step S1304, the CPU 201 of the printer 200 searches for the next FP part data or piece data, and decompresses and acquires the data.

  Subsequently, in step S1305, the CPU 201 of the printer 200 performs a drawing command process for the FP part data or piece data acquired in step S1305.

  When the process of step S1305 is completed, or when it is determined in step S1303 that not all the unprocessed FP part data has been acquired, the process returns to step S1302, and the processes after step S1302 are performed again.

  The FP process in step S1206 in FIG. 20 is performed through the processes in steps S1301 to S1305 shown in FIG.

Next, the details of the FP part data or piece data drawing command processing (FP drawing command processing) in step S1305 of FIG. 21 will be described.
FIG. 22 is a flowchart illustrating an example of a detailed processing procedure of the FP drawing command processing in step S1305 of FIG.

  In step S1305 in FIG. 21, first, in step S1401 in FIG. 22, the CPU 201 of the printer 200 analyzes the FP data acquired in step S1304 in FIG. 21, and detects (extracts) a drawing command. I do.

  In step S1402, the CPU 201 of the printer 200 determines whether the drawing command detected (extracted) in step S1401 includes a reference to an external resource such as image data or font data.

  If the result of determination in step S1402 is that the rendering command detected in step S1401 includes a reference to an external resource, the process proceeds to step S1403.

  In step S1403, the CPU 201 of the printer 200 acquires an external resource stored in a storage area (for example, the external memory 210) of the printer 200 and performs a drawing process. At this time, the external resource referred to from the drawing command detected in step S1401 is arranged immediately after the FP piece data in which the drawing command is described in the process of step S1404, which is a subsequent process. It exists in the storage area.

  Subsequently, in step S1404, the CPU 201 of the printer 200 decrements the reference count of the detected external resource in the external reference resource list created in step S1301.

  In step S1405, the CPU 201 of the printer 200 determines whether the number of times the external resource is referenced in the external reference resource list is zero.

  If the result of determination in step S1405 is that the number of times the external resource is referenced in the external reference resource list is 0, processing proceeds to step S1406.

  In step S 1406, the CPU 201 of the printer 200 performs a process for deleting the external resource stored in the storage area of the printer 200. If the reference count is 0, the external resource stored in the storage area of the printer 200 will not be referenced again in the FP being processed, and there is no problem even if it is deleted from the storage area. Because. In this way, it is possible to give a margin to the storage area of the printer 200 by deleting external resources that will not be referred to in the future.

  When the processing in step S1406 is completed, when it is determined in step S1402 that the external resource reference is not included in the rendering command, or in step S1405, the reference count of the external resource in the external reference resource list is not zero. If it is determined, the process proceeds to step S1407.

  In step S1407, the CPU 201 of the printer 200 performs a process of deleting from the storage area (for example, the external memory 210) of the printer 200 because the FP part data or piece data currently being processed will not be referred to in the future. .

  In step S1408, the CPU 201 of the printer 200 determines whether the analysis has been performed up to the end of the FP part data or piece data currently being processed. If the result of this determination is that analysis has not yet been performed up to the end of the FP part data or piece data currently being processed, processing returns to step S1401, and processing from step S1401 is performed again.

  On the other hand, as a result of the determination in step S1408, if the analysis is performed up to the end of the FP part data or piece data currently being processed, the processing of the flowchart in FIG. That is, the process of step S1305 in FIG.

As described above, the host computer 100 (information processing apparatus) of the print control system 10 according to the present embodiment performs the following processing.
First, a page configuration data (FD) file in which document configuration information is described, a print target data (FP) file in which information on pages to be printed in the printer 200 is described based on the FD, and XPS data (archive data) including a resource file referred to based on FP is acquired (for example, S101 in FIG. 5: archive data acquisition step). Thereafter, the FP file is divided (for example, S810 and S817: division step in FIG. 15). Then, a print ticket (attribute information file) that stores attributes used when printing the FP, including the reference count for referring to the resource file in the print target data (FP), and the FP divided by the dividing step XPS data (archive data) including a file, an FD file, and a resource file is generated (for example, S823 in FIG. 15: archive data generation step).
According to this configuration, when XPS data processed by the host computer 100 is printed on the printer 200 side, XPS data including a resource file is appropriately printed even if the printer has a small memory capacity. be able to.

  Further, the host computer 100 acquires the memory amount (first memory amount) of the printer 200 (S801 in FIG. 15: printer memory amount acquisition step), and the memory amount based on the FP data amount is acquired in S801. It is determined whether or not (second memory amount) is exceeded (S816 in FIG. 15: determination step), and in the division step, in addition to information on the number of references referring to the resource file, the determination in the determination step Based on the result, the FP file is divided. Further, in the dividing step, in addition to the information on the number of references for referring to the resource file and the result of the determination in the determining step, the file of the FP is further converted based on the information on the already-referenced resource file (referenced flag). I try to divide it.

Further, the printer 200 of the print control system 10 according to the present embodiment performs the following processing.
First, XPS data edited by the host computer 100 is received, and the XPS data is stored in a storage area (for example, the external memory 210) of the printer 200 (S901 in FIG. 17). When the XPS data is printed, the resource file included in the XPS data stored in the storage area of the printer 200 is deleted according to the reference count information included in the XPS data. (S1406 in FIG. 22: deletion step).

(Other embodiments of the present invention)
3 and 4 constituting the host computer 100 of the print control system 10 according to the embodiment of the present invention, and print control processing in the host computer 100 and the printer 200 are shown in FIGS. 8 to 11, 13, 15, and 17 to 22 can be realized by the CPU of the computer executing a program stored in a ROM or the like. This program and a computer-readable recording medium recording the program are included in the present invention.

  In addition, the present invention can be implemented as, for example, a system, apparatus, method, program, storage medium, or the like. Specifically, the present invention may be applied to a system including a plurality of devices. You may apply to the apparatus which consists of one apparatus.

  The present invention corresponds to the software program for realizing the functions of the above-described embodiments (in the embodiment, the flowcharts shown in FIGS. 5, 6, 8 to 11, 13, 15, and 17 to 22). Program) directly or remotely to a system or apparatus. The present invention also includes a case where the system or the computer of the apparatus is achieved by reading and executing the supplied program code.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, and the like.

  Examples of the recording medium for supplying the program include a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. In addition, there are magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R), and the like.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. The computer program itself of the present invention or a compressed file including an automatic installation function can be downloaded from the homepage by downloading it to a recording medium such as a hard disk.

  It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. Let It is also possible to execute the encrypted program by using the downloaded key information and install the program on a computer.

  Further, the functions of the above-described embodiments are realized by the computer executing the read program. In addition, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments are realized by the processing.

  Note that each of the above-described embodiments is merely a specific example for carrying out the present invention, and the technical scope of the present invention should not be construed as being limited thereto. . That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.

1 is a schematic diagram illustrating an example of a schematic configuration of a print control system according to an embodiment of the present invention. It is a schematic diagram which shows the modification of schematic structure of the printing control system which concerns on embodiment of this invention. It is a schematic diagram showing an example of a functional configuration of a print control function using a GDI print path by a host computer of the print control system according to the embodiment of the present invention. FIG. 3 is a schematic diagram illustrating an example of a functional configuration of a print control function using an XPS print path by a host computer of a print control system according to an embodiment of the present invention. 6 is a flowchart illustrating an example of a processing procedure of print control processing using an XPS print path by a host computer of the print control system according to the embodiment of the present invention. 6 is a flowchart illustrating an example of a detailed processing procedure of XPS data analysis / editing processing in step S102 of FIG. 5; It is a schematic diagram which shows embodiment of this invention and shows an example of XPS data containing FP. 7 is a flowchart illustrating an example of a detailed processing procedure of FDS processing in step S206 of FIG. 6. It is a flowchart which shows an example of the detailed process sequence of the process of FD in step S306 of FIG. 10 is a flowchart illustrating an example of a detailed processing procedure of FP processing in step S406 of FIG. 9. It is a flowchart which shows an example of the detailed process sequence of the external resource reference frequency list creation process in step S502 of FIG. It is a schematic diagram which shows embodiment of this invention and shows an example of an external reference resource list | wrist. 11 is a flowchart illustrating an example of a detailed processing procedure of a print ticket editing process in step S503 in FIG. 1 is a schematic diagram illustrating an example of a print ticket according to an embodiment of the present invention. It is a flowchart which shows an example of the detailed process sequence of FP division | segmentation process in FIG.10 S504. FIG. 5 is a schematic diagram illustrating an example of an FP divided in the layout filter illustrated in FIG. 4 according to the embodiment of this invention. 6 is a flowchart illustrating an example of a processing procedure of print control processing using an XPS print path by a printer of the print control system according to the embodiment of the present invention. 18 is a flowchart illustrating an example of a detailed processing procedure of XPS data analysis / print processing in step S902 in FIG. 19 is a flowchart illustrating an example of a detailed processing procedure of FDS processing in step S1006 of FIG. 20 is a flowchart illustrating an example of a detailed processing procedure of FD processing in step S1106 of FIG. 19. 21 is a flowchart illustrating an example of a detailed processing procedure of FP processing in step S1206 of FIG. It is a flowchart which shows an example of the detailed process sequence of FP drawing command process in step S1305 of FIG. It is a schematic diagram which shows an example of the image of a structure of XPS data. It is a schematic diagram which shows an example of the logical structure of the reference relationship of each part included in the XPS data shown in FIG. It is a schematic diagram which shows an example of the reference relationship based on the description of an XML file. It is a schematic diagram which shows an example of the print ticket based on the description of an XML file. It is a schematic diagram which shows an example of the data order of the XPS file normally generated by MXDW. FIG. 26 is a schematic diagram illustrating an example of part data when the XPS data illustrated in FIG. 25 is interleaved. It is a schematic diagram which shows an example of the image of a structure of XPS data at the time of making it interleave. It is a schematic diagram which shows an example of the data order of the XPS file at the time of interleaving. It is a schematic diagram which shows an example of a structure of ZIP compression data. It is a schematic diagram which shows an example of the data order of the interleaved XPS file. FIG. 33 is a schematic diagram illustrating an example of an FP in the XPS file illustrated in FIG. 32. It is a schematic diagram which shows an example of the division | segmentation process of FP. It is a schematic diagram which shows an example of the data order of an XPS file.

Explanation of symbols

10-1 Print Control System 100 Host Computer (Client Computer)
101 CPU
102 RAM
103 ROM
104 System bus 105 Input C (input controller)
106 VC (video controller)
107 MC (memory controller)
108 Communication I / F (communication interface)
109 KB (keyboard)
110 CRT (CRT display)
111 External memory 200 Printer 201 CPU
202 RAM
203 ROM
204 System bus 205 Communication I / F (communication interface)
206 Print section I / F (print section interface)
207 MC (memory controller)
208 Printing unit 209 Operation unit 210 External memory 300 Network

Claims (9)

An information processing apparatus communicably connected to a printer,
A page configuration data file in which document configuration information is described, a print target data file that is referred to based on the page configuration data and in which information on a page to be printed in the printer is described, and the print target data Archive data acquisition means for acquiring archive data including resource files referred to based on;
A dividing unit for dividing the file of the print target data;
An attribute information file for storing attributes used when printing the print target data, including the number of times the resource file is referred to by the print target data; and the file of the print target data divided by the dividing unit And an archive data generating means for generating archive data including the page configuration data file and the resource file.   The information processing apparatus according to claim 1, wherein the dividing unit divides the file of the print target data according to a reference count stored in the attribute information file. Printer memory amount acquisition means for acquiring a first memory amount of the printer;
Determination means for determining whether or not a second memory amount based on the data amount of the file of the print target data exceeds the first memory amount acquired by the printer memory amount acquisition unit;
The dividing unit divides the file of the print target data at a position not exceeding the first memory amount when the determining unit determines that the second memory amount exceeds the first memory amount. The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. Attribute information file determination means for determining whether or not the attribute information file exists;
An attribute information file generating means for generating the attribute information file, storing a reference count for referring to the resource file in the print target data;
When it is determined that the attribute information file does not exist, when it is determined that the attribute information file exists in the attribute information file generated by the attribute information file generation unit, the attribute information file that already exists The information processing apparatus according to claim 1, further comprising: a reference number input unit configured to input the reference number. The resource file is an image file or a font file,
The information processing apparatus according to claim 4, wherein the reference count input unit inputs the reference count for each image file or font file referred to in the print target data to the attribute information file.   The information processing apparatus according to claim 1, further comprising a transmission unit configured to transmit the archive data generated by the archive data generation unit to the printer. A print control system comprising an information processing device and a printer,
The information processing apparatus includes:
A page configuration data file in which document configuration information is described, a print target data file that is referred to based on the page configuration data and in which information on a page to be printed in the printer is described, and the print target data Archive data acquisition means for acquiring archive data including a resource file referred to based on;
A dividing unit for dividing the file of the print target data;
An attribute information file for storing attributes used when printing the print target data, including the number of times the resource file is referred to by the print target data; and the file of the print target data divided by the dividing unit And archive data generation means for generating archive data including the page configuration data file and the resource file,
The printer is
Receiving means for sequentially receiving the archive data generated by the archive data generating means;
A printing control system comprising: a deleting unit that deletes a resource file included in the archive data received by the receiving unit according to the number of times the attribute information file included in the archive data is referenced. A method for controlling an information processing apparatus connected to a printer in a communicable manner,
A page configuration data file in which document configuration information is described, a print target data file that is referred to based on the page configuration data and in which information on a page to be printed in the printer is described, and the print target data An archive data acquisition step for acquiring archive data including a resource file referred to based on;
A dividing step of dividing the file of the print target data;
An attribute information file for storing attributes used when printing the print target data, including a reference count for referring to the resource file in the print target data; and the file of the print target data divided by the dividing step And an archive data generation step of generating archive data including the page configuration data file and the resource file. A program for causing a computer to execute a control method of an information processing apparatus that is communicably connected to a printer,
A page configuration data file in which document configuration information is described, a print target data file that is referred to based on the page configuration data and in which information on a page to be printed in the printer is described, and the print target data An archive data acquisition step for acquiring archive data including a resource file referred to based on;
A dividing step of dividing the file of the print target data;
An attribute information file for storing attributes used when printing the print target data, including a reference count for referring to the resource file in the print target data; and the file of the print target data divided by the dividing step And an archive data generation step for generating archive data including the page configuration data file and the resource file.

Images