JP2008123345A - Information processing apparatus, information processing method and program, and storage medium storing the program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processor, an information processing method, an information processing program, and a storage medium storing the program for preventing breakage of coded image data when printing is carried out while setting the coded image data and the stamp image data. <P>SOLUTION: A spool file manager reads a configuration of the stamp image data from a spool file and starts management of a job. A coded image detection part detects whether coded image data are included in document image data or not, and if the coded image data are included, determines whether the stamp image data overlaps with the coded image data or not. Then, breakage of the coded image data is prevented by stopping print processing itself, composing no stamp image data, or changing/shrinking the position of the stamp image data. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an information processing apparatus capable of handling encoded image data, an information processing method and program, and a storage medium storing the program. More specifically, the present invention relates to processing when printing encoded image data and stamp image data in an information processing apparatus such as a personal computer.

  Conventionally, when a mark having a character string such as “confidential” or “circulation” is added to a document, stamp image data has been used.

  A technique for giving such a mark when image data created by an application operating on a host computer such as a personal computer is printed by a printer is known. That is, a function of adding a stamp mark or a watermark to the printer driver is incorporated (see Patent Document 1).

  The printer driver is software that receives a drawing instruction from an application via a graphics module of an operating system (OS) and generates image recording data unique to the output destination printer in accordance with the drawing instruction.

  This printer driver is unique to the OS and does not depend on individual applications. For this reason, conventionally, a function for superimposing and outputting a common mark on an image created by an arbitrary application without modifying an existing application is also incorporated in the printer driver (see Patent Document 2). .

  Conventionally, as represented by barcodes and QR codes (two-dimensional codes), information such as products is converted into encoded image data and embedded in output paper (in this case, there are many labels and the like). It was. By reading such output paper with a reader (reader), information before being encoded is acquired and used for product management or the like.

  Recently, not only text data (character information) but also an image and various other information are converted into encoded image data and embedded in paper. A method has been considered (see Patent Document 3). In Patent Document 3, the original file together with thumbnails (images reduced to display a large number of images as a list) is converted into encoded image data, printed on output paper, and the output paper is read by a copying machine. The original file can be printed.

JP 2001-197297 A JP 2004260852 A JP 2001-344588

  When the encoded image data is generated by encoding the information, and the stamp image data is added to the print data obtained by synthesizing the encoded image data with the original image data, the encoded image data and the stamp image data overlap. May be printed. In such a case, the encoded image data is damaged and cannot be read accurately.

  The present invention has been made in view of such a problem, and an object of the present invention is to damage the encoded image data when the encoded image data and the stamp image data are set and printed. An object is to provide an information processing apparatus and an information processing method that are not allowed to be performed.

  In order to solve the above problem, an information processing apparatus according to the present invention includes a first determination unit that determines whether or not there is a setting for combining a stamp image with a document image, and the encoded image is combined with the document image. If the second determination unit and the first determination unit determine that there is a setting, and the second determination unit determines that the encoded image is synthesized, the original image includes A third determination unit that determines whether or not the stamp image and the encoded image overlap, and if the third determination unit determines that the stamp image and the encoded image overlap, the user is notified that the stamp image and the encoded image overlap. And notifying means for notifying the user.

  The information processing method of the present invention also includes a first determination step for determining whether or not there is a setting for combining a stamp image with a document image, and determining whether or not an encoded image is combined with the document image. When it is determined that there is a setting in the second determination step and the first determination step, and it is determined in the second determination step that the encoded image is synthesized, the stamp image and the encoded image in the document image A determination step for determining whether or not the stamp image and the encoded image are overlapped by the third determination step, and a notification step for notifying the user of the overlap It is characterized by providing.

  Further, the present invention resides in a program for causing an information processing apparatus to execute the above information processing method, and a storage medium storing the program.

  According to the present invention, when the encoded image data and the stamp image data are set at the same time, the printing process is stopped when it is detected that the encoded image data is damaged. Alternatively, the user is notified using a user interface or the like, and the printing process is performed without combining the stamp image data.

  Further, when it is detected that the encoded image data is damaged, the printing process is performed so that the encoded image data is not damaged by automatically shifting the printing position of the stamp image data or reducing the size of the stamp image data. be able to.

  Hereinafter, embodiments to which the present invention can be applied will be described in detail with reference to the drawings.

  1 to 18 illustrate an image forming system including an information processing apparatus (host computer 3000) and an image forming apparatus (printer 1500) according to an embodiment of the present invention. FIGS. 1 to 18 illustrate a configuration relating to a printing process in the image forming system, and a method for generating / combining encoded image data and stamp image data associated therewith.

(First embodiment)
<Configuration of printing system>
FIG. 1 is a block diagram showing a configuration of an image forming system according to the first embodiment of the present invention. As long as the functions of the present invention are executed, processing is performed by connecting via a network such as a LAN / WAN, regardless of whether the system is composed of a single device or a system composed of a plurality of devices. It may be a system in which is performed.

  In FIG. 1, a host computer 3000 and a printer 1500 are connected by a bidirectional interface 21.

  The host computer 3000 includes a control unit 2000, a keyboard (KB) 9, a CRT display (CRT) 10, and an external memory 11.

  Further, the control unit 2000 includes a CPU 1, a RAM 2, a ROM 3, a system bus 4, a keyboard controller (KBC) 5, a CRT controller (CRTC) 6, a disk controller (DKC) 7, and a printer controller (PRTC) 8.

  The CPU 1, RAM 2, ROM 3, keyboard controller (KBC) 5, CRT controller (CRTC) 6, disk controller (DKC) 7, and printer controller (PRTC) 8 are connected via a system bus 4.

  The ROM 3 further includes a font ROM, a program ROM, and a data ROM therein.

  On the other hand, the printer 1500 includes a control unit 1000, a printing unit (printer engine) 17, an operation unit 1501, and an external memory 14.

  Further, the control unit 1000 includes a CPU 12, a ROM 13, a system bus 15, a printing unit interface (I / F) 16, an input unit 18, a RAM 19, and a memory controller (MC) 20.

  The CPU 12, the ROM 13, the printing unit interface (I / F) 16, the input unit 18, the RAM 19, and the memory controller (MC) 20 are connected via a system bus 15.

  Like the ROM 3, the ROM 13 further includes a font ROM, a program ROM, and a data ROM.

