WO2002008861A2

WO2002008861A2 - A preflight system and method for categorizing errors in a print file

Info

Publication number: WO2002008861A2
Application number: PCT/US2001/023134
Authority: WO
Inventors: Joseph Schorr; Scott Franklin; Todd Whitaker; Tara E. Starr; Brooks Brown; Blake L. Sliter; Raymond J. Marshall; James Jardee-Borquist; Francesco Buzziglio
Original assignee: Creativepro.Com, Inc.
Priority date: 2000-07-26
Filing date: 2001-07-23
Publication date: 2002-01-31
Also published as: AU2001277095A1; WO2002008861A3

Abstract

A preflight system having a printer profile database containing a first list of problem document elements classified in a first category and a second list of problem document elements classified in a second category. The system also has an analyzer that compares document elements from a print file provided by a print buyer with the problem document elements in the first list and the second list to identify problem document elements occurring in the print file, and compiles a categorization list of the problem document elements occurring in the print file that identifies the category for one or more of the problem document elements occurring in the print file. The analyzer may then provide the categorization list to the print buyer, the print vendor, or both. In particular, the analyzer may post the categorization list to a Web page accessible to the print buyer and the print vendor. Alternately or additionally, the analyzer may provide the categorization list to the print vendor as XML data.

Description

A Preflight System And Method For Categorizing Errors In A Print File

Related Application Information

This application is a continuation-in-part application of copending U.S. Patent Application No. 09/625,737, entitled "A Preflight System That Provides A Universal Resource Locator Address Associated With A Detected Print File Error," filed on July 26, 2000, and naming Raymond J. Marshall as inventor.

This application is related to (1) the copending U.S. Patent Application No. 09/625,737, entitled "A Preflight System That Provides A Universal Resource Locator Address Associated With A Detected Print File Error," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (2) the copending U.S. Patent Application No. 09/626,086, entitled "A Preflight System That Preflights Print Files On A Pass-Fail Basis," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (3) the copending U.S. Patent Application No. 09/626,088, entitled "A Preflight System That Employs Inspector Programs Specific To A Print File Type," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (4) the copending U.S. Patent Application No. 09/625,738 entitled "A Preflight System Having A Print Buyer Interface Provided Through A Print Vendor," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference (5) the copending U.S. Patent Application No. 09/626,089, entitled "A Preflight System That Allows A Print Buyer To Employ Print Profiles From A Plurality Of Print Vendors," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (6) the copending U.S. Patent Application No. 09/626,093, entitled "A Preflight System That . Flags Specific Print File Errors For Review By A Print Vendor," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (7) the copending U.S. Patent Application No. 09/626,414 entitled "A Preflight System That Charges A Fee Each Time A Print Buyer Uses The System To Preflight A Print File," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (8) the copending U.S. Patent Application No.

09/625,736 entitled "A Preflight System That Automatically Forwards A Preflighted Print File To A Print Vendor For Printing," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (9) the copending U.S. Patent Application No. 09/626,413 entitled "A Method Of Preflighting That Provides A Universal Resource Locator Address Associated With A Detected Print File Error," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (10) the copending U.S. Patent Application No. 09/626,411 entitled "A Method Of Preflighting Print Files On A Pass-Fail Basis," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (11) the copending U.S. Patent Application No. 09/625,740 entitled "A Method Of Preflighting A Print File That Employs Inspector Programs Specific To The Print File Type," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (12) the copending U.S. Patent Application No. 09/625,742 entitled- "A Method Of Preflighting Using A Print Buyer Interface Provided Through A Print Vendor," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (13) the copending U.S. Patent Application No.

09/625,731 entitled "A Method Of Preflighting Where A Print Buyer May Employ Print Profiles From A Plurality Of Print Vendors," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (14) the copending U.S. Patent Application No. 09/625,743 entitled "A Method Of Preflighting That Flags Specific Print File Errors For Review By A Print Vendor," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (15) the copending U.S. Patent Application No. 09//625,741 entitled "A Method Of Preflighting That Charges A Fee Each Time A Print Buyer Preflights A Print File," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (16) the copending U.S. Patent Application No. 09/625,739 entitled "A Method Of Preflighting Including Automatically Forwarding A Preflighted Print File To A Print Vendor For Printing," filed on July 27, 2000, and naming Raymond J. Marshall as inventor, which application is incorporated entirely herein by reference; (17) A Preflight System And Method For Preflighting Print Files According To Profile Information That Cannot Be Modified By The Print Buyer, filed concurrently herewith, and naming Raymond J. Marshall, James Jardee-

Bordquist and Scott Franklin as inventors, which application is incorporated entirely herein by reference; (18) A Preflight System And Method Employing A User Interface That Can Be Modified Independent Of The Preflight System, filed concurrently herewith, and naming Raymond J. Marshall, James Jardee-Bordquist and Scott Franklin as inventors, which application is incorporated entirely herein by reference; (19) A Preflight System And Method For Bundling Preflight Results For A Print File With The Preflighted Print File, filed concurrently herewith, and naming Raymond J. Marshall, James Jardee-Bordquist and Scott Franklin as inventors, which application is incorporated entirely herein by reference; and (20) A Preflight System And Method For Monitoring A Volume Of Preflight Processes, filed concurrently herewith, and naming Raymond J. Marshall, James Jardee-Bordquist and Scott Franklin as inventors, which application is incorporated entirely herein by reference.

Background Of The Invention

Field Of The Invention This invention is directed to a preflight system that allows a print buyer to submit a print file for preflighting from a remote user interface. More particularly, the invention is directed to a method and system that allow a print buyer to seamlessly integrate a preflight process into its workflow with a print vendor, by, for example, preflighting a print file via a remote preflight system using an interface associated with the print vendor.

Background Of The Invention Preflighting is the process of reviewing print information for errors or possible printing problems before actually printing the information. This process is important because a printing press can be very expensive to set up and run. Further, a print run may require hundreds of thousands of sheets of paper, special binding procedures, etc. If errors or problems in a print job are not caught before the printing job is completed, it can be very costly to reprint the job. Currently, print buyers who wish to have something printed will submit it in digital form to a print vendor (e.g., a printer with a printing press or a print broker who passes the item on to a printer with a printing press). In theory, this allows the print file containing the item to be easily preflighted by computer analysis, but this has not worked out in practice. While the print vendor can preflight the print file, the print vendor cannot correct all of the errors that are detected. Instead, to correct most errors, the print vendor must either return the print file to the print buyer or obtain additional information from the print buyer. This can significantly delay printing of the item.

The print buyer, on the other hand, may not be aware of the need to preflight a print file before submitting it to a print vendor. Even if a print buyer is sophisticated enough to appreciate the need for preflighting, the preflighting process is still time consuming for the print buyer. The print buyer must obtain a preflighting program, preflight the print file, and correct any detected errors before submitting the print file to a print vendor. If the print buyer obtains the preflighting program from a source other than the print vendor being used by the print buyer, then the preflighting program may not recognize possible print errors that are specific to the print vendor. On the other, if the print buyer obtains its preflighting program from one print vendor, then the program may not recognize print errors specific to other print vendors. Instead, the print buyer must obtain new preflighting criteria for each new print vendor it employs.

