US20070211276A1 - Information processing apparatus with print preview function - Google Patents

Abstract

A printer apparatus of this invention includes a reception unit which receives print job from a host apparatus, a preview information generation unit which generates preview information that indicates layouts of logical pages and finishing processing for respective physical pages to be printed in accordance with job control information and print data included in the print job, when a job type corresponding to the print job is preview, and a transmission unit which transmits the preview information to the host apparatus.

Description

BACKGROUND OF THE INVENTION
• 1. Field of the Invention
• The present invention relates to, for example, an information processing apparatus such as a personal computer or the like which transmits print data to a printer and, more particularly, to an information processing apparatus which displays a preview based on print data at the time of a print instruction.
• 2. Description of the Related Art
• Conventionally, a preview scheme that displays a print result on an information processing apparatus such as a host computer or the like before execution of printing roughly includes two schemes.
• In one preview scheme, an information processing apparatus generates and displays a preview image by simulating processing to be executed by a printer so as to allow the user to confirm a finishing result upon using a function such as stapling or the like (for example, see Japanese Patent Laid-Open No. 2001-67347).
• In the other preview scheme, an information processing apparatus sends print instructions to a printer, the printer sends back image data which has undergone RIP processing (rasterize processing) to a host, and the host displays the image data (for example, see Japanese Patent Laid-Open No. 08-030410).
• Some printers as computer peripheral devices support a Print On Demand (to be abbreviated as POD hereinafter) service, and have advanced functions such as complete bookbinding. Upon using printers with advanced functions, plural pieces of information associated with print results such as a finishing result, color determination result, blank page determination result, and the like that the user should know before actual printing are complicated, and functions which do not allow for mistakes are increasing. Since these pieces of information are different for respective printers, respective print instructions, and respective pages, it becomes difficult for a computer to completely simulate them.
SUMMARY OF THE INVENTION
• The present invention has been made in consideration of the above prior art, and has as its object to provide a printer apparatus which can implement an accurate preview display that reflects processing to be executed by the printer. It is another object of the present invention to provide a printer apparatus which allows the user to change print settings while displaying a preview window and can accurately reflect changes of the print setting in the preview and printouts.
• In order to achieve the above object, the present invention comprises the following arrangement. That is, there is provided a printer apparatus comprising:
• a reception unit adapted to receive print job from a host apparatus;
• a preview information generation unit adapted to generate, when a job type corresponding to the print job is preview, preview information which indicates layouts of logical pages and finishing processing for respective physical pages to be printed in accordance with job control information and print data included in the print job; and
• a transmission unit adapted to transmit the preview information to the host apparatus.
• The present invention can implement an accurate preview display that reflects the states of output materials by the printer. The present invention allows the user to change print settings while displaying a preview window, and can accurately reflect the changes of the print settings on a preview and printouts.
• Further features of the present invention will become apparent from the following description of exemplary embodiments with reference to the attached drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a block diagram for explaining the arrangement of a print control apparatus according to one embodiment of the present invention;
• FIG. 2 is a block diagram showing the arrangement of a typical print system of a host computer to which a printer is connected;
• FIG. 3 is a block diagram showing the arrangement of a print system which temporarily spools an intermediate code before it converts print instructions from an application into printer control commands;
• FIG. 4 is a sectional view for explaining a printer according to the present invention;
• FIG. 5 is a flowchart showing the processing in aspooler302;
• FIG. 6 is a flowchart showing the print control in aspool file manager304;
• FIG. 7 is a flowchart showing the processing in adespooler305;
• FIG. 8 shows an example of a print setting window of a printer driver;
• FIG. 9 shows an example of a list display window of a spool file;
• FIG. 10 shows an example of preview information (JDFP);
• FIG. 11 shows an example of a preview window;
• FIG. 12 shows an example of a preview job;
• FIG. 13 shows an example of a preview job;
• FIG. 14 is a flowchart for explaining the preview processing of a previewer;
• FIGS. 15A and 15B are flowcharts for explaining the preview processing and print processing of a printer;
• FIG. 16 is a chart showing the flow of the overall conventional preview processing system;
• FIG. 17 is a chart showing the flow of the overall preview processing system according to the present invention;
• FIG. 18 shows an example of a print instruction job; and
• FIG. 19 shows an example of a print cancel job.
DESCRIPTION OF THE EMBODIMENTS
• Embodiments to which the present invention can be suitably applied will be described hereinafter.FIG. 1 is a block diagram showing the arrangement of a printer control system according to one embodiment of the present invention. Note that the present invention can be applied to any of a standalone device, a system including a plurality of devices, and a system in which devices are connected via a network such as a LAN, WAN, or the like to execute processing, as long as the functions of the present invention can be implemented.
• Referring toFIG. 1, ahost computer3000 comprises aCPU101. TheCPU101 systematically controls respective devices connected to asystem bus104. TheCPU101 controls document processing, print processing, and the like of documents that include any combinations of graphics data, image data, text data, table data (including a spreadsheet), and the like together, based on a document processing program and the like stored in a program ROM of aROM103 or anexternal memory111. The program ROM of theROM103 or theexternal memory111 stores an operating system program (to be referred to as an OS hereinafter), and programs of the procedures shown inFIGS. 5,6,7, and14. A font ROM of theROM103 or theexternal memory111 stores font data and the like used in the document processing. A data ROM of theROM103 or theexternal memory111 stores various data used upon executing the document processing and the like. ARAM102 serves as a main memory, work area, and the like of theCPU101.
• A keyboard controller (KBC)105 controls key inputs from akeyboard109 and a pointing device (not shown). A CRT controller (CRTC)106 controls a display on a CRT display (CRT)110. A disk controller (DKC)107 controls access to theexternal memory111 such as a hard disk (HD), flexible disk (FD), or the like. Theexternal memory111 such as the hard disk or the like stores programs and data such as a boot program, various applications, font data, user files, edit files, a printer control command (or to be referred to as a PDL command) generation program (to be referred to as a printer driver hereinafter), and the like. A printer controller (PRTC)108 is connected to aprinter2000 via anetwork121, and executes communication control processing with theprinter2000. The printer (printing apparatus)2000 is often connected to a network such as Ethernet® or the like.
• Note that theCPU101 executes rasterize processing of a print preview image on a display information RAM assured on, e.g., theRAM102 to display a preview on theCRT110. TheCPU101 opens various registered windows based on commands instructed by a mouse cursor or the like (not shown) on the CRT110, and executes various kinds of data processing in accordance with operations by the operator. Upon execution of printing, the user opens a window associated with print settings, and can set a printer and a print processing method for a printer driver as well as selection of a print mode. The user can also call and display the window for the print settings (also called print attributes) from a preview display window, and can change the settings from the windows for the print settings. In this embodiment, various settings for printing are called print settings, and information including the print settings together is called print setting information. The print setting information is, for example, a structure called DEVMODE in Windows®. The print setting information is changed by the printer driver, is passed to a spooler for each print job, and is saved as the print settings of that job. This information which is stored in the spooler and indicates the print settings for each job is called job setting information.
• Aprinter CPU112 controls theprinter2000. Theprinter CPU112 outputs an image signal as output information to aprinter engine2010 connected to asystem bus115 via aprinter engine interface118 based on control programs and the like stored in a program ROM of aROM113 or anexternal memory2011. The program ROM of theROM113 stores control programs and the like of theCPU112. A font ROM of theROM113 stores font data and the like used upon generating the output information. A data ROM of theROM113 stores information and the like used on the host computer in case of a printer which has noexternal memory2011 such as a hard disk or the like.
• Theprinter CPU112 can execute communication processing with the host computer via aninterface unit2001, and can send information and the like in the printer to thehost computer3000. ARAM119 serves as a main memory, work area, and the like of theprinter CPU112, and can expand its memory capacity by an optional RAM connected to an expansion port (not shown). Note that theRAM119 can also be used as an output information rasterize area, environmental data storage area, NVRAM, and the like. A disk controller (DKC)120 controls access to theexternal memory2011 such as a hard disk (HD), IC card, or the like. Theexternal memory2011 is connected as an option, and stores font data, emulation programs, form data, and the like. On theoperation panel2020, switches, LED indicators, and the like used to operate the printer are arranged. Theprinter CPU112 executes the program of the procedure shown inFIGS. 15A and 15B, and rasterizes print data received from thecomputer3000 to print it on a paper sheet. In case of a preview job, theprinter CPU112 generates preview information which reflects layouts and the like for respective pages, and finishing processing based on the job setting Information received from thecomputer3000, and transmits the generated preview information to thecomputer3000.
• The number ofexternal memories2011 is not limited to one, and a plurality of external memories may be connected. A plurality of external memories including an optional font card in addition to built-in font data, an external memory which stores a program that interprets a printer control language of a different language system, and the like may be connected. Furthermore, the printer may comprise an NVRAM (not shown), and may store printer mode setting information from anoperation panel2020.
<Arrangement of Printer>
• FIG. 4 is a sectional view of a color laser beam printer which has a double-sided print function, as an example of theprinter2000. Theprinter2000 scans, via apolygon mirror31, aphotosensitive drum15 with a laser beam, which is modulated by image data for each color obtained based on print data input from thehost computer3000, thus forming an electrostatic latent image. Theprinter2000 develops this electrostatic image by each toner to obtain a visible image of a given color, and multiple-transfers visible images for all the colors onto anintermediate transfer member9, thus forming a color visible image. Furthermore, theprinter2000 transfers this color visible image onto a transfer material (e.g., a sheet of paper)2, and fixes the color visible image on thetransfer material2. An image forming unit which makes the aforementioned control comprises a drum unit having thephotosensitive drum15, a primary charger having acontact charger roller17, a cleaning unit, a developing unit, theintermediate transfer member9, a paper feed unit including apaper cassette1 andvarious rollers3,4,5, and7, a transfer unit including atransfer roller10, and a fixingunit25.
• Adrum unit13 is configured by integrating the photosensitive drum (photosensitive body)15 and acleaner container14 which also serves as a holder of thephotosensitive drum15 and has a cleaning mechanism. Thisdrum unit13 is detachably supported by a printer main body, and is easily exchanged by another unit in correspondence with the service life of thephotosensitive drum15. Thephotosensitive drum15 is formed by applying an organic photoconductor layer on the outer circumferential surface of an aluminum cylinder, and is rotatably supported by thecleaner container14. Thephotosensitive drum15 is rotated by the driving force transmitted from a drive motor (not shown), which rotates thephotosensitive drum15 counterclockwise in correspondence with the image forming operation. An electrostatic latent image is formed by selectively exposing the surface of thephotosensitive drum15. In ascanner unit30, a modulated laser beam is reflected by thepolygon mirror31, which rotates in synchronism with a horizontal sync signal of an image signal by amotor31a, and strikes the photosensitive drum via alens32 and reflectingmirror33.
• The developing unit has an arrangement comprising threecolor developers20Y,20M, and20C used to develop yellow (Y), magenta (M), and cyan (C), and oneblack developer21B used to develop black, so as to visualize the electrostatic latent image. Thecolor developers20Y,20M, and20C and theblack developer21B respectively comprise sleeves20YS,20MS, and20CS, and21BS, and application blades20YB,20MB,20CB, and21BB, which are respectively in press contact with the outer circumferential surfaces of these sleeves20YS,20MS, and20CS, and21BS. The threecolor developers20Y,20M, and20C respectively have application rollers20YR,20MR, and20CR.
• Theblack developer21B is detachably attached to the printer main body, and thecolor developers20Y,20M, and20C are detachably attached to a developingrotary23, which rotates about arotation shaft22. The sleeve21BS of theblack developer21B is located to have a small gap of about 300 μm from thephotosensitive drum15. Theblack developer21B feeds toner using a built-in feeding member, and gives an electric charge to the toner by frictional electrification so as to apply the toner on the outer circumferential surface of the sleeve21BS, which rotates clockwise, using the application blade21BB. By applying a developing bias to the sleeve21BS, an electrostatic latent image on thephotosensitive drum15 is developed by black toner to form a visible image on thephotosensitive drum15.
• The threecolor developers20Y,20M, and20C rotate upon rotation of the developingrotary23 in image formation, and the predetermined sleeve20YS,20MS, or20CS opposes thephotosensitive drum15 to have a small gap of about 300 μm. In this way, thepredetermined color developer20Y,20M, or20C stops at a developing position that opposes thephotosensitive drum15, thus forming a visible image on thephotosensitive drum15.
• Upon forming a color image, the developingrotary23 rotates upon completion of a color developing process for a component color on theintermediate transfer member9. The developing processes are done in the order of theyellow developer20Y,magenta developer20M, cyan developer20C, andblack developer21B. After four rotations of theintermediate transfer member9, visible images of yellow, magenta, cyan, and black toners are sequentially formed, thus consequently forming a full-color visible image on theintermediate transfer member9.
• Theintermediate transfer member9 contacts thephotosensitive drum15, and rotates upon rotation of thephotosensitive drum15. Theintermediate transfer member9 rotates clockwise and receives four visible images multiple-transferred from thephotosensitive drum15 upon color image formation. Also, the transfer roller10 (to be described later) contacts theintermediate transfer member9 to clamp and convey thetransfer material2 upon image formation, thus simultaneously multiple-transferring the color visible image on theintermediate transfer member9 onto thetransfer material2. ATOP sensor9aandRS sensor9bused to detect the positions associated with the rotation direction of theintermediate transfer member9, and adensity sensor9cused to detect the density of a toner image transferred onto the intermediate transfer member are located around the intermediate transfer member.
• Thetransfer roller10 comprises a transfer charger supported to be movable toward or away from theintermediate transfer member9. Thetransfer roller10 is formed by warping a medium resistance foamed elastic body on a metal shaft.
• Thetransfer roller10 moves away downward so as not to disturb color visible images while the color visible images are multiple-transferred onto theintermediate transfer member9, as indicated by the solid line inFIG. 4. After the four color visible images are formed on theintermediate transfer member9, thetransfer roller10 is located at an upper position indicated by the dotted line inFIG. 4 by a cam member (not shown) in synchronism with the transfer timing of the multi-color visible image onto thetransfer material2. In this way, thetransfer roller10 is brought into press contact with theintermediate transfer member9 at a predetermined pressure via thetransfer material2, and is applied with a bias voltage, thus transferring the multi-color visible image onto thetransfer material2.
• The fixingunit25 fixes the transferred multi-color visible image while conveying thetransfer material2, and comprises a fixingroller26 which heats thetransfer material2, and apressure roller27 which makes thetransfer material2 pressure-contact the fixingroller27. The fixingroller26 andpressure roller27 have a hollow shape, and respectively incorporateheaters28 and29. That is, thetransfer material2 which holds the multi-color visible image is conveyed and applied with heat and pressure by the fixingroller26 andpressure roller27, thus fixing the toner image on its surface.
• After the visible image is fixed, thetransfer material2 is exhausted onto anexhaust unit37 byexhaust rollers34,35, and36, thus ending the image forming operation.
• The cleaning unit cleans the residual toner on thephotosensitive drum15 andintermediate transfer member9, and thecleaner container14 stores waste toner after the toner visible image formed on thephotosensitive drum15 is transferred onto theintermediate transfer member9 or after the four color visible images formed on theintermediate transfer member9 are transferred onto thetransfer material2.
• A transfer material (print sheet)2 to be printed is picked up from thepaper cassette1 by apickup roller3, and is conveyed while being clamped between theintermediate transfer member9 and transferroller10. Then, a color toner image is transferred to thetransfer material2, and is fixed via the fixingunit25. In a single-sided print mode, aguide38 forms a conveyance path to guide the print sheet to the exhaust unit at an upper position. However, in a double-sided print mode, theguide38 forms a path to guide the print sheet to a double-sided unit at a lower position.
• The print sheet guided to the double-sided unit is temporary fed to a portion under the paper cassette1 (a convey path indicated by the two-dashed chain line) by conveyrollers40, and is then conveyed in a reverse direction to be fed to a double-sided tray39. On the double-sided tray39, the obverse and reverse faces of the print sheet are reversed from those placed on thepaper cassette11, and the leading and trailing ends of the convey direction are reversed. In this state, by transferring and fixing toner images again, the double-sided print mode can be attained.
<Software Configuration of Host Computer>
• FIG. 2 shows the configuration of typical print processing in the host computer to which the printing apparatus such as a printer or the like is connected directly or via a network. Anapplication201,graphic engine202,printer driver203, andsystem spooler204 exist as files saved in theexternal memory111. These files are executed after they are loaded onto theRAM102 by the OS or modules that use those of the OS. Theapplication201 andprinter driver203 can be added to the HD of theexternal memory111 via the FD or a CD-ROM (not shown) of theexternal memory111, or a network (not shown). However, when print processing is executed from theapplication201 to theprinter2000, theapplication201 outputs rendering data using thegraphic engine202 which is similarly loaded onto theRAM102 and is ready to run. Note that the following explanation will be given using the Windows® OS available from Microsoft Corporation. In Windows®, thegraphic engine202 as rendering means of the OS is generally called a GDI (Graphic Device Interface), and the application outputs rendering data called GDI functions to the GDI serving as the graphic engine.
• Thegraphic engine202 similarly loads onto theRAM102 theprinter driver203, which is prepared for each printing apparatus, from the external memory1l. Thegraphic engine202 then converts the CDI functions output from theapplication201 into DDI (Device Driver Interface) functions based on a library and outputs the DDI functions to theprinter driver203. Theprinter driver203 converts the DDI functions received from thegraphic engine202 into control commands that can be recognized by the printer, e.g., PDL (Page Description Language) commands. The converted PDL commands are output to theprinter2000 as print data included in a print job via thesystem spooler204, which is loaded onto theRAM102 by the OS, and theinterface121. The preview print system proposed by Japanese Patent Laid-Open No. 2001-067347 is implemented by providing a configuration that temporarily spools print data from the application as intermediate code data in addition to the print system which includes the printer and host computer shown inFIG. 2.
• A preview print system of this embodiment will be described below usingFIG. 3.FIG. 3 shows a system obtained by enhancing that shown inFIG. 2, and adopts a configuration that temporarily generates aspool file303 including intermediate codes upon sending print instructions from thegraphic engine202 as the rendering means of the OS to theprinter driver203. Since intermediate codes are temporarily generated, a previewer loads the contents of the intermediate codes of thespool file303 and allows the user to preview and to change the print settings.
• For these purposes, the system shown inFIG. 2 is enhanced to spool as intermediate code data, as shown inFIG. 3. In order to change the settings of print data, the user normally makes settings from a window provided by theprinter driver203, which saves the setting contents on thePAM102 orexternal memory111.
<Software Configuration of Host Computer of This Embodiment>
• Details ofFIG. 3 will be described below. The same reference numerals inFIG. 3 denote the same blocks as those inFIG. 2. As shown inFIG. 3, in this enhanced processing system, adispatcher301 receives print instructions output from thegraphic engine202. If the print instructions (DDI functions) received from thegraphic engine202 are those (GDI functions) issued from theapplication201, thedispatcher301 loads thespooler302 stored in theexternal memory111 onto theRAM102. Also, thedispatcher301 sends the received print instructions (GDI functions) to thespooler302 in place of the printer driver. In order to allow thedispatcher301 to determine the source of print instructions, a method of appending an ID of a process as a transmission source of print instructions to those print instructions or the like is available.
• Thespooler302 interprets the received print instructions, converts them into intermediate codes in a predetermined format, which allows easy modifications, for respective pages, and outputs the converted intermediate codes to store them in thespool file303. The spool file of the intermediate codes stored for each page is called a page rendering file (or Unified Display List: UDL). Thespooler302 acquires print setting information set using theprinter driver203 from it, and saves the acquired print setting information in thespool file303 as a setting file for each job. The print setting file stored for each job is called a job setting file. The job setting file is also called a JDF (Job Definition Format). This job setting file will be described later. The operator changes the print settings on the printer driver in advance before he or she issues a print instruction from the application. Print setting items that can be set using the printer driver include an Nup setting used to lay out, e.g., N pages on one page in a reduced scale, double-/single-sided setting, staple setting, color/monochrome setting, and the like.
• Thespooler302 loads aspool file manager304 stored in theexternal memory111 onto theRAM102, and notifies thespool file manager304 of the generation state of thespool file303. After that, if thespool file manager304 determines that print processing is ready to be executed using the intermediate data stored in thespool file303, it loads adespooler305 stored in theexternal memory111 onto theRAM102. Thespool file manager304 instructs thedespooler305 to execute print processing of page rendering files described using the intermediate codes (UDL) described in thespool file303. In this case, thespool file manager304 loads apreviewer306 stored in theexternal memory111 onto theRAM102, and notifies it of the job ID to set thepreviewer306 in the standby state.
• Thedespooler305 re-generates GDI functions in accordance with the contents of the page rendering files of the intermediate codes included in thespool file303 and the job setting information included in thespool file303. The re-generated GDI functions are output via thegraphic engine202 as the rendering means of the OS once again.
• If the print instructions (DDI functions) received by thedispatcher301 from thegraphic engine202 are those (GDI functions) issued by thedespooler305, thedispatcher301 passes the print instructions to theprinter driver203.
• Theprinter driver203 generates printer control commands in a page description language (PDL) or the like based on the print instructions (DDI functions) acquired from thegraphic engine202, and sends the generated commands to theprinter2000 via thesystem spooler204 as a print job. In this embodiment, if a preview mode is designated from a user interface or the like of the printer driver, a preview attribute is appended to the PDL commands, which are transmitted to the printer. For example, the preview attribute is appended to information (job control information) associated with a job as a unit of print processing, and that information is transmitted to the printer. Theprinter2000 does not print the print job appended with the preview attribute onto paper sheets, but it generates preview information associated with the job ID and transmits the generated information to thecomputer3000. The preview information includes information required to display a preview such as layout information indicating the layout of pages which are to be actually printed on paper sheets and are stored in thespool file303, staple positions of respective physical pages, and the like. Note that a paper sheet which is to actually undergo printing is also called a sheet or physical page. Also, a page stored in thespool file303 is also called a logical page. In addition, the preview information includes a blank page determination result (blank page information) indicating whether or not a page of interest is a blank page, and color mode information indicating one of monochrome and color.
• Thepreviewer306 configures apreview unit310 together with a settingchange editor307. Upon reception, from the printer (printing apparatus), of the preview information corresponding to the job ID received from thespool file manager304, thepreviewer306 stores the received preview information in thespool file303. At the same time, thepreviewer306 pops up a window of the spool file manager, and displays, as a list, job IDs associated with the preview information spooled in thespool file303 on the window. Note that the preview information is also called “JDFP” (Job Definition Format For Preview) for short.
• The user can set to display a preview by providing a user interface window shown in, e.g.,FIG. 8. In order to display a print preview and to change the print settings, the user must designate “store” from a pull-down menu (also called output method selection means)803 as means for “designating an output destination” on the property window of the printer driver shown inFIG. 8. When the user wants to display only a preview, he or she selects “preview” from the pull-down menu803 as designation of the output destination.
• FIG. 9 shows a display example of the print state when one print job is spooled. By pressing one ofmenu bar items901 or one ofmenu icons902 immediately below the menu bar, the user can manipulate a job. The manipulations that the user can make using themenu bar901 are the same as those that he or she can make using themenu icons902 the manipulations include “print”, “save & print”, “preview”, “delete”, “copy”, “edit job”, “change order”, and the like. “Print” is a manipulation for making theprinter2000 print a print job selected from alist903. “Save & print” is a manipulation for making the printer print the print job selected from thelist903 while leaving the spool file of the intermediate codes of that print job intact. “Preview” is a manipulation for displaying a preview of the print job selected from thelist903 while reflecting the print settings. “Delete” is a manipulation for deleting the spool file of the intermediate codes of the print job selected from thelist903. “Copy” is a manipulation for copying the spool file of the intermediate codes of the print job selected from thelist903. “Job edit” is a manipulation for changing the print settings (layout setting, finishing setting, and the like) of the job selected from thelist903. “Change order” is a manipulation for changing the print order of jobs.
• When the user selects a certain print job and designates its preview on the window (FIG. 9) of thespool file manager304, thespool file manager304 loads thepreviewer306 stored in theexternal memory111 onto theRAM102. Thespool file manager304 designates thepreviewer306 to execute preview processing of the job of the intermediate codes described in thespool file303.
• Upon reception of the designation, thepreviewer306 receives the preview information from the printer, and sequentially reads out page rendering files (UDL) of the corresponding intermediate codes included in thespool file303. Thepreviewer306 modifies the page rendering files in accordance with the setting information for respective pages included in the preview information (JDFP), re-generates GDI functions based on the modified intermediate data (page rendering files), and outputs the re-generated GDI functions to thegraphic engine202. In this case, a client area of thepreviewer306, i.e., a display device is designated as the output destination. In this manner, since thegraphic engine202 which received the GDI functions outputs DDT functions for the display device, a display output onto the screen can be attained. Note that the preview information and page rendering files can be associated with each other using the job ID of the print job. Since the job ID is included in both the preview information and spool file, the preview information and spool file having the same job ID can be associated with each other as information pertaining to an identical print job.
• Thegraphic engine202 can perform appropriate rendering in accordance with the designated output destination. For example, the display device and printing apparatus have different resolutions. Thegraphic engine202 acquires attribute information such as the resolution of the designated output destination and the like from, e.g., a database or the like managed by the OS, and executes rendering using the acquired information. As described above, thepreviewer306 can be implemented by the method of modifying the intermediate codes included in thespool file303 in accordance with the preview information (JDFP) and outputting the modified intermediate codes using thegraphic engine202.
<Software Configuration ofPrinter2000>
• The operation of the printer (printing apparatus)2000 shown inFIG. 3 will be described below. Theprinter2000 receives printer control commands such as PDL commands or the like from thehost computer3000, and temporarily stores them in areception buffer2003. Acommand interpreter2007 interprets the printer control commands such as the PDL commands. As a result of interpretation, if the received printer control commands are print commands, a renderingprocessing execution unit2005 rasterizes image data in accordance with the print settings of the print job of interest, and temporarily stores the image data in anHD2011. After the image data that can be output is stored, anoutput controller2008 converts the image data into a video signal in synchronism with engine rotations (ship processing), and passes the video signal to aprinter engine2010. Theprinter engine2010 forms images on sheets in accordance with the video signal. Note that the job includes a series of printer control commands delimited by a job start command. The job setting information indicating the print settings is transmitted from thehost computer3000 to theprinting apparatus2000 after, e.g., the job start command. Whether one job is a print job or preview job is indicated by, e.g., the value of a “job type” field in the job setting information. Alternatively, the value of the “job type” field in the job setting information may be copied to the job start command, so that the job start command indicates the job type.
• In this embodiment, if the job received by theprinting apparatus2000 is a preview job, the renderingprocessing execution unit2005 rasterizes image data in accordance with the designated settings in the same manner as in the print job. The rasterized image data is temporarily stored in theHD2011 together with the job ID. The renderingprocessing execution unit2005 associates detailed preview information (JDFP) for respective physical pages generated during the process for rasterizing image data to process it to a state immediately before printing, and the temporarily stored image data, and saves them as a set.
• The generated preview information is returned to thepreviewer306 of thehost computer3000 as the transmission source of the job. In order to speed up the preview processing, the generation time of the preview information (JDFP) may be shortened by simplifying the processing for rasterizing to an image, and after the preview information is returned to the previewer, image data to be printed may be rasterized.
• Thepreviewer306 sends, to the printer, print instructions with a preview attribute generated by theprinter driver203 based on the job setting information (JDF) and page rendering files (UDL). As a result, the printer executes the same processing as actual print processing, and generates accurate preview information (JDFP) as in actual printing. The preview information generated by the printing apparatus has the same data format as that of the job setting information. However, unlike the job setting information, the preview information is generated for each physical page. Also, the preview information includes items different from the job setting information. The job setting information and preview information will be described later with reference toFIGS. 12,13, and the like. Thepreviewer306 modifies data of the spooled page rendering files (UDL) based on the preview information (JDFP) received from the printer, and outputs the modified data to the display. In this way, an accurate preview display can be attained.
• As a result of the above preview processing, thepreviewer306 displays previews as large as printouts that reflect the job settings included in thespool file303 on the screen, as shown inFIG. 11. After that, if the user instructs to clear the displayed contents, thepreviewer306 is closed, and the control shifts to thespool file manager304. Thespool file manager304 displays a window (FIG. 9).
• Upon executing job setting/print processing displayed on the previewer, the user designates “print” or “save & print” on the window of thespool file manager304 to issue a print request to thegraphic engine202. If the print settings are not to be changed, the user can designate the job ID in the print request. The printer which received the printer control commands of the print request via thegraphic engine202 and the like can output images which correspond to the designated job ID and have already undergone RIP (have already been rasterized to image data) at high speed.
• Upon changing the print settings, the user changes the print settings such as the layout, paper orientation, print order, paper cassette to be used, and the like from the print setting window provided by thepreviewer306, and settles the changes. The settingchange editor307 edits the job setting information (JDF) corresponding to the preview job saved in thespool file303 in accordance with the contents of the changed print settings. Thedespooler305 reads out the edited job setting information from thespool file303, and passes it to theprinter driver203 together with the job ID via thegraphic engine202 and the like. Theprinter driver203 generates printer control commands corresponding to differences from the printer control commands of the already transmitted job, and outputs them to theprinting apparatus2000. In this case, the differences are limited to those in the job setting information. Therefore, for example, new printer control commands required to transmit the job setting information to theprinting apparatus2000 are generated, and are transmitted to theprinting apparatus2000 together with the job ID. This job ID is the same as that of the preview job which was transmitted first to theprinting apparatus2000.
<Processing Flow>
• The processing flow of the conventional preview scheme will be described below usingFIGS. 2 and 16.FIG. 16 shows an example of the processing flow of the overall conventional preview processing system. Upon reception of a print instruction from theapplication201, theprinter driver203 generates intermediate codes (processing step1601). The generated intermediate codes are saved in a spool file. A preview utility generates an image to be displayed by loading the intermediate codes, and displays a preview on the screen of a personal computer (processing step1602). If the display result has no problem, the user presses a print button to call theprinter driver203. Theprinter driver203 generates PDL commands (printer control commands) (processing step1603) Upon reception of the print job including the PDL commands from theprinter driver203, aprinter600 starts print processing from PDL command interpretation (processing step1604). The preview utility of the host computer generates and displays a preview image using the intermediate codes.
• FIG. 17 shows an example of the processing sequence of the overall system of this embodiment. Upon reception of a print instruction from theapplication201, theprinter driver203 generates intermediate codes (processing step1701) Thespooler302 saves the intermediate codes in thespool file303. Thepreview unit310 loads the spooled intermediate codes, and issues a print instruction to theprinter driver203. Note that this print instruction includes information indicating preview. For example, information indicating preview is described in the job setting information. The print instruction including information indicating preview is referred to as a preview instruction in this invention. Upon reception of the print instruction (i.e., preview instruction), theprinter driver203 generates PDL commands (processing step1702). Theprinter driver203 appends a preview attribute to the generated PDL commands, and transmits them as print instructions with the preview attribute to theprinter2000. The print instruction send to theprinter2000 from theprinter driver203 is referred to as a print job. The print job with the preview attribute is referred to as a preview job. Upon reception of the print job with the preview attribute, theprinter2000 interprets the PDL commands to generate preview information (JDFP), and returns the generated preview information to the host computer (processing step1703). A final recipient of the preview information in the host computer is thepreview unit310. Theprinter2000 also executes RIP processing of the print job with the preview attribute received after interpretation of the PDL commands to generate image data. The generated image data are stored in the hard disk together with the preview information in association with the job ID (processing step1705). However, as this RIP processing, the same RIP processing as that upon reception of the print job is executed to generate image data to be printed. If the PDL commands are also saved, only information associated with differences may be received after the settings have been changed. Hence, it is desirable to store the PDL commands. In this embodiment, the received PDL commands are also stored.
• Thepreview unit310 loads the spooled intermediate codes, and makes preview display in accordance with the preview information (JDFP) received from the printer2000 (processing step1704). The spooled intermediate codes include image information for respective pages such as objects to be rendered for respective physical pages, and the like. The preview information includes information associated with the print settings such as the layout for each physical page, finishing information, and the like. Thepreview unit310 rasterizes the intermediate codes to those for display, lays out logical pages in accordance with the print settings described in the preview information, and appends image objects according to output materials. The image objects to be appended include those which represent punch holes, staples, a watermark, character strings of tab sheets, and the like. When a finisher has an inserter function, image objects that represent sheets such as a front cover sheet, back cover sheet, tab sheets, and the like to be inserted by an inserter, and objects such as character strings, images, and the like written on these sheets to be inserted are inserted in accordance with the preview information. If a finisher having a bookbinding function is added to theprinter2000, thepreview unit310 also appends identification objects indicating the bookbinding positions and the like. In this way, preview images are generated and displayed in accordance with the preview information.
• When the user changes the print settings, thepreview unit310 reflects the changed print settings in the job setting information. Also, thepreview unit310 sends a print instruction to theprinter driver203 via thegraphic engine202. Theprinter driver203 generates difference PDL commands (processing step1710). Since information changed by thepreview unit310 is limited to the job setting information, new PDL commands are generated as difference PDL commands. The difference PDL commands are transmitted to theprinter2000 together with the job ID. This job ID is the same as that of the preview job which was transmitted to theprinter2000 first. Upon reception of the difference PDL commands, theprinter2000 generates preview information again with reference to its job ID (processing step1707). Inprocessing step1707, for example, theprinter2000 substitutes the job setting information received as the difference PDL commands with that in the PDL commands stored in association with that job ID. Theprinter2000 then generates preview information based on the substituted PDL commands. Theprinter2000 transmits the generated preview information to thepreview unit310 as the request source of the preview information. After that, theprinter2000 executes RIP processing using the changed job setting information to reflect the changed print settings in image data, thus updating the stored image data (processing step1709). This RIP processing may be executed for only a changed part if the settings are partially changed. However, since the changed part in job setting information influences all the pages included in the job of interest even when settings are changed partially, it is desirable to execute the RIP processing for the entire job again.
• Thepreview unit310 generates and displays preview images using the received preview information and the spooled intermediate codes and accepts the print button (processing step1708). When the user has depressed the print button after he or she confirms the preview images, thepreview unit310 sends the print instruction to theprinter driver203. Theprinter driver203 generates difference PDL commands, and sends a print job to the printer2000 (processing step1710). However, if the print settings are not changed, since there is no difference information to be sent, the print job to be transmitted to theprinter2000 at this time need only include information indicating that the job is a print job, and the job ID.
• If the stored PDL commands are not changed, theprinter2000 prints out the images generated inprocessing step1709. If the stored PDL commands are changed, theprinter2000 generates and prints image data that reflect the changes (processing step1711). Image data obtained by applying RIP processing to only the changed part may be printed in place of the image data with the same job ID, but the entire job may undergo the RIP processing again.
• As described above, the printer driver works as a print instruction transmission means that generates, when a preview instruction of data is issued, printer control commands according to print data together with a job type indicating preview, and transmit the generated printer control commands to the printer. In addition, the previewer works as a preview means that generates and displays a preview image based on preview information which is generated by theprinter2000 in accordance with the printer control commands and which indicates layouts and finishing processing for respective physical pages. Moreover, the printer driver works as a setting change means that generates, when the print settings are changed, print instructions associated with a changed part.
<Processing by Spooler>
• FIG. 5 is a flowchart showing the storage processing of the intermediate codes for respective pages in generation of thespool file303. This processing is executed after thedispatcher301 accepts DDI functions as rendering data output from thegraphic engine202 and passes this rendering data to thespooler302 upon reception of a print request from the application.
• Instep501, thespooler302 accepts a print request issued by the application from thedispatcher301 via thegraphic engine202. As described above, theapplication201 displays a dialog used to input the print settings, as shown inFIG. 8, before a print instruction, and theprinter driver203 passes job setting information indicating the print settings input from this dialog to thespooler302. Note that the setting input dialog shown inFIG. 8 includes settingitems801 used to determine the number of logical pages to be laid out per physical page, and the like.
• Thespooler302 checks instep502 if the accepted print request is a job start request. If thespooler302 determines instep502 that the accepted print request is a job start request, the process advances to step503-1, and thespooler302 generates aspool file303 used to temporarily store intermediate data on the PAM102 (or on the hard disk). Subsequently, thespooler302 receives print setting information (corresponding to DEVMODE of Windows®) from theprinter driver203, and stores job setting information (JDF) in the spool file303 (step503-2). After that, thespooler302 notifies thespool file manager304 of the progress of print processing. In this case, if the job designated by the user is a preview job, thespooler302 sends a preview notification to thespool file manager304; if the job is a print job, thespooler302 sends a print start notification to the manager304 (step504).
• Next, in step505 a page counter managed by thespooler302 is reset to1. Note that thespool file manager304 loads job information for the job, the print processing of which has started, and job setting information as modification settings from the job setting file of thespool file303.
• On the other hand, if thespooler302 determines instep502 that the accepted print request is not a job start request, the process advances to step506. Thespooler302 checks instep506 if the accepted request is a job end request. If thespooler302 determines that the accepted request is not a job end request, the process advances to step507, and thespooler302 checks if the accepted request is a new page request. If thespooler302 determines instep507 that the accepted request is a new page request, the process advances to step508-1 to increment the page counter. In step508-2, thespooler302 notifies thespool file manager304 of the progress of print processing. In this case, thespooler302 notifies thespool file manager304 of reception of the new page request as the progress information. At the same time, thespooler302 may notify the page counter value.
• If thespooler302 determines instep507 that the accepted print request is not a new page request, the process advances to step509, and thespooler302 prepares for extraction of intermediate codes (UDL) to each page rendering file. In step510, thespooler302 converts rendering data such as text data, graphic data, image data, and the like passed together with the print request into intermediate data to be stored in thespool file303. In step511, thespooler302 writes the print request which is converted into a storable format (intermediate data) in step510 in each page rendering file (UDL) of thespool file303. After that, the process returns to step501 to accept a print request from the application again. Thespooler302 repeats a series of processes insteps501 to511 until it received a job end request (End Doc) from the application.
• At the same time, thespooler302 acquires print setting information such as modification settings and the like stored in the DEVMODE structure (i.e., print setting information) from theprinter driver203, and stores it as job setting information (JDF) in thespool file303. On the other hand, if thespooler302 determines instep506 that the print request from the application is a job end request, all print requests from the application end. Hence, the process advances to step512, and thespooler302 closes the spool file. In step513, thespooler302 notifies thespool file manager304 of the progress of print processing (job end notification in this case), thus ending the processing.
<Processing by Spool File Manager>
• FIG. 6 is a flowchart showing details of control between thespool file303 generation process and a print data generation process (to be described later) in thespool file manager304. Instep601, thespool file manager304 accepts a progress notification or report of print processing from thespooler302 ordespooler305.
• Thespool file manager304 checks instep602 if the progress notification is a preview or print start notification sent from thespooler302 instep504 above. If the accepted notification is a preview or print start notification, the process advances to step603, and thespool file manager304 acquires a job ID to start job management. Thespool file manager304 can acquire the job ID from a job ID generation counter or the like used to assign serial numbers in turn.
• On the other hand, if thespool file manager304 determines instep602 that the accepted notification is not a preview or print start notification from thespooler302, the process advances to step604. Thespool file manager304 checks instep604 if the progress notification is a new page notification sent from thespooler302 in step508 above, i.e., a processing end notification of one logical page. If the accepted notification is a processing end notification of one logical page, the process advances to step605, and thespool file manager304 stores page information for this page. The page information includes, e.g., a page ID (physical page and logical page), information indicating association between the logical and physical pages, and the like. Instep606, thespool file manager304 determines a page number to be printed every time print instructions (intermediate codes) corresponding to one physical page are spooled, and sends to the despooler a processibility notification indicating that the physical page of interest is ready to process. The processibility notification includes a page ID of the physical page which is ready to output. For example, when a plurality of logical pages are laid out on one physical page, thespool file manager304 receives a new page notification from the spooler every time it receives a logical page to be laid out on that one physical page. If data of all logical pages to be laid out on one physical page are not spooled yet, the processibility notification is not output instep606. Only after data for one physical page are spooled, the processibility notification is output. Note that printing in this case includes preview processing.
• The process then returns to step601, and thespool file manager304 waits for the next notification. In this embodiment, print processing can start even when spooling of the entire print job is not completed after print data for one physical page are spooled.
• On the other hand, if thespool file manager304 determines instep604 that the accepted notification is not a print end notification for one logical page, the process advances to step607. Thespool file manager304 check instep607 if the received notification is a job end notification sent from thespooler302 instep512 above. If the received notification is a job end notification, the process advances to step606 above. On the other hand, if the received notification is not a job end notification, the process advances to step608, and thespool file manager304 checks if the accepted notification is a print end (output end) notification for one physical page from thedespooler305. If the accepted notification is a print end notification for one physical page, the process advances to step609 to check if print processing of the entire job is complete.
• If the print (output) processing is complete, the process advances to step610, and thespool file manager304 sends a print end notification to thedespooler305. If thespool file manager304 determines that the print processing is not complete yet, the process returns to step606. Assume that the number of pages for which thedespooler305 of this embodiment can simultaneously execute print processing (output processing) is 1.
• On the other hand, if thespool file manager304 determines instep608 that the input notification is not a print end notification for one physical page from thedespooler305, the process advances to step611. Thespool file manager304 check instep611 if the input notification is a print end notification from thedespooler305. If thespool file manager304 determines that the input notification is a print end notification from thedespooler305, the processing ends. On the other hand, if the input notification is not a print end notification from thedespooler305, the process advances to step612 to execute another normal processing, and thespool file manager304 waits for the next notification.
• If information required for executing print processing for one physical page is sequentially stored in a file insteps605 and606, the stored information is converted into a reusable format to issue a processibility notification. If the stored information is not reusable, an implementation method which uses a high-speed medium such as a shared memory or the like to overwrite a despooled physical page in turn, and saves the resources may be adopted. The delimiter of one physical page is determined with reference to the job setting information. When the progress of spooling is faster than that of despooling, or when despooling starts after the end of spooling for all pages, a page printable notification for each page may not be sent instep606. In this case, the number of times of notification is saved by adopting the notification contents indicating that a plurality of or all physical pages are ready to print, in accordance with the progress on the despooler side.
<Processing by Despooler>
• FIG. 7 is a flowchart showing details of the print data generation process in thedespooler305. Thedespooler305 generates print data by reading out necessary information (page rendering files (UDL) and job setting information (JDF)) from thespool file303 in accordance with a print request from thespool file manager304. The method of transferring the generated print data to the printer is as described above usingFIG. 3. In the print data generation process by thedespooler305, thedespooler305 checks if the input job is a preview job (S701). If the input job is a preview job, thedespooler305 launches thepreview unit310 by notifying it of the job ID to be processed instep702. The job type indicating a preview job or print job can be determined by referring to the job type field of the job setting information.
• Instep703, thedespooler305 accepts a notification from thespool file manager304. If a notification is input, the process advances to step704. Thedespooler305 checks instep704 if the input notification is a job end notification. If the input notification is a job end notification, the process advances to step705 to set an end flag. The process then advances to step707.
• On the other hand, if thedespooler305 determines instep704 that the input notification is not a job end notification, the process advances to step706, and thedespooler305 checks if the input notification is a processibility notification instep606 inFIG. 6. If thedespooler305 determines instep706 that the input notification is not a processibility notification, the process advances to step708 to execute another error processing. The process then returns to step701 to wait for the next notification. On the other hand, if thedespooler305 determines instep706 that the input notification is a processibility notification, the process advances to step707, and thedespooler305 stores a page ID in the processibility notification which notifies that the print processing is ready to start.
• Thedespooler305 then checks instep709 if the output processing for all the pages of the physical page IDs stored instep707 is complete. If the processing of all the pages is complete, the process advances to step710 to check if an end flag is set. If the end flag is set, thedespooler305 determines that the print processing of the job is complete, and sends a processing end notification to thespool file manager304, thus ending the processing. If thedespooler305 determines instep710 that the end flag is not set, the process returns to step701 to wait for the next notification.
• On the other hand, if thedespooler305 determines instep709 that pages which can undergo output processing still remain, the process advances to step711. Instep711, thedespooler305 reads out a physical page ID to be processed in turn from the stored physical page IDs. The despooler305 loads information required to generate print data of a physical page corresponding to the readout physical page ID from the spool file, and executes print processing (output processing).
• In the print processing, thedespooler305 converts print request instructions (UDL) and job setting information (JDF) stored in thespool file303 into a format that thegraphic engine202 can recognize, e.g., into GDI functions in the Windows® OS. Thedespooler305 transfers these GDI functions to thegraphic engine202. Upon completion of print processing, thedespooler305 sends a print data generation end notification to thespool file manager304 instep712. The process returns to step709, and thedespooler305 repeats print processing for all the physical page IDs stored instep707.
• With the above sequence, the despooler converts spooled intermediate codes into print instructions (GDI functions), and outputs them for each physical page.
<Processing by Printer>
• FIGS.15A and1SB are flowcharts showing details of the process of the printer which receives print instructions with a preview attribute generated instep711.
• Instep1501, the type of a job included in the received PDL commands is checked. If it is determined instep1502 that the received job is a preview job, the process advances to step1503. Instep1503, the received PDL commands are interpreted to collect information required to display a preview. If the information required to display a preview includes information such as the paper cassette, exhaust destination, staple positions, and the like of respective physical pages, the information can be collected by interpreting the job setting information without executing RIP processing (rasterize processing to bitmap data) that takes much time. If the information required to display a preview includes that which requires the RIP processing such as blank page determination, color/monochrome determination, and the like, the RIP processing is executed in this step to collect information.
• Instep1504, preview information (JDEP) is generated based on the information collected instep1503, and the generated preview information is returned to the request source (host computer3000 in this embodiment) of the preview job instep1505.
• Next, it is checked instep1506 if the received PDL commands are those for the already registered job. “Already registered” means that print data and preview information associated with a job with the same job ID as that of the received PDL commands are registered in theprinter2000. If the received PDL commands belong to an unregistered job, the renderingprocessing execution unit2005 of theprinter2000 executes RIP processing instep1510. The generated image data are stored in theHD2011 together with the preview information (JDFP) generated instep1504, original data, and job ID, thus ending the processing.
• If it is determined instep1506 that the PDL commands are those for a BOX already registered job, the print settings of the already registered job are compared with those of the received job by referring to their job setting information instep1507. Upon reception of the PDL commands in association with the already registered job, if, for example, these commands include job control information or print data of a certain page, that job control information is compared with that of the already stored preview information. If information stored in the printer is preview information, the preview information may be compared after preview information is generated based on the received PDL commands and is converted into the same format.
• If it is determined instep1508 that the print settings are different, RIP processing of a part influenced by the changed settings is executed, and image data are stored in theHD2011 together with newly generated preview information (JDFP) instep1509, thus ending the processing. That is, if image data which are left unchanged still remain, newly generated image data are merged with the already stored image data. If no image data which are left unchanged remain, the newly generated image data may be overwritten.
• If it is determined instep1502 that the received job is not a preview job, the job IDs registered in theHD2011 are searched for that of the received PDL commands instep1511. If a hit occurs, since the job ID of the received PDL commands has already been registered, the process branches to step1512. If it is determined instep1512 that the job of received PDL commands is a print cancel job, the process branches to step1518; if it is a print job, the process branches to step1513.
• Instep1513, the print settings of the already stored job are compared with those of the received job by referring to their job setting information. If it is determined instep1514 that the print settings are different, RIP processing of a part influenced by the changed settings is executed, and newly generated image data are stored in theHD2011 instep1515. The newly generated and stored image data are merged with already stored image data. Instep1516, the merged image data are transferred to theprinter engine2010, thus executing print processing. The process advances to step1518 in response to a print end notification from theprinter engine2010.
• If it is determined instep1514 that the print settings are not different, data that have already undergone the RIP processing and are stored in theHD2011 are printed instep1516, and the process advances to step1518, thus ending the processing. If it is determined instep1511 that the job of interest is not stored in theHD2011, RIP processing is executed instep1517 to store generated image data in theHD2011. Instep1516, the stored image data are transferred to theprinter engine2010 to execute print processing. In response to a print end notification from theprinter engine2010, the file of the print job whose print processing is complete is deleted from a BOX instep1518, thus ending the processing. On the other hand, upon reception of a print processing completion notification from theprinter2000, thehost computer3000 deletes the file of the corresponding print job in thespool file303.
<Preview Processing>
• FIG. 14 is a flowchart showing details of the preview process in thepreview unit310. Thepreviewer306 waits for an event from the printer instep1401 after thedespooler305 is launched. An event is transmission of preview information in the example ofFIG. 14. If an event is returned from the printer, thepreviewer306 loads the received preview information (JDFP) instep1402.
• Instep1403, thepreviewer306 reads out the page rendering files (UDL) of a job ID which corresponds to (matches) that of the preview information from thespool file303. Instep1404, thepreviewer306 executes preview rendering processing of the page rendering files (UDL) in accordance with the preview information (JDFP) (preview display).
• Instep1405, thepreviewer306 waits for an event from the user. If it is determined that the user has input a print processing continuation instruction without changing the settings of the preview display, thepreviewer306 generates a print instruction and issues it to the printer instep1407, and the process branches to step1412. The print instruction is generated by the printer driver in accordance with a request from the previewer. This print instruction is a simple one including only a job ID without any changes in print settings, since it is issued to make the printer print the stored job intact.
• If it is determined that the print processing of the job is not to be continued instep1406, the process branches to step1408. Instep1408, it is determined whether the user has instructed the previewer on modification of the print settings or cancellation of the print job. If it is determined that the user has instructed the previewer on cancellation of the print processing of the job instep1408, thepreviewer306 generates a print cancel instruction instep1409, and the process then branches to step1412.
• If it is determined that the user has changed the print settings instep1408, the process branches to step1410. If the user has changed the print settings, job setting information (JDF) is generated from the preview information (JDFP) received instep1402, and print instructions are sent again to the printer using thedespooler305 instep1410. In this case, the processing time can be shortened by sending only a changed part. The settingchange editor307 executes this step.
• If the user issues a re-preview request, the process branches to step1401 according to the determination result instep1411. If the user does not issue any re-preview request, thepreviewer306 deletes the preview information (JDFP) and page rendering files (UDL) in thespool file303, thus ending the processing.
• The procedures of the print preview processing and print processing using thedispatcher301,spooler302,spool file manager304,despooler305,printer2000, andpreviewer306 have been described.
<Job Setting Information and Preview Information>
• A preview job will be described below with reference toFIG. 12. In this example, the preview job includes job setting information (JDF)1201 and print instructions (1202 to1206). The preview job is transmitted as PDL commands to the printer.FIG. 12 illustrates the job setting information and print instructions included in the preview job. The job setting information (JDF)1201 includes10 records inFIG. 12, whose item names (indices) and their contents are delimited by tabs, and respective records are given as a text file delimited by, e.g., line feed codes. As the contents of the records, the job setting information (JDF)1201 includes ajob type1201aindicating a type, i.e., preview or print, a job name (job ID)1201b, and print settings copied from the print setting information.
• In a Windows® printing system, since the settings set by the print settings on a printer driver are applied to the entire job, one setting data is generated for the entire job like thejob setting information1201.
• However, as for print instructions defined by PDL commands or the like, the settings can be changed in the middle of the job like L3 is A5 portrait, L4 is A4 landscape, L5 is A4 portrait, and so forth after L1 and L2 starting from A4 portrait.
• Preview information1001 inFIG. 10 is an example of preview information (JDFP) generated by theprinter2000 which receives thejob setting information1201 and print instructions (1202 to1206). The preview information includes the job setting information and physical page information. The physical page information includes finishing information indicating finishing processing such as stapling or the like which appears on each physical page, and configuring logical page information which includes a layout of logical pages that configure that physical page.
• The implication of thepreview information1001 is expressed bypages1002,1003,1004, and1005. That is, L1, L2, L3, L4, and L5 are assigned to respective 2-up divided regions on the two faces of A3 landscape paper sheets. In this way, using the preview information, output materials to be printed can be re-configured. In this case, the configuringlogical page information1010 should be noted. In this information, the printer which generates the preview information describes a layout of logical pages. That is, this information includes logical page IDs, sizes, rotation angle, sizes after scaling (or scaling factors), reference position coordinates, and the like of logical pages included in one physical page. With reference to this configuring logical page information, the same physical page as that to be printed by the printer can be re-configured.
• In addition, the preview information includes staple position information, blank page determination information, and accounting determination information for each page. The staple position information is referred to so as to re-configure the staple positions, and the blank page determination information is referred to so as to indicate the presence/absence of an image in a page.
• On the other hand,preview information1301 inFIG. 13 is also an example of preview information (JDFP) which is generated by the printer that receives thejob setting information1201 and print instructions (1202 to1206) inFIG. 12 and is different fromFIG. 10. Unlike thepreview information1001 inFIG. 10, the rotation angles of logical pages included in configuringlogical page information1310 express that images on the reverse face are upside down to those on the obverse face. Also, the preview information represents that an L4 page has a layout which is reduced in scale to the width of an A4 sheet in the landscape direction.
• In this way, the printer generates preview information that includes information of the layout of logical pages and finishing processing which are to be made according to the interpretation of the job setting information for each printer.
• Job setting information1801 inFIG. 18 is print instruction information generated when the previewer that receives thepreview information1001 changes the print settings on the reverse face of the first page to those on the reverse face of the first page in thepreview information1301. The settingchange editor307 generates job setting information and print instructions shown inFIG. 18 for a physical page whose settings have been changed, and transmits them to the printer driver. The printer driver converts these print instructions into PDL commands, and transmits the converted commands to the printer. In the example ofFIG. 12, the printer driver converts thejob setting information1201 and print instructions associated with L3 and L4 pages into PDL commands, and transmits them to the printer. The printer stores the received difference to be merged with the already stored print data, and generates new preview information. The printer then transmits the new preview information to thehost computer3000. After that, theprinter2000 executes RIP processing to generate image data and stores the generated image data. The difference is merged with data of the stored job.
• Amessage1901 inFIG. 19 indicates a print cancel instruction generated by thepreviewer306 which receives thepreview information1001. The print cancel instruction includes a job type and the job ID to be canceled. If the job type inFIG. 19 is changed to “print”, a print instruction when the print settings are not changed is generated.
• In this way, the output results of printers are of great variety depending on models, manufacturers, and the like, even if the application outputs identical data with identical print settings. According to this embodiment, a perfect preview that reflects different operations depending on models can be implemented.
• Furthermore, since print instructions are already sent to the printer upon preview, the time required from determination of print processing to the end of the print processing can be shortened.
• That is, according to the print system of this embodiment, an accurate preview display which reflects the states of output materials by the printer can be implemented. Furthermore, the user is allowed to change the print settings while displaying a preview window, and the changed print settings can be accurately reflected in the preview and printouts.
• Note that the present invention may be applied to either a system constituted by a plurality of devices (e.g., a host computer, interface device, reader, printer, and the like), or an apparatus consisting of a single equipment (e.g., a copying machine, facsimile apparatus, or the like). The objects of the present invention are also achieved by supplying a recording or storage medium, which records a program code of a software program that can implement the functions of the above-mentioned embodiments to the system or apparatus, and reading out and executing the program code stored in the storage medium by a computer (or a CPU or MPU) of the system or apparatus. In this case, the program code itself read out from the storage medium implements the functions of the above-mentioned embodiments, and the storage medium which stores the program code constitutes the present invention.
• The present invention also includes a case wherein the functions of the above-mentioned embodiments are implemented not only by executing the readout program code by the computer but also by some or all of actual processing operations executed by an operating system (OS) running on the computer on the basis of an instruction of the program code. Furthermore, the present invention is applied to a case wherein the program code read out from a storage medium is written in a memory of an expansion card or a function expansion unit which is inserted in or connected to the computer. In this case, the functions of the aforementioned embodiments are implemented by some or all of actual processes executed by a CPU or the like arranged in the function expansion card or unit based on the instruction of that program code.
• While the present invention has been described with reference to exemplary embodiments, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.
• This application claims the benefit of Japanese Patent No. 2006-068272, filed Mar. 13, 2006, which is hereby incorporated by reference herein in its entirety.