Each component in FIG. 1 will be described in detail.
First, each component included in the host computer 3000 of FIG. 1 will be described.

  The CPU 1 controls the entire host computer 3000 and executes document processing including a graphic, an image, a character, a table (including a spreadsheet), and the like including processing according to the embodiment of the present invention, and print processing based on the document processing. To control. The processing is performed based on a program ROM stored in the ROM 3 or a document processing program stored in the external memory 11. The processing according to the embodiment of the present invention will be described in detail with reference to FIG. In addition, the CPU 1 comprehensively controls each device connected via the system bus 4.

  The RAM 2 functions as a main memory and work area for the CPU 1. As will be described later, various data according to the embodiment of the present invention is stored on the RAM 2 or various programs are loaded on the RAM 2 and executed.

  The font ROM, program ROM, and data ROM included in the ROM 3 will be described.

  The program ROM stores an operating system (hereinafter referred to as OS) that is a control program of the CPU 1.

  The font ROM stores font data used for the document processing.

  The data ROM stores various data used when performing the document processing or the like.

  The font ROM, the program ROM, and the data ROM may exist in the ROM 3, but may be an embodiment that exists in the external memory 11.

  A keyboard controller (KBC) 5 controls key input from a keyboard (KB) 9 or a pointing device (not shown).

  A CRT controller (CRTC) 6 controls display on a CRT display (CRT) 10.

  A disk controller (DKC) 7 controls access to an external memory 11 such as a hard disk (HD) and a floppy (registered trademark) disk (FD). The external memory 11 such as HD and FD stores a boot program, various applications, font data, user files, editing files, a printer control command generation program (hereinafter referred to as a printer driver), and the like. Here, HD and FD are given as examples of the external memory 11, but the present invention is not limited to these, and any recording medium such as a CD-ROM may be used.

  The printer controller (PRTC) 8 is connected to the printer 1500 via the bidirectional interface 21 and executes communication control processing with the printer 1500.

  For example, the CPU 1 executes an outline font rasterization process on the display information set on the RAM 2 to enable WYSIWYG (wizig wig) on the CRT 10.

  Further, the CPU 1 opens various registered windows and executes various data processing based on commands instructed by a mouse cursor (not shown) or the like on the CRT 10. For this reason, when executing printing, the user can open a window regarding print settings and set the print processing method for the printer driver, including printer settings and print mode selection.

  Next, each component provided in the printer 1500 of FIG. 1 will be described.

  The CPU 12 controls the entire printer 1500 and controls each device connected to the system bus 15 based on a control program stored in the program ROM of the ROM 13 or a control program stored in the external memory 14. . For example, the CPU 12 outputs an image signal as print output information to the printing unit (printer engine) 17 via the printing unit I / F 16.

  The font ROM, program ROM, and data ROM included in the ROM 13 will be described.

  The program ROM stores a control program for the CPU 12 and the like.

  The font ROM stores font data used when generating the print output information.

  The data ROM stores information used on the printer 1500.

  The font ROM, the program ROM, and the data ROM may exist in the ROM 13, but may be an embodiment that exists in the external memory 14.

  Further, the CPU 12 can also control communication processing with the host computer 3000 via the input unit 18 and the bidirectional interface 21, and can transmit information in the printer 1500 to the host computer 3000.

  The RAM 19 is a memory that functions as a main memory of the CPU 12, a work area, and the like, and is configured such that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown). The RAM 19 is used as an output information expansion area, an environment data storage area, an NVRAM (Non Volatile RAM), and the like.

  The external memory 14 is accessed via a memory controller (MC) 20 and is controlled by the CPU 12. The external memory 14 is connected as an option and stores font data, an emulation program, form data, and the like.

  Further, the number of external memories 14 is not limited to one, and a plurality of external memories 14 may be provided. That is, the printer 1500 may be configured to be able to connect a plurality of external memories 14 that store an option card and a program for interpreting printer control languages of different language systems in addition to the built-in font. Further, the printer 1500 may include an NVRAM (not shown) and store printer mode setting information from the operation unit 1501.

  In FIG. 1, the external memory 14 is illustrated as an example of a storage medium such as a hard disk (HD) and a floppy (registered trademark) disk (FD). Other storage media such as a ROM may be used.

  In this embodiment, the printing unit 17 includes an electrophotographic engine. Therefore, the printing of the image and the accompanying copy-forgery-inhibited pattern image are performed by toner dots formed according to the print data. It should be noted that the printing method applicable to the present invention is not limited to such an electrophotographic method, and other printing methods that perform printing by forming ink dots, such as an ink jet method. The present invention can be applied.

  The input unit 18 is an operation panel, on which switches for operation, an LED display, and the like are arranged.

  FIG. 2 shows an example of a configuration for print processing in the host computer 3000 shown in FIG.

  In FIG. 2, the external memory 11 is omitted for convenience of explanation, but the application 201, the graphic engine 202, the printer driver 203, and the system spooler 204 exist as files stored in the external memory 11. The application 201, the graphic engine 202, the printer driver 203, and the system spooler 204 are program modules, which are loaded into the RAM 2 and executed by the modules that use the OS and OS modules when executed.

  Further, the application 201 and the printer driver 203 can be added to the HD of the external memory 11 via the FD or CD-ROM (not shown) of the external memory 11 or a network (not shown).

  The application 201 is loaded into the RAM 2 and executed. When printing to the printer 1500, the application 201 outputs a GDI (Graphic Device Interface) function to the graphic engine 202 that is similarly loaded into the RAM 2 and can be executed.

  The graphic engine 202 loads the printer driver 203 prepared for each image forming apparatus such as the printer 1500 from the external memory 11 to the RAM 2. The graphic engine 202 converts the GDI function received from the application 201 into a DDI (Device Driver Interface) function, and outputs the DDI function to the printer driver 203.

  The printer driver 203 converts the DDI function received from the graphic engine 202 into a control command that can be recognized by the printer 1500, for example, PDL (Page Description Language). The converted control command is transmitted as print data to the printer 1500 via the bidirectional interface 21 via the system spooler 204 loaded into the RAM 2 by the OS.

  Here, the application 201 shown in the present embodiment is an application that generates encoded image data and synthesizes it with document image data.