Summary Of The Invention Accordingly, there is a need for a preflight system that seamlessly integrates into the print buyer's workflow. Advantageously, some embodiments of the invention allow a print buyer to access a preflight system using an interface provided through a print vendor. Thus, in the process of working with a print vendor, a print buyer can easily preflight print files prior to printing. Various embodiments of the invention may further allow the preflight system to pass error free print files along to the print vendor, or to pass print files having correctable errors along to the print vendor with a list identifying the correctable errors for the print vendor. Still other embodiments of the invention may pass all preflighted files along to the print vendor and/or the print buyer. These embodiments may further categorize each error discovered in a preflighted file according to its severity, and pass a list of the categorized errors onto the print vendor and/or the print buyer, either with or without the preflighted print file itself.

In accordance with some embodiments of the invention, a preflight system provides an interface Web page accessible through a print vendor's Web site, so that a print buyer can access the preflight system through the print vendor's Web site. Upon interfacing with the preflight system, the system provides inspector modules to the print buyer's client machine. These inspector modules inspect the print file, and convey the detected document elements back to the analyzer of the preflight system. The analyzer compares the detected document elements with a list of elements in one or more selected printer profiles provided by the print vendor, to identify any of the document elements that may present a problem during printing. The analyzer then compiles a list of error messages associated with the identified document elements that can be reviewed by the print buyer and/or the print vendor. By accessing the preflight system through the print vendor, the print buyer is not hardwired to one particularly vendor. Further, as will be understood by reviewing the description of the preferred embodiments below, the print buyer can employ the preflight system according to the invention through potentially any print vendor.

Brief Description Of The Drawings Fig. 1 A illustrates a block diagram of the preflight system according to one embodiment of the invention.

Fig. IB illustrates a block diagram of the plug-in library shown in Fig. 1 A. Figs. 2A and 2B illustrate a method of preflighting according to one embodiment of the invention. Fig. 3 A shows a print vendor's Web site including a link to an initial interface Web page according to one embodiment of the invention.

Fig. 3B shows a generic organization's Web site including a link to an initial interface Web page according to one embodiment of the invention.

Figs. 4 and 5 show two file submission interface pages according to one embodiment of the invention.

Fig. 6 illustrates the contents of a conventional print file.

Fig. 7A shows an error listing Web page according to one embodiment of the invention. Fig. 7B shows another error listing Web page according to one embodiment of the invention. Fig. 8 illustrates an error listing in XML provided to the print vendor according to one embodiment of the invention.

Fig. 9 shows a Web page used to bundle preflight results with the preflighted file into a single archive file according to one embodiment of the invention.

Detailed Description Of The Preferred Embodiments Turning now to Fig. 1 A, this figure shows the components of the preflight system 101 according to one embodiment of the invention. The preflight system 101 includes a controller 103, an interface 105, an enabler 107, a plug-in library 109, an analyzer 11 1 and a memory 1 13. Each of these components may be embodied on a single computer server, or may be embodied on a system of interconnected computer servers. Also, as will be explained in detail below, the enabler 107 and the plug-in library 109 have modules that are downloaded to a user's computer for operation on that local machine. The preflight system 101 operates according to printer profile data stored in the printer profile database 115. While the printer profile database 115 is illustrated as being separate from the preflight system 101 in Fig. 1 A, those of ordinary skill in the art will appreciate that the printer profile database 1 15 can alternately be incorporated into the preflight system 101.

As will be seen from Fig. 1A, the preflight system 101 may be used by both a plurality of print vendors 117 A- 117D and by a print buyer 119. The print vendors 117A- 117D are companies or organizations that will print information on a medium for the print buyer 119, while the print buyer 119 may be an individual or organization that desires to have information professionally printed onto a medium. Typically, the print buyer 119 will provide a print file, containing the information to be printed, to one of the print vendors 1 17 for printing. The print buyer 119 may transmit the print file to the print vendor 117 over a network, such as the Internet. Alternately, the print buyer 119 may submit the print file to the print vendor on a memory storage medium, such as a CD-ROM or magnetic media disc (e.g., a Zip disc).

For most preferred embodiments of the invention, the print buyer 119 will have (or have access to) a client machine 121 that is capable of receiving operational files (e.g., plug-in programs) over a network, such as the Internet. More particularly, the client machine 121 will also preferably be able to run a browser program 123, such as Microsoft Explorer or Netscape Navigator, for retrieving information from a network such as the Internet.

The components of the preflight system 101 will now be described in detail. As will be appreciated by those of ordinary skill in the art, the controller 103 coordinates the operation of the other components 105-113 and the transfer of data between these components 105-113. The interface 105 provides an interface between the preflight system 101 and at least the print buyer 119. In some preferred embodiments of the invention, the interface 105 provides an initial interface page (such as an HTML "Web" page, to be described in detail later) for each of print vendors 1 17A-1 17D. The print buyer 119 can then use its browser 123 to download an appropriate enabler module 107A and various plug in programs 109A-109Θ through the interface page of the print vendor 1 17 that the print buyer 119 is employing to print the print file.

According to some embodiments of the invention, the enabler 107 includes enabler modules 107A that function to provide both a user interface for the print buyer 1 19 and as a "plug-in" manager for the client machine's browser 123. More specifically, the enabler 107 includes enabler modules 107A that can be downloaded to the client machine 121 to plug into the browser 123. As is well known in the art, a "plug-in" program is a supplemental program that works in conjunction with a basic application to add additional functionality to that basic application. In some preferred embodiments of the invention, the enabler 107 includes four different enabler modules 107 A, one for each type of commonly used browser program (i.e., the first for use with Microsoft Internet Explorer running on the Microsoft Windows operating system, another for use with Netscape Navigator running on the Microsoft Windows operating system, the third for use with Microsoft Internet Explorer running on the Apple Macintosh operating system, and the fourth for use with Netscape Navigator running on the Apple

Macintosh operating system). Of course, those of ordinary skill in the art will appreciate that the enabler 107 can have more or fewer enabler modules 107A depending upon the intended market for the preflight system 101.