Claims (5)

1. A printer apparatus comprising:

a reception unit adapted to receive a print job from a host apparatus;

a preview information generation unit adapted to generate, when a job type corresponding to the printer control commands is preview, preview information which indicates layouts of logical pages and finishing processing for respective physical pages to be printed in accordance with job setting information and print data included in the print job; and

a transmission unit adapted to transmit the preview information to the host apparatus.

2. The apparatus according toclaim 1, further comprising:

a storage unit adapted to store, when the job type is preview, the job setting information and the print data included in the print job received by said reception unit;

a rendering unit adapted to generate image data for respective physical pages based on the print setting information and the print data;

an image storage unit adapted to store, when the job type is preview, the image data generated by said rendering unit; and

a merge unit adapted merge, when a job identifier corresponding to the print job received by said reception unit matches a job identifier of a job stored in said storage unit, the job setting information and the print data included in the received print job with already stored job setting information and print data.

3. A printer apparatus comprising:

a reception unit adapted to receive print job from a host apparatus;

a preview information generation unit adapted to generate, when a job type corresponding to the print job is preview, preview information which indicates sizes, orientations, and scaling information of configuring pages in accordance with job control information and print data included in the print job; and

a transmission unit adapted to transmit the preview information to the host apparatus.

4. The apparatus according toclaim 3, further comprising:

a storage unit adapted to store images based on the print job received by said reception unit; and

a print unit adapted to print image data stored in said storage unit in response to a print designation from the host apparatus.

5. A printer apparatus comprising:

a reception unit adapted to receive print job from a host apparatus;

a generation unit adapted to generate, when a job type corresponding to the print job is preview, preview information and image data in accordance with the print job;

a transmission unit adapted to transmit the preview information generated by said generation unit to the host apparatus;

a storage unit adapted to store the image data generated by said generation unit; and

a print unit adapted to print the image data stored in said storage unit in response to a print designation from the host apparatus.

Images