<Printing-related software module>
FIG. 3 is a diagram illustrating another example of a configuration for print processing in the host computer 3000.

  FIG. 3 is an extension of the configuration shown in FIG. 2, and shows a configuration in which a spool file 303 consisting of intermediate code is temporarily generated while a print command is sent from the graphic engine 202 to the printer driver 203.

  As in FIG. 2, the external memory 11 is omitted in FIG. 3 for convenience of explanation, but each component shown in FIG. 3 is stored in the external memory 11.

  The host computer 3000 includes an application 201, a graphic engine 202, a printer driver 203, a system spooler 204, a dispatcher 301, a spooler 302, and a spool file 303 in the external memory 11. The host computer 3000 includes a spool file manager 304, a despooler 305, a previewer 306, and a setting change editor 307 in the external memory 11. Further, the spool file manager 304 includes an encoded image detection unit 308 and a stamp image processing unit 309 therein.

  Differences between the configurations shown in FIGS. 2 and 3 will be described first.

  In the configuration of FIG. 2, the application 201 is released from the printing process when the printer driver 203 has converted all print commands received from the graphic engine 202 into control commands that can be recognized by the printer 1500.

  On the other hand, the configuration shown in FIG. 3 is different in that the application 201 is released from the printing process when the spooler 302 converts all print commands into intermediate code data and outputs them to the spool file 303.

  Usually, the latter (configuration shown in FIG. 3) requires a shorter printing process by the application 201.

  In the configuration shown in FIG. 3, the contents of the spool file 303 can be processed. As a result, functions that the application 201 itself does not have, such as an enlargement / reduction function or a function of reducing a plurality of pages into one page and printing the original image data received from the application 201 can be realized.

  In order to realize these things, the system is extended to spool the file consisting of the intermediate code data as shown in FIG. 3 with respect to the configuration of FIG.

  In order to process the document image data, the printer driver 203 normally performs settings from a window (not shown) displayed on the CRT display (CRT) 10. The printer driver 203 stores the contents set from the window in the RAM 2 or the external memory 11.

  Hereinafter, the configuration shown in FIG. 3 will be described in detail.

  As shown in FIG. 3, the dispatcher 301 receives a print command (DDI function) from the graphic engine 202. When the print command (DDI function) is converted based on the print command (GDI function) output from the application 201 to the graphic engine 202, the print command is different from the route described in FIG. (DDI function) is transmitted. That is, the dispatcher 301 loads the spooler 302 into the RAM 2 and transmits the print command (DDI function) to the spooler 302 instead of the printer driver 203.

  The spooler 302 analyzes the received print command (DDI function) and outputs a spool file converted into an intermediate code for each page to the spool file 303. Note that the spool file of the intermediate code stored in units of pages is referred to as a “page drawing file (PDF)” in this specification.

  Further, the spooler 302 acquires a “job setting file (SDF: Spool Description File)” from the printer driver 203 and stores the job setting file in the spool file 303 as a file for each job.

  In this specification, the “job setting file” means a file set for the printer driver 203 by the application 201. More specifically, the file is a file in which processing settings (Nup, double-sided, staple, color / monochrome, stamp image data designation, etc.) relating to printing of document image data are collected in units of jobs. This job setting file will be described later.

  The spool file 303 is generated as a file on the external memory 11 in this embodiment, but may be generated on the RAM 2.

  Further, the spooler 302 loads the spool file manager 304 into the RAM 2 and transmits the generation status of the spool file 303 to the spool file manager 304.

  Thereafter, the spool file manager 304 determines whether printing can be performed in accordance with the contents of the processing settings stored in the spool file 303. At that time, the encoded image detection unit 308 decodes the encoded image data of the document image data, and as a result, detects the presence of the encoded image data. When the encoded image data is detected, the encoded image detection unit 308 stores the drawing position of the encoded image data in the document image data in the RAM 2.

  On the other hand, the stamp image processing unit 309 determines whether or not a later-described stamp image data drawing process can be performed and a drawing position based on the drawing position of the encoded image data and the position where the stamp image data is drawn.

  If the spool file manager 304 determines that printing can be performed using the graphic engine 202 as a result of the determination, the spool file manager 304 loads the despooler 305 into the RAM 2. Then, the spool file manager 304 instructs (notifies) the despooler 305 to perform print processing of the page drawing file (PDF) stored in the spool file 303.

  The despooler 305 processes the page drawing file stored in the spool file 303 according to the job setting file (SDF) including the processing setting information stored in the spool file 303, and regenerates the print command (GDI function). To do. Then, the despooler 305 transmits the print command (GDI function) to the graphic engine 202. At this time, for the drawing position of the stamp image data, the despooler 305 loads the stamp image processing unit 309 to acquire the drawing position information, and performs the drawing process according to the information.

  The print command (GDI function) transmitted from the despooler 305 to the graphic engine 202 is converted into a print command (DDI function) by the graphic engine 202 and transmitted to the dispatcher 301.

  In such a case, the dispatcher 301 transmits a print command (DDI function) to the printer driver 203 instead of the spooler 302.

  That is, when the print command (DDI function) received from the graphic engine 202 is the print command (DDI function) received from the despooler 305, the dispatcher 301 transmits the print command (DDI function) to the printer driver 203. To do. On the other hand, as described above, when the print command (DDI function) received from the graphic engine 202 is the print command (GDI function) received from the application 201, the dispatcher 301 sends the print command (DDI) to the spooler 302. Function).

  The printer driver 203 generates a printer control command including PDL (page description language) based on the print command (DDI function) received from the dispatcher 301, and transmits the printer control command to the printer 1500 via the system spooler 204.

  In addition to the above-described configuration, FIG. 3 further includes a previewer 306 and a setting change editor 307, which enables print preview including a preview of stamp image data, print setting change, and combination of multiple jobs. An example is shown.

  In order to perform print preview, print setting change, and combination of a plurality of jobs, first, in a property sheet (not shown) of the printer driver 203, a pull-down menu (not shown) for “designating an output destination” is used. It is necessary to specify "Store". If only the print preview is desired, it is also possible to select “Preview” as the output destination designation.

  The contents set in the property sheet of the printer driver 203 are stored as a setting file in a structure provided by the OS (called DEVMODE in the Windows (registered trademark) OS). The structure includes, for example, a setting for whether or not the spool file manager 304 performs the store in a job setting file including processing setting information. When the spool file manager 304 reads the processing settings via the printer driver and stores are specified, a page drawing file (PDF) and a job setting file (SDF) are generated in the spool file 303 as described above. -Stored. Then, the spool file manager 304 pops up a window screen (not shown) of the spool file manager 304 and displays a list of jobs spooled in the spool file 303.

  When a preview of a single job or a combined job is designated on the window screen of the spool file manager 304, the spool file manager 304 loads the previewer 306 into the RAM 2. Then, the spool file manager 304 instructs the previewer 306 to perform a preview process of the page drawing file (PDF) stored in the spool file 303.

(Previewer)
Here, the previewer 306 will be described in detail.
The previewer 306 sequentially reads the page drawing file (PDF) stored in the spool file 303 and processes it according to the content of the processing setting information included in the job setting file (SDF) stored in the spool file 303. Then, with respect to the processed preview information, the previewer 306 transmits drawing data (substantially a GDI function) to the graphic engine 202 via the spool file manager 304. When the graphic engine 202 outputs the received drawing data to the client area secured by the graphic engine 202, it is possible to output a preview on the screen.

  The graphic engine 202 can perform appropriate rendering according to the designated output destination. From this, the previewer 306 processes the page drawing file (PDF) stored in the spool file 303 in accordance with the processing setting contents of the job setting file (SDF) stored in the spool file 303, similarly to the despooler 305. be able to. The previewer 306 can realize a preview by outputting a preview processed using the graphic engine 202. As described above, the previewer 306 stores the processing settings set by the printer driver 203 in the spool file 303 as a job setting file (SDF), and generates a page drawing file (PDF) based on the job setting file (SDF). Process and output data.

  Since the preview function of general application software is drawn based on the page setting in the application, the print setting of the printer driver is not reflected, and the user cannot recognize the preview that is actually output.

  On the other hand, the present invention can provide the user with how the actual drawing data is printed by the above-described processing. Furthermore, when Nup, double-sided printing, bookbinding printing, and stamp image data are designated, the present invention can provide the user with a print preview that is close to that output by the printer. Note that Nup indicates a process of printing N pages of logical pages in a reduced arrangement on one physical page.

  By performing the preview process as described above, a preview based on the print processing setting included in the spool file 303 is displayed on the screen by the previewer 306.

  When the previewer 306 is closed by a user non-display instruction, control is transferred to a window screen (not shown) of the spool file manager 304. When the user performs printing according to the contents displayed by the previewer 306, the spool file manager 304 issues a print request by instructing “print” or “save and print” on the spool file manager 304. . In response to this print request, the despooler 305 generates a GDI function by processing the page drawing file (PDF) based on the job setting file (SDF) and transmits the GDI function to the graphic engine 202 as described above. A print command (DDI function) is transmitted from the graphic engine 202 to the printer driver 203 via the dispatcher 301, and printing is executed.