Once the enabler module 107A for browser 123 has been downloaded to the client machine 121 of a print buyer 1 19, the downloaded enabler module 107A plugs into the browser 123 to provide a plug-in interface. As will be discussed in detail below, the enabler module 107A allows any of the multiple plug-in modules 109A-109Θ of the same operating system type to plug into the browser 123. According to some embodiments of the invention, the enabler module 107A may also cooperate with the interface 105 to provide the print buyer 119 with interface Web pages. (According to alternate embodiments of the invention, however, this function may be performed by another plug-in module stored in the plug-in library 109, such as the plug-in module 109B.) As will also be discussed in detail below, the print buyer 119 uses this initial interface page to employ the preflight system 101 to preflight print files. With some embodiments of the invention, the enabler module 107A may additionally be used to identify the file type of each print file submitted by the print buyer 119 for preflighting. As seen in Fig. IB, the plug-in library 109 includes at least one set of inspector modules 109A] - 109A_n. Preferably, each inspector module 109A is designed to scan through a particular file type for document elements (i.e., the elements that make up the print file). Thus, each module 109A corresponds to a file type that can be preflighted by the preflight system 101. For example, inspector module 109Aj may be a module for scanning QuarkXpress files, while 109A may be a module for scanning Adobe Photoshop files and 109 A₃ may be a module for scanning Microsoft Word files. The enabler module 107B downloads specific inspector modules 109A from the plug-in library 109 to the client machine 121 that correspond to the print file types submitted by the print buyer 119 for preflighting. For example, if the print buyer 119 submitted a QuarkXpress print file for preflighting, then the enabler module 107A would download the inspector module 109Aj (specific to scanning QuarkXpress files) from the plug-in library 109 to scan the print file. Further, the plug-in library 109 will provide as many different inspector modules 109A as necessary to completely scan the print file. Thus, if the print file is a QuarkXpress file containing an embedded Adobe Photoshop file (or if it contains a link to an Adobe Photoshop file), the enabler module 107A will download both the inspector module 109A] for scanning the QuarkXpress file and the inspector module 109A₂ for scanning the embedded (or linked) Adobe Photoshop file.

Preferably, the inspector modules 109A operate as plug-ins to the browser 123. As is known in the art, however, each browser program requires a specific type of plug-in format (e.g., Microsoft Internet Explorer may require an ActiveX plug-in format). Thus, the plug-in library 109 typically would need several set of inspector modules 109A] to 109A_N, one for each type of browser 123 that might be employed on the client machine 121. Instead, as previously noted, the enabler 107 includes an enabler module 107A for each type of browser 123 that might be employed by the print buyer 119. The enabler module 107A corresponding to the browser 123 then acts as a plug-in interface between that browser and the inspector modules 109Aj to 109AN. In particular, the enabler module 107A allows any inspector module 109A that is compatible with the operating system of the client machine 121 to be used with the browser 123. Thus, one embodiment of the preflight system 101 may employ only two sets of inspector modules 109A] to 109 AN: one set for a client machine 121 using the Microsoft Windows operating system, and one set for a client machine 121 using the Apple Macintosh operating system. Of course, those of ordinary skill in the art will appreciate that other embodiments of the invention can include additional sets of inspector modules 109Aι to 109 A_N for other operating systems, such as Unix or Linux.

As seen in Fig. IB, the plug-in library 109 may include a variety of other plug-in modules 109B-109Θ for performing other functions associated with the preflight system 101. For example, as previously noted, instead of the enabler module 107A retrieving an initial interface Web page for submitting a document for preflighting, plug-in module 109B may perform this function. Further, other plug-in modules 109C-109Θ may carry out other functions (particularly interface functions), such as allowing the print buyer 119 to submit documents for preflighting by dragging and dropping them onto the initial interface Web page, as will be discussed in detail below. Preferably, like the plug-in modules 109A, the plug-in modules 109B-109Θ cooperate with the enabler module 107 A. The different groups of plug-in modules 109B-109Θ may include any combination of plug-in modules, such as different versions of the same module for use with different operating systems (e.g., modules 109B and 109Θ in Fig. IB), different modules for use with a single operating system (e.g., modules 109D in Fig. IB), a single module (e.g., module 109C in Fig. IB), etc.

Returning now to the inspector modules 109A, an inspector module 109A that has been downloaded to the client machine 121 scans through the designated print file, identifies document elements in the print file, and then transmits the identified document elements to the preflight system 101 (i.e., to the analyzer 1 11) for analysis. With some embodiments of the invention, the inspector modules 109A create a memory -file on the client machine 121 for storing detected document elements. The inspector module 109A can then periodically transmit the contents of the memory file to the analyzer 111, or alternately wait until the scan of the print file has been completed to transmit the contents of the memory file to the analyzer 111. This technique reduces the number of transmissions required between the client machine 121 and the preflight system 101. With other preferred embodiments of the invention, however, the inspector modules 109 A immediately relay the detected document elements to the preflight system 101, without storing any of the document elements in the memory of the client machine 121. This technique is particularly advantageous in that it can significantly reduce the time required to provide the analyzer 111 with the document elements from the print file. This technique also uses less memory in the client machine 121 , as print files are often quite large. The analyzer 11 1 works in conjunction with information from the printer profile database 115 to recognize particular document elements from the print file being preflighted. Each of print vendors 1 17A-1 17D sets up one or more printer profiles in the printer profile database 115. These profiles define the document elements that the print vendor 117 believes may present a problem when it goes to print the print file. For example, print vendor 1 17A may not have a printing press capable of printing a RGB (red-green-blue) color image. The print vendor 1 17A may then have its printer profile designate any document element indicating a RGB color image as an erroneous document element. If print vendors 117B and 117C both have presses capable of printing a RGB color image, then the printer profiles for these vendors might not designate RGB color image document elements as erroneous. Similarly, if print vendor 1 17C does not have a press capable of printing a resolution higher than 800 dpi (dots per inch), then vendor 1 17C may set up its printer profile to indicate that any document elements representing a resolution higher than 800 dpi should be treated as erroneous document elements. If print vendors 117A and 117B are capable of higher resolutions, however, then their printer profiles may not indicate that document elements representing a resolution higher than 800 dpi are erroneous.

Of course, those of ordinary skill in the art will appreciate that more sophisticated printer profiles can be employed. For example, a printer profile could indicate that a particular document element is a problem if, and only if, it immediately follows another specific document element. Thus, according to other embodiments of the invention, printer profiles could be set up to signal an error for any logical combination of document elements (or absence of document elements).

In some preferred embodiments of the invention, a printer profile is formed by a database cross-referencing each erroneous document element (i.e., each document element, logical combination of document elements, or absence of document elements designated by the print vendor to be treated as an erroneous document element) against an error message selected by the print vendor 117. Thus, two different print vendors 117 may provide different error messages for the same document element. For a document element representing a resolution of 1200 dpi, for example, print vendor 117C may provide an error message indicating that it cannot print at a resolution higher than 800 dpi. Print vendor 117B, on the other hand, may associate this document element with an error message saying that it will require an additional two weeks over its normal turnaround time to print an image with a resolution of 1200 dpi. Some preferred embodiments of the invention may include a universal resource locator (URL) address in the error message. As will be explained in detail below, this allows a print vendor 117 to direct a print buyer 119 to a Web page particularly designated (or provided) by the print vendor 1 17 to address the erroneous document element.

Still further, each print vendor 117 may individually categorize, in advance, each possible erroneous document element according to its severity for that print vendor. For example, print vendor 117 may categorize a document element representing a resolution of 1200 dpi as a minor error, and categorize a document element calling for a particular font type (i.e., Times New Roman) as a "fatal" error. Another print vendor, however, may categorize both documents elements as a minor error. Of course, those of ordinary skill in the art will appreciate that a variety of classification hierarchies can be used to categorize erroneous document elements. For example, some embodiments can allow a print vendor to designate three or more different levels of severity, while other embodiments can categorize errors according to criteria other than severity. As will be explained in detail below, this categorization information can be displayed to the print buyer instead of or in addition to other error messages. Further, this categorization information can alternately or additionally be transmitted to the print vendor, to allow the print vendor to decide whether or not to accept the preflighted print file for printing.