(Setting change editor)
Next, setting change using the setting change editor 307 will be described. In the setting change editor 307, as with the preview described above, the setting can be changed for a job designated as “Store”.

  First, the spool file manager 304 pops up a window screen (not shown) of the spool file manager 304 in the same procedure as the preview, and displays a list of jobs spooled in the spool file 303. When “job editing” is selected on the window screen of the spool file manager 304 and a setting change instruction is given, the spool file manager 304 loads the setting change editor 307 into the RAM 2. Then, the spool file manager 304 instructs the setting change editor 307 to display the current or default processing settings. Then, the setting change editor 307 displays a job setting screen.

  The setting change editor 307 acquires a job setting file (SDF) of a job for which “job editing” is specified from the spool file 303, and sets the job setting screen based on the setting items specified in the job setting file (SDF). Change the default value of. This setting change editor 307 can also output a preview on the screen. That is, the setting change editor 307 processes the page drawing file (PDF) of the intermediate code included in the spool file 303 according to the contents of the processing setting included in the job setting file (SDF) stored in the spool file 303. After processing, the setting change editor 307 can output a preview on the screen by outputting it to the memory using the graphic engine 202.

  The setting change editor 307 can change the contents of the processing settings included in the job setting file (SDF) stored in the spool file 303. In such a case, the user interface of the setting change editor 307 may be configured to have items that can be set by the printer driver 203, or may be configured to call up the user interface of the printer driver 203 itself. In the setting change editor 307, the number of copies, printing method (single side, double side, bookbinding printing), staple (saddle finisher, etc.), page layout, arrangement order, etc. can be specified. The setting change editor 307 can also reset the detailed setting items that can be specified by the printer driver 203.

  The change item changed in the setting change editor 307 is transferred to the spool file manager 304 when the change is authenticated in accordance with the authentication request on the setting change editor 307. The spool file manager 304 stores the item whose change has been authenticated as print setting change information. At this time, the spool file manager 304 does not store the item in the original job setting file (SDF). Create a new file and store it. Details of the job output setting file will be described later with reference to FIG.

  When the user performs printing according to the setting change content after confirmation by the previewer 306, the spool file manager 304 reads the job output setting file and issues a print request. The print request is transmitted to the graphic engine 202 via the despooler 305. Thereafter, the print request is transmitted from the graphic engine 202 to the printer driver 203 via the dispatcher 301, and printing according to the setting change content is executed.

  Also, on the window screen (not shown) of the spool file manager 304, it is possible to combine a plurality of print jobs and specify printing as one print job. Similar to the preview and setting change described above, this combining process can be performed for a job whose output destination is designated as “store” in the property sheet (not shown) of the printer driver 203. Also, functions such as a mailbox and secure print can be selected by designating “mailbox” and “secure print” in a menu (not shown) designated “store”.

  When a user combines print jobs, first, the printer driver 203 is called from the application 201, and a store is selected from a user interface (not shown). Similar to the above, the intermediate code data (page drawing file) is stored in the spool file 303 by this selection, and the spool file manager 304 pops up the window screen of the spool file manager 304. Then, the spool file manager 304 displays a list of jobs spooled in the spool file 303 on the window screen of the spool file manager 304. A plurality of job lists can be displayed on the spool file manager 304 by performing the same operation as described above from the application 201.

  Here, when multiple jobs are selected and “join” is designated, the spool file manager 304 loads the setting change editor 307 stored in the external memory 11 into the RAM 2 and executes it. When the user instructs to display the first job on the list or the default processing setting via the setting change editor 307, a combination setting screen (not shown) is displayed. Here, the setting change editor 307 has been described as the combination setting screen, but a setting screen of another module may be used.

  The setting change editor 307 processes the page drawing file (PDF) stored in the spool file 303 according to the contents of the processing settings included in the job setting file (SDF) stored in the spool file 303. Thereafter, the setting change editor 307 performs screen output by outputting all jobs designated as combined jobs to the memory using the graphic engine 202. At that time, all jobs selected in the preview area can be previewed. When generating a combined job, a job output setting file is generated by expanding the job setting file (SDF) of each single job. This job output setting file is also generated when job editing is performed. One job output setting file is generated for one job, and one job is also generated for a combined job.

  Here, each job can be displayed with the processing setting before combining, or can be changed to a unified processing setting and displayed as a combined job. At this time, items that can be set by the printer driver 203 may be set by the user interface of the setting change editor 307, or may be set by calling the user interface of the printer driver 203 itself.

  As described above, when the combined job and the changed change item are authenticated according to the authentication request on the setting change editor 307, the control is transferred to the spool file manager 304. By this operation, the plurality of jobs selected previously are displayed as one combined job on the spool file manager 304 window.

  When the user performs printing according to the setting change content, as in the confirmation by the previewer 306, the spool file manager 304 issues a print request. The issued print request is transmitted to the graphic engine 202. The graphic engine 202 converts the print request into a DDI function, transmits the converted print command to the printer driver 203 via the dispatcher 301, and performs printing according to the print command.

  FIG. 4 is a diagram showing a configuration related to the application 201 in the present invention. The application 201 generates encoded image data, and synthesizes the generated encoded image data and document image data.

  The application 201 includes an application control unit 401, a driver call unit 402, a code image generation unit 403, a code image synthesis unit 404, a print file reading unit 405, an encoded data file reading unit 406, and a file I / O unit 407.

  The application control unit 401 controls each unit in the application 201 in an integrated manner. When there is an execution command from each part of the user interface 500 of the application 201 to be described later, the application control unit 401 receives the command and issues an instruction to each part in FIG. That is, as shown in FIG. 4, the application control unit 401 issues an instruction to the driver call unit 402, the code image generation unit 403, the print file reading unit 405, and the encoded data file reading unit 406.

<Encoding process>
The CPU 1 performs control to perform encoding processing of predetermined information (the predetermined information includes, for example, a device number, printing time information, user ID information, and the like) to generate encoded image data. Is possible.

  In this specification, “encoded image data” refers to an image such as a two-dimensional code image or a barcode image, or a digital watermark image generated by a digital watermark technique.

  The above control (code image generation control, transmission control) is performed by the CPU 1 executing a program stored in the RAM 2.

  A driver call unit 402 calls the printer driver 203 to perform print settings such as designation of stamp image data.

  The code image generation unit 403 generates encoded image data and transmits it to the code image synthesis unit 404. The code image combining unit 404 combines the encoded image data with the document image data.

  A print file reading unit 405 reads a file to be printed and develops it in the RAM 2.

  The encoded data file reading unit 406 reads the data that has been encoded and combined with the document image data as a file, and develops it in the RAM 2.

  The file I / O unit 407 opens the file read by the print file reading unit 405 and the encoded data file reading unit 406 and develops the data in the RAM 2.

  FIG. 5 is an example of an operation screen of the user interface 500 of the application 201. As described above, since the application 201 is controlled by the application control unit 401, the application control unit 401 also controls the user interface 500.

  The user interface 500 includes a print image display area 501, a composite image display area 502, a print file read button 503, an encoded data read button 504, a print setting button 505, a print start button 506, and a close button 507.

  Hereinafter, each component of the user interface 500 will be described.

  When the application control unit 401 detects that the print file reading button 503 is pressed, it reads the document image data and displays the read document image data in the print image display area 501.

  When the application control unit 401 detects that the encoded data reading button 504 is pressed, the application control unit 401 reads the data file to be encoded, and an image obtained by combining the encoded image data with the document image data is displayed in the combined image display area 502. indicate.

  When the print setting button 505 is pressed, the driver calling unit 402 calls the printer driver 203 and displays a print setting user interface of the printer driver 203 described later (see FIG. 6).

  When the printing start button 506 is pressed to start printing, the graphic engine 202 loads the printer driver 203 prepared for each image forming apparatus such as the printer 1500 from the external memory 11 to the RAM 2. Then, the graphic engine 202 sets the output from the application 201 in the printer driver 203.

  When the close button 507 is pressed, the user interface 500 is closed.

  FIG. 6 is an example of a print setting user interface of the printer driver 203, and the stamp image data is designated by this user interface. As the stamp image data, items to be set as stamp image data such as “secret” and “copy prohibited” can be selected from a pull-down menu.

<Storage processing of intermediate data for printing>
FIG. 7 is a flowchart showing the processing of the page unit storage step in generating the spool file 303, which is executed by the spooler 302. Hereinafter, processing in each step will be described.

  In step S <b> 701, the spooler 302 receives a print request from the application 201 via the graphic engine 202 and the dispatcher 301.

  In the application 201, a dialog for inputting print settings as shown in FIG. 6 is displayed, and the print settings input from this dialog are also passed from the printer driver 203 to the spooler 302. This print setting is the above-described job setting file (SDF). For example, the setting input dialog shown in FIG. 6 includes setting items for determining whether or not to print stamp image data, such as a “stamp” check box. Such print settings are transferred from the printer driver 203 to the spooler 302.

  In step S702, the spooler 302 determines whether the received print request is a job start request. If it is determined that the request is a job start request, the process proceeds to step S703. On the other hand, the spooler 302 determines that the request is not a job start request. In this case, the process proceeds to step S706.

  First, the processing flow that proceeds to step S703 will be described.

  In step S703, the spooler 302 creates a spool file 303 for temporarily storing intermediate data.

  In step S704, the spooler 302 notifies the spool file manager 304 of the progress of the printing process.

  In step S705, the spooler 302 initializes its own page number counter to 1.

  Note that the spool file manager 304 reads job information, processing settings, and the like for a job for which printing has started from the spool file 303 and stores it in the spool file manager 304.

  Next, the processing flow that proceeds to step S706 will be described.

  In step S706, it is determined whether the received request is a job end request. If it is determined that the request is a job end request, the process proceeds to step S712. If it is determined that the request is not a job end request, the process proceeds to step S707.

  First, the processing flow that proceeds to step S707 will be described.

  In step S707, the spooler 302 determines whether the received request is a page break. If it is determined in step S707 that the received request is a page break, the process advances to step S708, and the spooler 302 has received the progress of print processing, that is, a page break print request, to the spool file manager 304. To be notified. The spooler 302 increments (increments) the page number counter by 1, closes the page drawing file (PDF) storing the intermediate code, and generates the next page drawing file (PDF).

  On the other hand, if it is determined in step S707 that the received print request is not a page break, the process advances to step S709 to prepare for writing the intermediate code to the page drawing file (PDF).

  Next, in step S710, the spooler 302 performs processing for converting the print request into an intermediate code in order to store the print request in the spool file 303.

  In step S <b> 711, the spooler 302 writes the print request converted into the form that can be stored in step S <b> 710, that is, the intermediate code into the page drawing file (PDF) of the spool file 303.

  Thereafter, the process returns to step S701, and the spooler 302 receives the print request from the application 201 again.

  The spooler 302 continues the series of processing from step S701 to step S711 until a job end request (EndDoc) is received from the application 201.

  Further, the spooler 302 acquires information such as processing settings stored in the DEVMODE structure from the printer driver 203 during the above-described series of processing, and stores the information in the spool file 303 as a job setting file (SDF).

  Next, a processing flow in which it is determined in step S706 that the print request from the application is a job end and the process proceeds to step S712 will be described.

  In this case, since all print requests from the application 201 are completed, the process advances to step S712, and the spooler 302 notifies the spool file manager 304 of the progress of the printing process and ends the process.

<Generate spool file>
FIG. 8 is a flowchart showing details of control between the spool file 303 generation process and the print data generation process described below, which is executed by the spool file manager 304.

  In step S <b> 801, the spool file manager 304 receives a print processing progress notification from the spooler 302 or the despooler 305.

  In step S802, the spool file manager 304 determines whether the progress notification is a print start notification from the spooler 302 notified in step S704 described above. If the progress notification is a print start notification from the spooler 302, the process advances to step S803 to read print processing settings (stamp image data settings, etc.) from the spool file 303, and start job management. Thereafter, in step S816, the spool file manager 304 sets stamp image data described later.

  On the other hand, if the spool file manager 304 determines in step S802 that the progress notification is not a print start notification from the spooler 302, the process advances to step S804. In step S804, the spool file manager 304 determines whether or not the progress notification is a print end notification of one logical page from the spooler 302 notified in the above-described step S708, that is, a page break notification. If it is a print end notification for one logical page, the spool file manager 304 sets stamp image data, which will be described later, in step S817, and stores logical page information related to this logical page in the RAM 2 in step S805.

  In subsequent step S806, the spool file manager 304 determines whether printing of one physical page can be started with respect to the n logical pages for which spooling has been completed at this time. If it is determined that printing is possible, the process advances to step S807, and the spool file manager 304 determines the physical page number from the logical number assigned to one physical page to be printed.

  The calculation of the physical page is performed as follows.

  For example, when the processing setting is such that four logical pages are arranged on one physical page, the first physical page can be printed when the first to fourth logical pages are spooled. Subsequently, the second physical page can be printed when the fifth to eighth logical pages are spooled.

  Even if the total number of logical pages is not a multiple of the number of logical pages allocated to one physical page, the logical page to be allocated to one physical page can be determined by the spool end notification in step S712.

  In step S808, the spool file manager 304 stores the physical page information in a job output setting file (a file including physical page information). That is, in the format shown in FIG. 10, information such as the logical page number constituting the printable physical page and the physical page number is stored in the job output setting file. Thereafter, the spool file manager 304 notifies the despooler 305 that one physical page of physical page information has been added.

  Thereafter, the process returns to step S801, and the spool file manager 304 waits for the next notification. In the present embodiment, even if the spooling of the print job is not completed, the printing process can be performed when one page of print data, that is, a logical page constituting one physical page is spooled.

  On the other hand, if the progress notification is not a print end notification of one logical page from the spooler 302 in step S804, the process proceeds to step S809. In step S809, the spool file manager 304 determines whether or not the progress notification is a job end notification from the spooler 302 notified in step S712.

  If it is determined that the job end notification is received from the spooler 302, the process proceeds to step S806 described above. Since the subsequent processing contents overlap with the above description, they are omitted.

  On the other hand, if it is determined that it is not a job end notification from the spooler 302, the process advances to step S810, and the spool file manager 304 determines whether or not the progress notification is a print end notification of one physical page from the despooler 305. Determine.

  If it is determined in step S810 that it is a print end notification for one physical page, the process proceeds to step S811. In step S811, the spool file manager 304 determines whether printing for all the processing settings read from the spool file 303 in step S803 has been completed. When printing for all the processing settings is completed, the spool file manager 304 advances the process to step S812 to notify the despooler 305 of the completion of printing.

  On the other hand, if it is determined in step S811 that printing for the processing setting has not yet been completed, the process proceeds to step S806 described above.

  The despooler 305 in this embodiment assumes every physical page number as a unit for performing a printing process. In step S808, information necessary for performing printing processing of one physical page is sequentially stored in the job output setting file so that it can be reused. However, in the case where reuse is unnecessary, an embodiment may be used in which a high-speed medium such as a shared memory is used, and the medium is overwritten one after another in units of one physical page to save speed and resources. In addition, when the progress of the spooler 302 is faster than the progress of the despooler 305, or when the processing by the despooler 305 is started after the end of the processing by the spooler 302, processing different from the processing described above may be performed. . That is, the spool file manager 304 may perform notification according to the progress on the despooler 305 side without notifying that page printing is possible for each physical page in step S808. For example, if the spool file manager 304 notifies that a plurality of physical pages or all physical pages can be printed, the number of notifications can be saved.

  Here, it returns to step S810 and demonstrates.

  If it is determined that the progress notification is not a print end notification of one physical page from the despooler 305, the process proceeds to step S813. In step S813, the spool file manager 304 determines whether a print end notification is received from the despooler 305.

  On the other hand, if it is determined that the progress notification is a print end notification from the despooler 305, the process proceeds to step S814. Thereafter, the spool file manager 304 deletes the corresponding page drawing file (PDF) from the spool file 303 and ends the processing.

  On the other hand, if the print end notification is not received from the despooler 305, the process advances to step S815, and the spool file manager 304 executes error processing. Thereafter, other processing (not shown) is executed, and the next notification is awaited.