Thus, the printer profiles according to the invention allow individual print vendors to develop printer profiles tailored to their specific printing capability. Moreover, with the invention, a single preflight system can employ different profiles from different print vendors. With some embodiments of the invention, each print vendor can even maintain more than one printer profile in the printer profile database 115. For example, a print vendor 117 with five different presses could set up a printer profile for each press. Print buyer 119 could then preflight a print file using all five printer profiles for that vendor, to determine which of the vendor's presses required the fewest (or easiest) changes to the print file before printing. Alternately, if the print vendor 117A changed the configuration of its press based upon time (e.g., each week) then the print vendor 117A could choose to have four different profiles, one for each week of the month. According to some preferred embodiments of the invention, the print vendors 1 17 can access the print profile database 115 at any time to immediately change their respective printer profiles, without otherwise involving the preflight system 101. This allows print vendors 1 17 the maximum flexibility to modify their print profiles to correspond with the current set-ups of their presses. More significantly, the print vendors 117 do not need to contact or interact with the print buyer 1 19 in any way in order to immediately make their profiles available for use by the print buyer 119. With some embodiments of the invention, the print buyer 119 cannot modify a print vendor's printer profile or profiles. For still other embodiments of the invention, the print buyer 1 19 may not even have access to specific information in a print vendor's printer profile or profiles.

As previously noted, the analyzer 1 11 works with the printer profile database 115 to recognize particular document elements from the print file being preflighted. More particularly, the analyzer 11 1 compares each document element retrieved by the inspector module or modules 109A with the documents elements listed in the printer profile. When the analyzer 111 recognizes a retrieved document element as one listed as erroneous in the printer profile, the analyzer 11 1 obtains the error message associated with the erroneous document element, and stores that error message in memory 113. It should be noted that, with the preflight system 101 according to the invention, the analyzer 111 can be generic to all print file types. That is, because the analyzer 1 11 simply reviews the document elements identified by the inspector modules 109 A, a single analyzer 1 1 1 can be employed to analyze any type of print file.

After the inspector or inspectors 109A have finished scanning through a print file, and the analyzer 111 has stored all of the relevant error messages in memory, the interface 105 may take several different courses of action, depending upon the embodiment of the invention. ^• For example, the analyzer 111 may post the list of error messages to a Web page that can be accessed by the print buyer 119. If the print file contains no errors, then the analyzer 111 may instead simply forward the print file to the print vendor 117 selected by the print buyer. Still further, if the selected print vendor 117 can correct the noted errors, the analyzer may provide both the print file and the list of errors directly to the print vendor 117. With other embodiments of the invention, the analyzer 111 (through the interface 105) may deliver the errors and/or the associated error messages to a Web site accessible to both the print buyer 119 and the print vendor 117. According to still other embodiments of the invention, the analyzer 111 may provide a listing of the noted erroneous document elements and/or a listing of the associated error messages to the print vendor 1 17 so that the print vendor 1 17 can decide whether it wants to accept the print file for printing. For example, with some of these embodiments, the analyzer 1 1 1 can provide an XML (extensible Markup Language) listing of the identified erroneous document elements and/or associated error messages to the print vendor 1 1 over a network, such as the Internet. This allows the print vendor 117 to then automatically decide (e.g., by a server computer that receives the XML listing) whether or not to accept or obtain the print file for printing. The print vendor 1 17 can also use this information to take some other action, such as, for example, providing the print buyer 119 with special instructions, accept the print file for printing with a disclaimer, refer the print buyer 119 to another print vendor 117, etc. With some of these embodiments of the invention, the error messages may include a classification scheme, as described above, to categorize each error, e.g., according to its severity, before it is sent to the print vendor 117. This categorization information may facilitate the print vendor's review of the noted errors in the print file.

With yet other embodiments of the invention, after the print buyer 1 19 has accessed the Web site listing the detected erroneous document elements and/or associated error messages, the print buyer 119 can save some or all of the information on the Web site for later submission to the print vendor 117. In particular, as will be explained in greater detail below, some embodiments allow the print buyer 119 to "collect" the error listing from the Web site with the preflighted print file (or files) into a single archive. For example, the error listing from the Web site can be saved as a results file, and the results file and the preflighted print file (or files) can be combined into a single, compressed archive file (e.g., as a .zip or a .sit file). This archive file can then be easily submitted to the print vendor 117, by, e.g., transmission over a network such as the Internet, direct transmission to the print vendor 117, downloading to a portable storage device such as a disk and for delivery to the print vendor 117, etc. The operation of the preflight system according to one embodiment of the invention will now be described in detail with reference to Figs. 2A and 2B. As shown in Fig. 2A, in step S201 a print buyer 119 may initiate the use of the preflight system 101 by accessing the network site (e.g., an Internet Web site) of one of the print vendors 1 17. For example, print vendor 1 17A may maintain an Internet Web site 301 as shown in Fig. 3 A. The Web site may include a number of linked Web pages 303-309 maintained by the print vendor 117A. The Web site 301 may also include a link to an initial interface Web page 31 1 maintained by the interface 105 on behalf of the print vendor 117A.