<Output spool file>
FIG. 9 is a flowchart showing details of a print command generation process executed by the despooler 305.

  In response to a print request from the spool file manager 304, the despooler 305 reads necessary information (page drawing file (PDF) and job setting file (SDF)) from the spool file 303 and generates a print command. The method for transmitting the generated print command to the printer 1500 is as described above with reference to FIG.

  In the generation of the print command, first, the notification from the spool file manager 304 is input to the despooler 305 in step S901.

  In subsequent step S902, the despooler 305 determines whether or not the input notification is a job end notification. If it is determined that the input is a job end notification, the process proceeds to step S903. In step S903, the despooler 305 sets an end flag on the RAM 2 (or the external memory 11). Thereafter, the process proceeds to step S905.

  On the other hand, if it is determined in step S902 that the input notification is not a job end notification, the process proceeds to step S904. In step S904, the despooler 305 determines whether the input notification is a request to start printing one physical page notified from the spool file manager 304 in step S808 described above.

  If it is determined in step S904 that the request is not a print start request, the process proceeds to step S910, the despooler 305 performs other error processing, returns to step S901, and waits for the next notification.

  On the other hand, if it is determined in step S904 that it is a request to start printing one physical page, the process proceeds to step S905, and the despooler 305 shows the ID of the physical page that can be printed, notified in step S904, as shown in FIG. Store in the job output setting file. The job output setting file will be described in detail with reference to FIG.

  In the subsequent step S906, the despooler 305 determines whether or not the printing process has been completed for all pages of the physical page ID stored in step S905. If it is determined that all physical pages have been processed, the process proceeds to step S907, and the despooler 305 determines whether or not the end flag is set.

  If it is determined in step S907 that the end flag is set, it is assumed that the job printing has ended, and the despooler 305 notifies the spool file manager 304 of the end of processing, and the processing ends.

  On the other hand, if it is determined in step S907 that the end flag is not set, the process returns to step S901 to wait for the next notification.

  If it is determined in step S906 that a printable physical page remains, the process proceeds to step S908.

  In step S908, the despooler 305 sequentially reads unprocessed physical page IDs from the stored physical page IDs. The despooler 305 reads information necessary for generating a physical page print command corresponding to the read physical page ID, and performs print processing. In the printing process, the despooler 305 converts the print request command stored in the spool file 303 into a format (GDI function) that can be recognized by the graphic engine 202 and transmits the converted print request command.

  For the processing setting (hereinafter, N-page printing) for laying out a plurality of logical pages on one physical page as in the present embodiment, conversion is performed in consideration of the reduced arrangement in step S908.

  When the necessary print processing is completed, the despooler 305 notifies the spool file manager 304 of the end of print command generation for one physical page in the subsequent step S909. Thereafter, the process returns to step S906 again, and the above process is repeated until the print process is performed for all printable physical page IDs stored in step S905.

  The above is the flow of print processing using the dispatcher 301, the spooler 302, the spool file manager 304, and the despooler 305.

  By performing the above processing, the application 201 is released from the printing process at the timing when the spooler 302 generates a page drawing file (PDF) and stores it in the spool file 303, so that it takes a shorter time than directly outputting to the printer driver 203. Just do it.

  Further, the spool file 303 is temporarily stored as an intermediate file (page drawing file (PDF), job setting file (SDF)) based on the print settings of the printer driver 203. Therefore, it is possible to allow the user to recognize an actual print image in a preview, and to combine and rearrange print jobs generated by a plurality of applications. Also, when changing the print settings, it is possible to allow the user to execute without starting up the application again and printing.

  Here, the job output setting file will be described.

  The job output setting file is generated at the time of a print request from the despooler 305 to the graphic engine 202 in the printing process using the spooler 302, but is also generated when previewing or job combination is performed. The job output setting file is equivalent to the job setting file (SDF) for a single job, and is generated based on a plurality of job setting information for a combined job.

<Configuration of job output setting file>
FIG. 10 shows an example of a job output setting file that stores information constituting the printable physical page generated by the spool file manager 304 in step S808.

  A field 1001 stores an ID for identifying a job. It is also possible to store the information in the form of a file name for storing this information or a shared memory name.

  A field 1002 stores job setting information. The job setting information includes information that can only be set for one job. For example, a structure necessary for starting printing of a job to the graphic engine 202, a color mode specification, an N page print specification, an additional drawing specification such as a page frame, the number of copies, a finishing specification such as stapling, etc. is there. The job setting information in the field 1002 stores as much information as necessary according to the function for the job.

  A field 1003 is the number of physical pages of the job, and indicates that this number of physical page information is stored after this field. Thereafter, the physical page information is stored in the number of fields 1003 from the field 1004 to the end. That is, the number after field 1004 is determined according to the number of physical page information stored in field 1003. For example, when the information that the number of physical pages of the job is “4” is stored in the field 1003, four fields are necessary. Therefore, the fourth physical page information that is the last physical page is the field 1007. Stored in

  In this embodiment, since the number of printable physical pages is notified, the operation is possible without this field.

  The physical page information will be described later with reference to FIG.

<Configuration of job setting information>
FIG. 11 shows an example of job setting information shown in the field 1002 of FIG.

  A field 1101 is the total number of physical pages. On the other hand, the field 1102 is the total number of logical pages. Fields 1101 and 1102 are used when printing by adding the number of pages as additional information to the print command. As printing continues, both fields have provisional values, or the spool file manager 304 postpones the creation of printable physical page information until printing ends.

  A field 1103 stores the number of copies information that specifies how many copies of the print job are to be printed.

  A field 1104 is a field for designating whether or not printing is to be performed in units of copies when the field 1103 is set to print a plurality of copies.

  A field 1105 is a field for storing finishing information such as stapling, punching, Z-folding, and the like, and is designated when a finisher exists in the printer main body or outside.

  The field 1106 contains additional print information, that is, information added to the job such as decoration of a page frame, additional information such as date, user name, number of pages, and the like, including printing of stamp image data of the present invention. The field to be stored. As the number of functions increases, the number of fields included in the job setting information increases. For example, when double-sided printing is possible, a field for storing designation of double-sided printing is added.

<Physical page information>
FIG. 12 shows an example of physical page information shown in the field 1004 of FIG.

  A field 1201 is a field in which a physical page number is stored, and the physical page number is a value used when managing the printing order and additionally printing the physical page number.

  A field 1202 stores physical page setting information. When layout or color / monochrome can be specified for each physical page, layout / color / monochrome setting information is stored.

  A field 1203 is a field for storing the number of logical pages to be allocated to the physical page. When 4 pages are allocated to one physical page, an ID indicating 4 or 4-page printing is stored.

  Fields 1204 and after are fields in which logical page information is stored in the number specified in the field 1203. Depending on the number of pages printed from the application 201, the actual number of page data may be smaller than the number of pages specified in the field 1203. In that case, special data (for example, NULL value) indicating an empty page is stored in the logical page information.

  FIG. 13 is a diagram illustrating an example of physical page setting information in the field 1202.

  A field 1301 is a field in which the order of arrangement of logical pages on a physical page is stored. For example, in N-page printing, the order of arrangement of logical pages on a physical page (from top left to side, top left to bottom, etc.) ) Is stored. Depending on the system, the setting of the field 1301 can be substituted by arranging the logical page information after the field 1204 in the order corresponding to the arrangement order instead of the page number order, instead of the arrangement order.

  A field 1302 is a field in which information on both sides of double-sided printing is stored, and is used, for example, when aligning binding margins on the front and back sides.

  A field 1303 is a field for indicating whether a color page or a monochrome page is specified. By using the field 1303, a color / monochrome mode can be specified for each physical page.

  A field 1304 stores additional print information, and is used when additional information such as the number of pages and date is printed on a physical page. In the physical page setting information, a field is added according to the function of the system.

  FIG. 14 is a diagram illustrating an example of the logical page information indicated in the field 1204.

  A field 1401 stores a logical page identification ID, and an intermediate code of a page drawing file (PDF) corresponding to the logical page can be referred to from the spool file 303 using the logical page identification ID. Note that it is only necessary that the intermediate code of the page drawing file (PDF) corresponding to the logical page can be accessed using the logical page identification ID. For this reason, the field 1401 may contain a file or memory pointer, or may contain the intermediate code itself constituting the logical page.

  A field 1402 is a field in which a logical page number is stored, and is used when the logical page number is printed as additional information or used as auxiliary information for the logical page ID.

  A field 1403 stores format information, and stores various setting items that can be specified in units of logical pages. For example, it stores additional print information such as page frames, and various setting information designated for each logical page such as an enlargement / reduction ratio. Further, if necessary, attribute information for a logical page such as color / monochrome information in units of logical pages can be stored. Note that the field 1403 is not necessary in a system that switches settings in units of logical pages, or in a system that does not require attribute information in units of logical pages.

  As described with reference to FIGS. 10 to 14, the job output setting file is configured as described above. Note that the job setting file (SDF) has almost the same configuration, and print format (single-sided, double-sided, bookbinding printing), print layout (Nup, poster printing), additional information (background print information, stamp, date, user name, etc.) ), The number of copies, and paper size information. The job setting file (SDF) includes a logical page arrangement order for each physical page, a front / back side for duplex printing, a color mode, and the like.

  Returning to FIG. 3, FIG. 3 shows an example in which a setting change editor 307 having a job setting change function is arranged in addition to the extended system described so far. In the present embodiment, the job setting contents are included in the job setting file (SDF) in the case of a single job, while in the job output setting file shown in FIG. 10 in the case of a combined job. Yes. That is, the job settings are independent of the spool file 303 that stores the page drawing file that is an intermediate code.

  For this reason, it is possible to change job settings by recreating a job output setting file. The setting change editor 307 implements a job setting change function by changing the job output setting file by itself or in cooperation with the spool file manager 304 or by rewriting a part thereof.

<Stamp image data setting>
FIG. 15 shows a flowchart in which the spool file manager 304 combines the stamp image data with the document image data. The spool file manager 304 is expanded in the RAM 2 and executed by the CPU 1.

  In step S1501, the spool file manager 304 determines whether or not stamp printing is designated in the processing settings read in step S803. If it is determined that there is a designation, the process proceeds to step S1502. Conversely, if it is determined that there is no designation, the process proceeds to step S1505.

  In step S1502, the encoded image detection unit 308 in the spool file manager 304 decodes (decodes) the encoded image data of the document image data, and detects whether the encoded image data is included in the document image data. . If it is determined in step S1502 that the encoded image data is not included, the process proceeds to step S1504, and the document image data not including the encoded image data is combined with the stamp. On the other hand, if it is determined in step S1502 that the encoded image data is included, the process proceeds to step S1503.

  In step S1503, the encoded image detection unit 308 acquires the drawing position of the detected encoded image data, and stores the acquired drawing position in the RAM 2. At the same time, the spool file manager 304 acquires the drawing position of the stamp image data included in the processing setting, and stores the acquired drawing position in the RAM 2. The spool file manager 304 determines whether there is an overlap area between the drawing position of the encoded image data stored in the RAM 2 and the drawing position of the stamp image data, that is, whether the encoded image data and the stamp image data overlap. Determine. In step S1503, if the encoded image detection unit 308 determines that the encoded image data and the stamp image data do not overlap, the process proceeds to step S1504, and the original image data including the stamp image data and the encoded image data. Are sent to the printer as print data. That is, the stamp image data and the document image data are transmitted to the printer as print data so that the stamp image data and the document image data are combined by the printer. Thereafter, the printer synthesizes the original image data and the stamp image data received as print data and forms them on the sheet. On the other hand, if the encoded image detection unit 308 determines in step S1503 that the encoded image data and the stamp image data overlap, the process proceeds to step S1506, and the process of interrupting printing (for the user) Notification to interrupt printing), and print data is not sent to the printer.

(Second Embodiment)
The processing in step S1506 in the flowchart of FIG. 15 is different between the first embodiment and the second embodiment. Therefore, step S1506 will be described.

  In step S1503, when the encoded image detection unit 308 determines that the encoded image data is duplicated, the process proceeds to step S1506. In step S1506, the user is notified of the presence of the encoded image data using the user interface of the application 201, and only the document image data is transmitted to the printer as print data. At this time, since only the document image data is transmitted as print data and the encoded image data is not transmitted, the printer forms only the document image data on the sheet.

  For this reason, the stamp image data is not combined with the encoded image data. Therefore, the encoded image data can be transmitted to the printer as print data without damaging the encoded image data. Can be known from the notification.

  In the present embodiment, the embodiment is described in which the notification is performed and the printing process is performed without compositing the stamp image data. However, the embodiment may be an embodiment in which the notification is notified and the printing process is stopped.

(Third embodiment)
FIG. 17 illustrates an embodiment in setting stamp image data. FIG. 17 is a diagram visually showing an image of processing when the encoded image data and the stamp image data are combined. When the stamp image data is shifted, the stamp image data is reduced in size from the original image data. It is the figure which showed the process in the case of protruding.

  Reference numeral 1701 is document image data in which encoded image data exists, and reference numeral 1702 is stamp image data. When the stamp image data of the reference numeral 1702 is directly combined with the original image data of the reference numeral 1701, the stamp image data and the encoded image data overlap as in the drawing data of the reference numeral 1703.

  In this case, the stamp image data is stamped at a position shifted from the area where the encoded image data is drawn on the document image data to the non-overlapping distance in the widest area other than the encoded image data as indicated by reference numeral 1704. Draw image data. However, as indicated by reference numeral 1704, there may be a case where there is no region where the stamp image data can be drawn (the stamp image data protrudes from the document image data). In such a case, the size of the stamp image data is reduced by N% at the drawing position initially specified in the processing settings, and as indicated by reference numeral 1705, the stamp image data is reduced to a size that does not overlap each other. .

  The object of the present embodiment is to prevent the encoded image data from being damaged when the stamp image data is synthesized. For this reason, when the stamp image data and the encoded image data overlap as shown by reference numeral 1703, a warning display may be notified to the user using the user interface, and the stamp image may be set again. Further, when stamp image data and encoded image data overlap as shown by reference numeral 1703, a warning display may be notified to the user using the user interface, and the printing process may be stopped.

  FIG. 18 is a flowchart for explaining an embodiment of the stamp image data setting shown in FIG. 17, and is a flowchart in which the spool file manager 304 combines the stamp image data with the document image data. The spool file manager 304 is expanded in the RAM 2 and executed by the CPU 1.

  In step S1801, the spool file manager 304 determines whether or not stamp image data printing is specified in the processing settings read in step S803. If it is determined that there is a print designation for stamp image data, the process proceeds to step S1802. On the other hand, if it is determined that there is no designation, the process ends.

  In step S1802, the encoded image detection unit 308 in the spool file manager 304 detects whether or not encoded image data is included in the document image data.

  If it is determined in step S1803 that there is encoded image data, the process proceeds to step S1804. If it is determined that there is no encoded image data, the process ends.

  In step S1804, the encoded image detection unit 308 decodes the encoded image data of the document image data, and detects the drawing position of the encoded image data.

  In step S1805, the spool file manager 304 acquires the drawing position of the stamp image data from the processing setting.

  In step S1806, the stamp image processing unit 309 in the spool file manager 304 determines whether the drawing position of the encoded image data and the drawing position of the stamp image data overlap.

  If it is determined in step S1806 that the drawing positions overlap, the process proceeds to step S1807. On the other hand, if it is determined that the drawing positions do not overlap, the process ends.

  In step S 1807, the stamp image processing unit 309 shifts the stamp image data from the area where the encoded image data is drawn on the document image data to the distance where the area other than the encoded image data is widest so as not to overlap. I do.

  In step S1808, it is determined whether or not the drawing position from which the stamp image data has been shifted falls within the area indicated by the document image data (that is, whether or not the drawing position protrudes from the document image data). If the result of this determination is that it fits as indicated by reference numeral 1604 in FIG. 16, printing is executed and the process is terminated. If not, the process proceeds to step S1809.

  In step S1809, the size of the stamp image data is reduced by N% based on the drawing position first obtained from the processing setting, and the drawing position of the encoded image data and the drawing position of the stamp image data do not overlap. The stamp image data is reduced until. It should be noted that the numerical value of N% is determined in advance, and after performing the reduction process, the process returns to step S1808 again, and after making the above determination, the process in step S1809 may be performed again. .

  When the above processing is completed, the reduced stamp (or not reduced as shown in FIG. 16) and the original image data including the encoded image data are transmitted to the printer as print data. That is, the stamp and the document image data are transmitted to the printer as print data so that the stamp and the document image data are combined by the printer. The printer combines the stamp and the original image data to form on the sheet.