That is, the interface 105 may maintain a Web page 311 that appears to be associated with the print vendor 1 17A (e.g., it may have the print vendor's 1 17A logo) but which is actually the initial interface page for accessing the preflight system 101. Alternately, one of the Web pages 303-309 may server to "frame" the initial interface page 311, such that the initial interface Web page 311 appears as a portion of one of the Web pages 303-309. Both the use of links and framing are known to those of ordinary skill in the art. These features allow the print buyer 1 19 to receive a preflight system user interface tailored to a particular print vendor 117 (or to another particular organization, as will be explained in detail below).

For example, a print buyer 1 19 accessing the preflight system 101 through a Web site of print vendor 1 17A may receive an user interface Web page (or pages) having information relating to only print vendor 117A (e.g., the print vendor's name, logo, contact information, etc.). The same print buyer 1 19 may then receive a different user interface Web page (or pages) for the preflight system 101 through the Web site of print vendor 117B. This different user interface Web page (or pages) may contain information relating to only print vendor 117B (e.g., the print vendor's name, logo, contact information, etc.). To the print buyer 119, it appears as if each preflight operation is specific to the print vendor 117 through which the preflight system 101 is accessed. In actuality, however, the print buyer 1 19 is accessing the same preflight system 101 each time. Thus, the print buyer 119 may access the preflight system 101 through the Web site 301 of the print vendor 1 17 A, possibly without even realizing that the preflight system 101 is separate from the Web site 301 of print vendor 117A.

Further, some embodiments of the invention may allow the print vendor 117 to control the appearance and even the operation of the preflight system user interface received by the print buyer 119, the print vendor 117. For example, print vendor 117A may set up its user interface Web page (or pages) to employ a "drag-and-drop" system that allows the print buyer 119 to submit print files for preflighting simply by dragging the print file onto the Web page and then dropping the file. Print vendor 117B, on the other hand, may instead configure its user interface Web page (or pages) to require the print buyer 119 to type in the file name for preflighting in a particular input field. Each print vendor 117 can then tailor its interface Web page or pages to the desires of its customers. Still other embodiments of the invention may allow the print vendor to maintain its own interface Web page 31 1 for interfacing with the preflight system 101. The print vendor 117 can maintain all of the functions of the interface Web page 31 1 , including downloading the necessary inspector modules 109 to the client machine 121 of the print buyer 1 19 and receiving the document elements identified in the print file by the inspector modules 109. The print vendor's interface Web page 311 can then post the received document elements to the interface 105 of the preflight system 101 for analysis by the analyzer 111. After the analyzer 111 has analyzed the document elements, the preflight system 101 can then post the preflight results (i.e., the erroneous document elements and/or associated error messages) back to the print vendor's interface Web page 311, from where they can subsequently be communicated to the print buyer 119. Thus, the print vendor 1 17 can maintain its own interface Web page 311 for allowing the print buyer 119 to employ the preflight system 101.

In the above-described embodiments, the Web site 301 is maintained by a single print vendor 117 and is linked to an interface Web page 311 that can be individually personalized for the print vendor 117. As shown in Figure 3B, however, a generic organization may maintain a link (or a framing connection) to an interface Web page 311 (or Web pages) that can be individually personalized for the organization. Alternately, as described above, the organization may maintain its own personalized interface Web page 31 1 (or Web pages) to the preflight system 101. The United States Army, for example, may employ a number of different print vendors 1 17, but still desire to provide its members with a standard user interface Web page (or pages) for preflighting print files. Thus, the Army could maintain the Web site 301' with a link to an interface Web page 311 ' (or Web pages) that can be individually personalized for that organization, or maintain its own individualized interface Web page 311 ' (or pages). By consistently presenting a single preflighting interface for a number of different print vendors 117, an organization can reduce training and mistakes caused by unfamiliarity with a different interface. As will be explained in detail below, a print buyer 119 (i.e., a member of the organization) can use the single interface to select printer profiles for a number of different print vendors 1 17. This selection can then be used to determine which of the plurality of print vendors 117 may receive the preflighted print file for printing. Further, the Web site 301' for the organization can maintain links to a number of different Web pages 313 '-319' provided by each print vendor 117, to allow the organization to easily transmit the preflighted print file to a desired print vendor.

Returning now to Figure 2, a print buyer 119 initiates the preflight process by using the browser 123 to retrieve the initial interface Web page 311. Thus, the browser 123 acts an in interface program for interfacing with the preflight system 101. The initial interface Web page 311 references the appropriate enabler module 107A for use with the browser 123 in step S203. As is known in the art, network browsers, such as Internet Explorer and Netscape Navigator, conventionally allow a Web page to include an HTML (Hypertext Mark-up Language) reference to a "plug-in" software program that operates in conjunction with the browser. If the plug-in has been installed on the client machine, then the reference in the Web page activates the plug-in. If the plug-in has not yet been installed, then the reference prompts the print buyer's browser 123 to install the plug-in. Thus, the reference to the appropriate enabler module 107A in the initial interface Web page 311 can determine if the most recent version of that enabler module 107A has been installed on the client machine 121, and initiates the download of the most recent version of that enabler module 107A to the client machine 121 if it has not.

As previously noted, in some preferred embodiments of the invention, the initial interface Web page 311 is specific to the print vendor 117A. That is, the interface 105 provides an initial interface Web page 31 1 A for the print vendor 1 17A, a different initial interface Web page 31 1 B for the print vendor 117B, still a different initial interface Web page 311C for the print vendor 117C, and yet another different initial interface Web page 311 D for the print vendor 117D.

Accordingly, when the print buyer 119 accesses the preflight system 101 through initial interface Web page 311 A, the system 101 recognizes that the print buyer 119 is interfacing the preflight system 101 through the Web site of the print vendor 117A.

Once the enabler module 107A has been activated to operate with the browser 123, in step S205 the enabler module 107A retrieves (from the interface 105) the file submission interface Web page 401 shown in Fig. 4. (It should be noted that, like the initial interface Web page 311, the file submission interface Web page 401 (and any other interface Web pages) may be individualized to the print vendor 117 through which the interface Web page was accessed.) As discussed above, the enabler module 107A operates as a plug-in management system for the inspector modules 109A. With some embodiments of the invention, however, the enabler module 107A may additionally modify the operation of the browser 123 to implement interface functions for the various interface Web pages provided by the interface 105. For example, the enabler module 107A may modify the operation of the browser 123 to allow a print buyer 119 to submit files for preflighting by "dragging-and-dropping" the print files onto an interface Web page. That is, the enabler module 107A may allow the print buyer 119 to submit a print file to the preflight system 101 simply by moving the icon representing the print file to an interface Web page displayed on the browser 123, and recognize when a file or files have been dropped onto the file submission Web page 401 for preflighting. Alternately, the enabler module 107A may be used only as a plug-in management system for modules 109A-109Θ, and one or more of the plug-in modules 109B-109Θ may implement the interface functions of the preflight system 101.

Thus, after the print buyer 119 has received the file submission interface Web page 401, the print buyer 1 19 can easily designate one or more print files for preflighting simply by dragging and dropping the files onto the file submission interface Web page 401 in step S207. When the enabler module 107A recognizes that one or more files have been dropped onto the file submission interface Web page 401 , the enabler sends a message to the interface 105 indicating the submission of the files, along with the names of the files, in step S209. In response, the interface 105 generates a new file submission interface Web page 401 ' in step S211 , which includes a list 403 of each submitted file, as shown in Fig. 5. The print buyer 1 19 can then continue to submit files for preflighting by dragging and dropping them onto the new file submission interface Web page 401 ' (which creates an updated file submission Web page 401' that includes the new file or files in the list 403). Alternately, in step S213, the print buyer 119 can instruct the preflight system 101 to preflight the print files that have already been submitted by activating button 405 (marked "Continue") on the file submission Web page 401 '.

In some preferred embodiments of the invention, the enabler module 107 A also identifies the file types of the print files to be preflighted, and passes these file types back to the preflight system 101 in step S215. (Again, one or more of the plug-in modules 109B-109Θ may alternately perform this identification function.) For client machines 121 employing the Microsoft Windows operating system, the enabler module 107A can easily identify the print file type by using the three-character suffix attached to the file name. If the client machine 121 is using an Apple Macintosh operating system, then the enabler can detect the print file type using the Macintosh creator code, which is a property of the file. Those of ordinary skill in the art will appreciate that other types of file identification techniques can be employed by the enabler 107A to identify the files submitted for preflighting. Further, it will be understood that another portion of the preflighting system 101 (e.g., the analyzer 111), other than the enabler module 107A, can identify the file type for each submitted print file in step S215. As previously noted, the preflight system 101 can recognize which print vendor 1 17 the print buyer 1 19 is using by the initial interface page 311. Accordingly, in step S217, the controller 103 accesses the print profile database 115 to retrieve the printer profiles designated by the print vendor 117 being used by the print buyer 119. In the particular embodiment described herein, the print buyer 119 is accessing the preflight system 101 through the Web page 311 A maintained for print vendor 117A, so the controller 103 accesses for display the printer profiles set up by the print vendor 117A. For example, if the print vendor 1 17 A has set up three different printer profiles for three different presses, then preflight system 101 preferably displays all three of those printer profiles for selection by the print buyer 119. Alternately, if the print buyer 119 is accessing the preflight system 101 through an initial interface Web page 31 1 ' for a generic organization employing a number of print vendors 117, the controller 103 accesses for display the printer profiles set up by each of the available print vendors. With this arrangement, the print buyer 1 19 can then designate which print vendor 117 will be used to print the print file by selecting a printer profile for that print vendor 117.

While the list of printer profiles may be displayed in a window of the interface Web page 401 (e.g., window 407), the interface 105 may alternately provide the browser 123 with a new interface Web page (not shown) displaying the list of printer profiles. In addition, depending upon the amount of print file information obtained by the enabler module 107 A (or alternate plug-in module), the preflight system 101 may select a printer profile for the print buyer. For example, if the print file is for a special type of print job, then the preflight system 107A may select a printer profile from a print vendor specializing in printing that type of print job.

It should be noted that the list of profiles can be displayed in response to the print buyer 119 activating the button 405 to continue the preflighting process, or, for other embodiments of the invention, in response to the print buyer 119 using another command, such as the command phrase "Choose A Profile" shown in menu 407 on the Web page 401. In step S219, the print buyer 119 selects one or more of the printer profiles to be used during the preflight process. After the print buyer 119 has selected the printer profile or profiles, the plug-in library 109 determines in step S221 which of inspector modules 109A| to 109 AN should be downloaded to the client machine 121 to scan the print file, and ensures that those inspector modules 109A have been installed on the client machine 121. Once the appropriate inspector module 109A has been downloaded to the client machine 121 , in step S223 the inspector module 109A then begins to review each document element of the print file to be preflighted.

As shown in Fig. 6, a print file 601 typically includes a number of document elements. These may include document elements 603 specifying paper size, document elements 605 specifying margins, document elements 607 specifying fonts, document elements 609 specifying text size, etc. The document elements of the print file may also include images, such as the RGB image 611 and the CMYK image 613. The document elements may also include a document element 615 referencing one or more linked images, i.e., image files that are stored in a different file location and that are retrieved when the print file is to be printed.

The inspector modules 109A read through the print file 601 to detect each document element. As previously described, the inspector modules 109A are employed according to the type of file being scanned for print documents. Thus, if the print file being scanned is a file created by Quark Express, then the QuarkXpress inspector module 109Aι is used to scan through the print file, identifying each document element. If, during the process of inspection, the inspector module 109Aι encounters an embedded or linked file of a different type, e.g., a Microsoft Word file, then the inspector module 109A] temporarily stops operation and the inspector module 109 A (for scanning Microsoft Word files) is initiated to scan the embedded or linked Microsoft Word file. If the inspector module 109A₃ for detecting document elements in Microsoft Word files has not previously been downloaded to the client machine 121, then the inspector module 109A₃ is downloaded when the linked or embedded Microsoft Word file is detected. After the inspector module 109A₃ for detecting Microsoft Word files has scanned the linked or embedded Microsoft Word file, it halts operation and reinitiates the operation of the first inspector module 109Aj (for scanning QuarkXpress files) to scan the remainder of the file.

It should be noted that the inspection process is recursive. That is, every inspector module 109A necessary to fully inspect a print file is employed. For example, with the explanation above, if the embedded Microsoft Word file itself had an embedded Adobe

Photoshop file, then, when the inspector module 109A₃ (for scanning Microsoft Word files) recognized the embedded Adobe Photoshop file, it would initiate the inspector module 109 A (for scanning Adobe Photoshop files) to scan the embedded Adobe Photoshop file. This process is employed for each file type required to fully scan the print files submitted by the print buyer 119. In addition, the inspection process is robust. If an inspector module 109A encounters an embedded or linked file type that does not have a corresponding inspector module 109A (i.e., a file type that is unrecognized or for which there is no inspector module 109 A), then the embedded or linked file is simply ignored and the inspector module 109A continues on with its inspection. This prevents the preflighting operation from prematurely stopping when a new or unrecognized file type is in the print file.

As the inspector module or modules 109A detect document elements, the module or modules 109A forward the document elements over the network (e.g., the Internet) to the analyzer 111 for analysis in step S225. As is known in the art, a particular document element may be difficult for a print vendor to process. For example, if the print vendor 117A has a press that can only print sheets with a size of 1 1 x 17/4 inches or smaller, then a document element indicating a paper size of 20 x 25 inches cannot be processed by the print vendor 117A. In addition to particular document elements hat are problems for specific print vendors, a print file may also contain document elements that would be generically difficult for any print vendor 117 to process. For example, if a print file included a link to an image file that does not exist (or which cannot be found), then no print vendor 117 would be able to process the print file with the link to the missing image file.

Accordingly, in step S227, the analyzer 111 reviews each document element retrieved by the inspector modules 109A for document elements that have been specifically identified as problems by the print vendor 117A in its printer profile or profiles that have been selected by the print buyer 119. Further, the analyzer 111 may also recognize generic problems, such as referenced or linked files that are missing, that would be a problem for any print vendor 117A to process.

With one embodiment of the invention, the analyzer 111 compares each document element provided by the inspector modules 109 A with the list of document elements in the printer profile or profiles for print vendor 117A that were selected by the print buyer 119. When the analyzer 111 identifies a listed document element in the print file, it stores the corresponding error message in memory 113 in step S229. After the analyzer 1 1 1 has completed reviewing every document element associated with a print file, the collected error messages may be compiled from memory 113 into an error listing Web page 701, shown in Fig. 7. The interface 105 can then provide this page 701 to the browser 123 for review by the print buyer 119. The print buyer can employ the list 703 of error messages included on the Web page 701 to modify the print file before resubmitting the print file to the print vendor 1 17A, to ensure that the print file can be optimally printed by the print vendor 117A. It should be noted that, if more than one print file is preflighted simultaneously, the Web page 701 may contain an itemized listing of error message corresponding to the errors found in each print file, as shown in Fig. 7. As seen in this figure, the Web page 701 contains preflight results 703A-703C for three different print files. Alternately, the interface 105 may provide multiple error listing Web pages 701 (e.g., one for each preflighted print file).

As was previously noted, an error message for a document element may include a universal resource locator (URL) address designated by the print vendor 1 17A. This URL address (or a link to this URL address) can be displayed on the error listing Web page 701 for use by the print vendor 117A. For example, the URL address can reference a Web page explaining in detail the particular problem that the print vendor 1 17A has with that specific document element. Further, the URL address may reference a Web page for providing detailed information to assist the print buyer 119 in changing or deleting the erroneous document element. Allowing the print vendor 117A to employ a URL address in the error message for its printer profile gives the print vendor 117A still greater flexibility in handling print problems. The print vendor 117A can easily change the content of the Web page addressed by the URL, without modifying its printer profile or disturbing the operation of the preflight system 101. If a print file does not have any errors, then some embodiments of the invention may arrange to have the print file automatically forwarded to print vendor 117A for printing. For example, the enabler module 107A may include additional functionality that allows it to recognize and respond to an error listing Web page 701 that does not actually list any errors. If the enabler module 107 A detects an error listing Web page 701 that does not contain any messages (or, for example, contains a message stating that the print file had no errors), then the enabler module 107A could instruct the browser 123 to retrieve a file transmission Web page from the print vendor 117A. The print buyer 119 could then use this page to submit the preflighted print file to the print vendor 117A. Alternately, the enabler module 107A can simply forward the print file to the print vendor 117A for printing, and generate a message for display on the browser 123 indicating when the file has been transmitted to the print vendor 1 17A.

According to still other embodiments of the invention, the print vendor 1 17A may set up its printer profile to distinguish between erroneous document elements based upon their severity. For example, the print vendor 117A may create a hierarchy that ranks a set of erroneous document elements as fatal errors (i.e., print file errors that cannot be corrected by the print vendor 117A) and another set of erroneous document elements as correctable errors (i.e., print file errors that can be corrected by the print vendor 117A). Of course, those of ordinary skill in the art will appreciate that a print vendor can use any number of hierarchical classifications (e.g., using three or more different classifications), and that different print vendors can employ different hierarchical classifications to categorize document elements found in the print file.

With some of these embodiments, the analyzer 1 11 may generate two lists of error messages: one for use by the print buyer 119, containing messages corresponding to fatal errors, and another list for use by the print vendor 117A, containing messages corresponding to correctable errors (these messages may simply identify the error to the print vendor 117A). That is, the analyzer 11 1 may create a separate error list of the correctable errors, in order to flag these correctable errors for special review by the print vendor 117A before printing. If the analyzer 111 determines that the print file contains both "fatal" and correctable errors, then the analyzer will "fail" the print file. In this case, the interface 105 provides the browser 123 with an error listing Web page that includes both lists of errors. On the other hand, if the analyzer 111 determines that the print file contains no errors, or only contains correctable errors, then the analyzer will "pass" the print file. The preflight system 101 will then transmit the print file to the print vendor 117A for printing, along with the list of correctable errors in the print file (if any). This embodiment is particularly advantageous for the print vendor 117A. By using this embodiment, the print vendor 117A can accept all of the print files that it is capable of printing, but still quickly identify those print files that will require special attention before printing.

According to still other embodiments of the invention, the analyzer 111 may generate a single list of error messages for the erroneous document elements that includes a severity categorization for each erroneous document element as designated by the print vendor 117A. The analyzer 1 11 then posts this list through the interface 105 to a Web page 701 ', as shown in Fig. 7B. Like the Web page 701, Web page 701' includes a three lists of error message 703A'- 703C, one for each of three print files that were simultaneously preflighted. In addition, however, the Web page 701 ' includes severity markers 705' that graphically indicate the severity of each noted error. The Web page 701 ' may also include a guide 707', indicating the severity of the error associated with each severity marker 705' (in the illustrated embodiment, there are three possible severities for each error.) The Web page 701 ' may also conveniently provide a tracking number 709' for the preflight results, thereby facilitating the tracking of the preflight results by the print vendor 117A and/or the print buyer 119.

The Web page 701 ' may be accessible to the print buyer 1 19, the print vendor 1 17A, or both. This allows the print buyer 119 and/or the print vendor 117A to assess the errors in the print file, and to determine if the print file should be forwarded to the print vendor 117A for printing. The preflight system 101 may alternately or additionally send the error information to the print vendor 1 17A in a particular form that allows the print vendor 117A to assess the errors in the print file. For example, the preflight system 101 may post an XML listing of the erroneous document elements and their corresponding severity classifications over the network (e.g., the Internet) to a computer operated by the print vendor 117A (e.g., the server computer used to maintain the print vendor's Web site 301). One such listing is shown in Fig. 8. As seen in this figure, the listing 801 includes the tracking number 803 for the preflight process, the name 805 of the print file, and the name 807 of the printer profile used for the preflight process. The listing 801 also includes the type 809 for each noted erroneous document element and the associated severity categorization 811.