(Other embodiments)
Furthermore, the present invention can be applied to a system including a plurality of devices (for example, a computer, an interface device, a reader, a printer, etc.) or to an apparatus (an image forming apparatus, a printer, a facsimile device, etc.) including a single device. It is also possible.

  In addition, an object of the present invention is to read and execute a program of a system or apparatus (or CPU or MPU) from a storage medium storing a program that realizes the procedure of the flowchart shown in the above-described embodiment. Can also be achieved. In this case, the program itself read from the storage medium realizes the functions of the above-described embodiment. Therefore, this program and a storage medium storing the program also constitute one aspect of the present invention.

  As a storage medium for supplying the program, for example, a floppy (registered trademark) disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like is used. Can do.

  The functions of the above-described embodiment are realized by executing the program read by the computer. In addition, an OS (operating system) running on the computer based on the instruction of the program performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing. It is.

  Furthermore, the program read from the storage medium may be written to 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.

1 is a block diagram illustrating a configuration of a printer control system according to an embodiment of the present invention. FIG. It is a block diagram which shows an example of the structure for the printing process in the host computer concerning one Embodiment of this invention. FIG. 3 is a block diagram illustrating an example in which the configuration illustrated in FIG. 2 is expanded. It is a block diagram which shows the structure of the application which produces the encoding image data concerning one Embodiment of this invention. It is a figure which shows an example of the user interface of the application which produces the encoding image data concerning one Embodiment of this invention. It is a figure which shows an example of the user interface of the printer driver which can designate the stamp image data concerning one Embodiment of this invention. It is a flowchart which shows the production | generation method of the spool file concerning one Embodiment of this invention. It is a flowchart which shows an example of the printing control by the spool file manager concerning one Embodiment of this invention, and the determination process of a physical page number. It is a flowchart which shows an example of the process in the despooler concerning one Embodiment of this invention. It is a figure which shows an example of the setting file for job output concerning one Embodiment of this invention. It is a figure which shows an example of the job setting information shown by FIG. It is a figure which shows an example of the physical page information shown by FIG. It is a figure which shows an example of the physical page setting information shown by FIG. It is a figure which shows an example of the logical page information shown by FIG. 6 is a flowchart for combining stamp image data with document image data by a spool file manager according to an embodiment of the present invention. It is a figure which shows the example which synthesize | combines stamp image data concerning one Embodiment of this invention with original image data. It is a figure which shows the process which reduces the stamp image data concerning one Embodiment of this invention, and synthesize | combines it with original image data. FIG. 18 is a flowchart of processing for reducing the stamp image data illustrated in FIG. 17 and combining it with document image data.

Explanation of symbols

1 CPU
2 RAM
3 ROM
4 System bus 5 Keyboard controller (KBC)
6 CRT controller (CRTC)
7 Disk controller (DKC)
8 Printer controller (PRTC)
9 Keyboard (KB)
10 CRT display (CRT)
11 External memory 12 CPU
13 ROM
14 External memory 15 System bus 16 Printing section interface (I / F)
17 Printing Department (Printer Engine)
18 Input unit 19 RAM
20 Memory controller (MC)
21 Bidirectional Interface 1000, 2000 Control Unit 1500 Printer 1501 Operation Unit 3000 Host Computer 201 Application 202 Graphic Engine 203 Printer Driver 204 System Spooler 301 Dispatcher 302 Spooler 303 Spool File 304 Spool File Manager 305 Despooler 306 Previewer 307 Setting Change Editor 308 Coded image detection unit 309 Stamp image processing unit 401 Application control unit 402 Driver call unit 403 Code image generation unit 404 Code image synthesis unit 405 Print file reading unit 406 Coded data file reading unit 407 File I / O unit

Claims (14)

First determination means for determining whether a setting for combining a stamp image with a document image exists;
Second determination means for determining whether an encoded image is combined with the document image;
When the first determination unit determines that the setting exists and the second determination unit determines that the encoded image is combined, the stamp image and the encoded image in the document image Third determination means for determining whether or not the
An information processing apparatus comprising: notification means for notifying a user that the stamp image and the encoded image are overlapped by the third determination means.   2. The apparatus according to claim 1, wherein when it is determined by the third determination unit that the image overlaps, the user is notified of the overlap, and only the document image is output from the stamp image and the document image. Information processing device.   2. The information processing apparatus according to claim 1, wherein when the third determination unit determines that there is an overlap, the user is notified of the overlap and the output of the stamp image and the document image is stopped. .   The information processing apparatus according to claim 1, further comprising a changing unit that changes a setting of a stamp image to be combined with the document image when the third determining unit determines that the document image overlaps. .   The information processing apparatus according to claim 4, wherein the changing unit changes a position setting of the stamp image so that the stamp image does not overlap a code image in the document image.   The information processing apparatus according to claim 4, wherein the changing unit changes a size setting of the stamp image so that the stamp image does not overlap a code image in the document image. A first determination step for determining whether or not a setting for combining a stamp image with a document image exists;
A second determination step of determining whether an encoded image is combined with the document image;
When it is determined that the setting exists in the first determination step and the encoded image is determined to be combined in the second determination step, the stamp image and the encoded image in the document image A third determination step of determining whether or not
An information processing method comprising: a notification step of notifying a user of an overlap when it is determined that the stamp image and the encoded image overlap in the third determination step.   8. The apparatus according to claim 7, wherein, when it is determined that there is an overlap in the third determination step, the user is notified of the overlap, and only the document image is output from the stamp image and the document image. Information processing method.   8. The information processing method according to claim 7, wherein, when it is determined in the third determination step that there is an overlap, the user is notified of the overlap and the output of the stamp image and the document image is stopped. .   The information processing method according to claim 7, further comprising a changing step of changing a setting of a stamp image to be combined with the document image when it is determined that the third determination step causes overlap.   The information processing method according to claim 10, wherein the changing step changes a position setting of the stamp image so that the stamp image does not overlap a code image in the document image.   The information processing method according to claim 10, wherein the changing step changes a size setting of the stamp image so that the stamp image does not overlap a code image in the document image.   A program for causing an information processing apparatus to execute the information processing method according to any one of claims 7 to 12.   A storage medium storing a program for causing an information processing apparatus to execute the information processing method according to any one of claims 7 to 12.

Images