Referring back now to Fig. 7B, it can be seen that the error listing 703 A' on the error listing Web page 701 ' includes an error message 711'. The error message 711 ' identifies the associated error as a color or grayscale graphic saved "with JPEG compression." The error message 711 ' also includes a severity marker 705 identifying the error with a "caution" severity. This error message 711' corresponds to XML data in listing 801 of Fig. 8 for a similar erroneous document element (although found in a different print file). As seen in Fig. 8, listing 801 includes an error type 809' identified as "jpegcompressedcgimage" with a corresponding severity categorization 811' identified as "CAUTION." With the XML listing 801 , the print vendor's 117A computer can automatically review the erroneous document elements and/or their severity ranking, and determine whether or not to accept the print file for printing. If the print vendor 117A determines (either automatically or by manual review) to accept the print file for printing, then the print vendor 1 17A can send a message, such as an email message, to the print buyer 119 requesting that the print buyer 119 forward the preflighted print file to the print vendor 117A for printing. Alternately, the print vendor 117A can transmit a submission Web page to the print buyer's browser, through which the print buyer 119 can submit the print file (or files) to the print vendor 1 17A. Further, through various mechanisms known in the art, the print vendor 117A can retrieve the print file for printing. For example, the user interface Web page 311 (or Web pages) can require the print buyer 119 to download a plug-in that will forward the print file to the print vendor 117A over the network (e.g., the Internet) at the print vendor's 117A request. As is known in the art, various embodiments can allow this transfer of the print file or files.

After a print file has been successfully preflighted and the preflight results posted to the error listing Web page 701 (or 701 ') for viewing by the print buyer 119, the print buyer 119 can collect the preflight results, together with the preflighted printed file, into a single archive for submission to the print vendor 119A. For example, as shown in Figs. 7A and 7B, the preflight results Web page 701 includes a command button 705 labeled "Collection." By activating this command button 705, the print buyer 119 retrieves the collection Web page 901, shown in Fig. 9.

The collection Web page 901 includes a list 903 of various options for the collection. For example, the list includes an option 905 to collect all of the fonts associated with the designated print files, and an option 907 to collect all of the images associated with the designated print files. The list 903 also includes an option 909 to designate a specific print file for collection (if more than one print file were preflighted, then the list 903 could include an option 909 for each print file). The list 903 further includes, for each preflighted print file, an option list 911 to individually designate each font referenced in that print file for collection and an option list 913 to individually designate each font referenced in that print file for collection. The print buyer 119 can then use the listed options to specifically designate each item to be collected into the archive. Further, the Web page 901 includes a comment box 915 that allows the print buyer 119 to designate particularly comments to be collected into the archive.

After the print buyer 119 has designated each item and comments to be collected into the archive, the print buyer 119 can then activate the "Collect" button 917 to complete the collection process. When this button 917 is activated, the client machine 121 saves the preflight results into a result file, and collects this result file together with the designated items file into a single archive file. This single archive file can then be conveniently submitted to the print vendor 117A by, for example, transmission over the network (e.g., the Internet), direct transmission over a telephone or other communications line, transfer to a physical storage medium (e.g., a magnetic storage disk) and physical transportation to the print vendor 117A, etc. The archive file may also be compressed using a convenient compression method (e.g., compressed into a .zip type file for a print buyer 1 19 using the Microsoft Windows operating system or a .sit type file for a print buyer 1 19 using the Apple Macintosh operating system). Those of ordinary skill in the art will appreciate that the collection process described above can be implemented by, e.g., a plug-in module 109 downloaded to the browser 123 for this purpose.

It should be noted that each time the preflight system 101 performs a preflighting process, the controller 103 can register information regarding the process against the print vendor 117A. While the scan of the print file takes place on the local machine 121, and the document element analysis takes place within the preflight system 101, the preflight system 101 may correlate any preflight process to the print vendor 117 through which the preflight process was initiated. This is because, according to the invention, the print buyer 119 initiates the preflight process through the print vendor 117 (or generic organization) by accessing the preflight system 101 via the print vendor 1 17 specific Web page 311 (or 31 1 ').. Preferably, the controller 103 can measure or record a variety of information regarding the preflight process for each print file, such as, for example, how many colors are in the print file, the size of the print file, the number of pages preflighted, the time required to preflight the print file, the number of print files preflighted, the number of profiles used for the preflight process, etc.

As shown in Fig. 9, this information can be collected and presented to the operators of the preflight system 101 in a Web page 901. Some or all of this information may also be made available to the print vendor 117A, either by providing the print vendor 117A with access to the Web page 901 or by other mechanisms. As will be appreciated by those of ordinary skill in the art, this information collected on the volume of preflight processes initiated through a particular print vendor can be very useful. For example, the operators of the preflight system 101 can use this information to determine which print vendor 117 is using the system the most, the computer equipment capacity required to properly service each print vendor 117, etc. Significantly, the information can also be used to accurately charge the print vendor 117 (i.e., the most significant beneficiary of the preflight process) for the costs associated with the preflight process. The charge may be based upon any of the criteria collected by the preflight system 101. Of course, the preflight system 101 can also (or additionally) collect the same preflight process information for each print buyer 119. This information can then be used to alternately (or additionally) charge the print buyer 1 19 based upon the preflighting processes.

While the above embodiments of the invention have been described with reference to a single print buyer 119 and a plurality of print vendors 117A-117D, those of ordinary skill in the art will appreciate that the preflight system 101 according to the invention it intended to be used simultaneously by both multiple print vendors and multiple print buyers. Further, those of ordinary skill in the art will appreciate that the preflight system 101 according to the invention can be embodied in a number of different ways. For example, while the above-described embodiment of the invention uses Web pages to facilitate the transfer of information between the print buyer 1 19 and the preflight system 101, those of ordinary skill in the art will understand that other techniques can be employed. Also, while the preflight system 101 has been described as embodied on a common server (i.e., a server associated with multiple print vendors 1 17), it will be understood that any print vendor may embody the preflight system 101 according to the invention on a proprietary server.

The present invention has been described above by way of specific exemplary embodiments, and the many features and advantages of the present invention are apparent from the written description. Thus, it is intended that the appended claims cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, the specification is not intended to limit the invention to the exact construction and operation ad illustrated and described. For example, the invention may include any one or more elements from the apparatus and methods described herein in any combination or subcombination. Accordingly, there are any number of alternative combinations for defining the invention, which incorporate one or more elements from the specification (including the drawings, claims, and summary of the invention) in any combinations or subcombinations. Hence, all suitable modifications and equivalents may be considered as falling within the scope of the appended claims.

Claims

We claim:

1. A preflight system, comprising: a printer profile database containing a first list of problem document elements classified in a first category and a second list of problem document elements classified in a second category; and an analyzer that compares document elements from a print file provided by a print buyer with the problem document elements in the first list and the second list to identify problem document elements occurring in the print file; and compiles a categorization list of the problem document elements occurring in the print file that identifies the category for one or more of the problem document elements occurring in the print file.

2. The preflight system recited in claim 1 , wherein the analyzer provides the categorization list to the print buyer.

3. The preflight system recited in claim 2, wherein the analyzer posts the categorization list to a Web page accessible by the print buyer.

4. The preflight system recited in claim 1, wherein the analyzer provides the categorization list to a print vendor.

5. The preflight system recited in claim 4, wherein the analyzer posts the categorization list to a Web page accessible by the print vendor.

6. The preflight system recited in claim 4, wherein the analyzer provides the categorization list to both the print buyer and the print vendor.

7. The preflight system recited in claim 6, wherein the analyzer posts the categorization list to a Web page accessible by both the print buyer and the print vendor.

8. The preflight system recited in claim 6, wherein the analyzer provides the categorization list to the print vendor as XML data.

9. The preflight system recited in claim 1 , wherein the printer profile database contains a third list of problem document elements classified in a third category; and the analyzer that compares document elements from a print file provided by a print buyer with the problem document elements in the first list, the second list and the third list to identify problem document elements occurring in the print file; and compiles a categorization list of the problem document elements occurring in the print file that identifies the category for one or more of the problem document elements occurring in the print file.

10. A method of preflighting a print file, comprising: retrieving a first list of problem document elements classified in a first category and a second list of problem document elements classified in a second category; comparing document elements from a print file provided by a print buyer with the problem document elements in the first list and the second list to identify problem document elements occurring in the print file; and compiling a categorization list of the problem document elements occurring in the print file that identifies the category for one or more of the problem document elements occurring in the print file.

11. The method of preflighting recited in claim 10, further including providing the categorization list to the print buyer.

12. The method of preflighting recited in claim 11 , f rther including posting the categorization list to a Web page accessible by the print buyer.

13. The method of preflighting recited in claim 10, further including providing the categorization list to a print vendor.

14. The method of preflighting recited in claim 13, further including posting the categorization list to a Web page accessible by the print vendor.

15. The method of preflighting recited in claim 13, further including providing the categorization list to both the print buyer and the print vendor.

16. The method of preflighting recited in claim 15, further including posting the categorization list to a Web page accessible by both the print buyer and the print vendor.

17. The method of preflighting recited in claim 15, further including providing the categorization list to the print vendor as XML data.

18. The method of preflighting recited in claim 10, further including: retrieving a third list of problem document elements classified in a third category; comparing document elements from a print file provided by a print buyer with the problem document elements in the first list, the second list and the third list to identify problem document elements occurring in the print file; and compiling a categorization list of the problem document elements occurring in the print file that identifies the category for one or more of the problem document elements occurring in the print file.