US20020149792A1 - Method and system for merging variable text and images into bitmaps defined by a page description language - Google Patents
Method and system for merging variable text and images into bitmaps defined by a page description language Download PDFInfo
- Publication number
- US20020149792A1 US20020149792A1 US09/874,895 US87489501A US2002149792A1 US 20020149792 A1 US20020149792 A1 US 20020149792A1 US 87489501 A US87489501 A US 87489501A US 2002149792 A1 US2002149792 A1 US 2002149792A1
- Authority
- US
- United States
- Prior art keywords
- template
- sub
- bitmap
- rendering commands
- merged
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K15/00—Arrangements for producing a permanent visual presentation of the output data, e.g. computer output printers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
- G06F3/1211—Improving printing performance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
- G06F3/1237—Print job management
- G06F3/1242—Image or content composition onto a page
- G06F3/1243—Variable data printing, e.g. document forms, templates, labels, coupons, advertisements, logos, watermarks, transactional printing, fixed content versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
- G06F3/1237—Print job management
- G06F3/1244—Job translation or job parsing, e.g. page banding
- G06F3/1247—Job translation or job parsing, e.g. page banding by conversion to printer ready format
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
- G06F3/1285—Remote printer device, e.g. being remote from client or server
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T11/00—2D [Two Dimensional] image generation
- G06T11/60—Editing figures and text; Combining figures or text
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/387—Composing, repositioning or otherwise geometrically modifying originals
- H04N1/3871—Composing, repositioning or otherwise geometrically modifying originals the composed originals being of different kinds, e.g. low- and high-resolution originals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K2215/00—Arrangements for producing a permanent visual presentation of the output data
- G06K2215/0002—Handling the output data
- G06K2215/0005—Accepting output data; Preparing data for the controlling system
- G06K2215/0011—Accepting output data; Preparing data for the controlling system characterised by a particular command or data flow, e.g. Page Description Language, configuration commands
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K2215/00—Arrangements for producing a permanent visual presentation of the output data
- G06K2215/0002—Handling the output data
- G06K2215/0062—Handling the output data combining generic and host data, e.g. filling a raster
- G06K2215/0065—Page or partial page composition
Definitions
- the present invention relates to the high-speed printing industry, and more particularly, to a system and method for merging variable data and images into a template image defined by a page description language file in a high speed printing environment.
- Application programs such as wordprocessors, illustrators, and computer aided design systems are software packages used to create a document (text and graphics) on a computer screen and to simultaneously generate a page description language (“PDL”) specification, which is to be transferred to the printer, or to any other type of raster device or output device for creating a hard copy or copies of the document.
- PDL page description language
- the printer executes the PDL specification to generate a bitmap of the document, or a raster-data representation of a document, and eventually transfers the bitmap or raster-data to a physical medium such as paper.
- a typical PDL language such as PostScript (a registered trademark of Adobe Corporation) defines a page of the document as containing a number of data areas, where each data area contains either graphic or alpha-numeric data.
- Each data area is defined by a “graphic state,” which is a collection of parameters or attributes for controlling the representation and appearance of text and graphics.
- the graphic state can include a set of text attributes such as scale factor, type font, etc.
- an example of a PDL command used to build a graphic state can be:
- PDL commands used to define the graphic or alpha-numeric data that is displayed in the data area include:
- PDL specification The entire group of PDL commands used to define a document is hereinafter referred to as the “PDL specification.”
- graphic attributes any particular attribute or combination of attributes included in a graphic state, or any similar attribute contained in a PDL specification for defining or controlling the representation, location and/or appearance of text and graphics in a final bitmap or raster image.
- each printed document shares a common template and there is at least one area in the template that changes for each printing of the template.
- Typical PDL languages are not designed for high-speed variable data printing because, with PDL languages and interpreters, even if a single item of data in the document changes, an entirely new PDL specification must be created and interpreted. For example, if 100,000 copies of a mass mailing advertisement were to be printed (i.e., each copy of which is identical except for the mailing address) it is typically necessary to generate a new PDL specification for each copy to be printed. Hence, to generate 100,000 advertisements, it would be necessary to generate 100,000 PDL specifications, even though each advertisement is virtually the same except for the variable data area. The processing time required to interpret and render 100,000 PDL specifications is enormous, significantly slowing the entire printing system.
- variable images or bitmaps such as company logos, coupons, charts, and the like
- variable text data such as company logos, coupons, charts, and the like
- the template is defined by a PDL specification, and this template specification only needs to be processed or interpreted once before creating all of the merged bitmaps, thus providing an extremely high-speed variable data printing operation.
- variable images to be merged into the template may also be defined by “sub-template” PDL specifications, which also need only be processed or interpreted once. Such sub-template specifications may also allow for variable data or images to be merged into them as well, before being merged into the primary template.
- a computer implemented method for merging variable data into an image defined by page description language specification generally comprises the steps of: processing (interpreting) the template PDL specification to produce a template; processing the sub-template specification (defining the variable bitmap image) to produce a sub-template; identifying a variable data identifier in the template specification; associating the sub-template with the variable data identifier; and merging the sub-template into a copy of a template to generate a merged bitmap.
- a computer implemented method of the present invention comprises the steps of: a) generating a template PDL specification, the template specification including template data and associated graphic attributes (i.e., graphic states) defining how the template data is to appear on a printed page, the template specification including at least one variable data identifier; b) generating a plurality of sub-template PDL specifications, each sub-template specification including sub-template data and associated graphic attributes defining how the sub-template data is to appear on a portion of a printed page; c) interpreting the template specification so as to generate a template bitmap or a plurality of template rendering commands (display list), and during the interpreting step, identifying the variable data identifier; d) saving the template bitmap or the plurality of template rendering commands into memory; e) associating the variable data identifier with the sub-template specifications; f) accessing a first sub-template specification from the plurality of sub-template specifications; g) processing the first sub-tem
- the method of the present invention is accomplished by executing a control task in conjunction with a PDL interpreter program.
- the control task generates a template display list based upon the PDL commands in the PDL specification.
- the display list includes a plurality of rendering commands, where each rendering command designates a particular data area or object to be rendered, the graphic states to be applied to the data area and the offset address at which the rendered object, if any, in the data area is to be over written onto the final bitmap.
- the graphic states for each data area re set forth in the PDL specification, and pertain to the print attributes that describe how particular graphic or alpha-numeric data is to appear on the printed page. These attributes can include size, font, position, orientation, location and the like.
- the control task also generates display lists for each of the sub-template PDL specifications.
- the control task monitors the data areas defined by the PDL specifications to watch for variable data identifiers defined by the PDL code. If the control task identifies a data area or object as being (or including) a variable data identifier, it reserves the graphic states associated with that variable data identifier in a cache and continues on with the interpretation procedure, preferably without adding the rendering commands for that variable data area into the display list. In this identification step, the control task will also watch for attributes associated with the variable data identifier. Such attributes may define the variable data identifier as identifying a sub-template bitmap, which is to be merged into the bitmap represented by the PDL specification.
- control task will instead store a “place holder” in the graphic states cache corresponding to the sub-template PDL specification identified in the variable data identifier string.
- control task may include certain graphic attributes associated with the variable data identifier in the cache, along with the place holder, such as a graphic attribute defining the location of the variable data identifier (which may be used to determine where to merge the sub-template bitmap into the template bitmap).
- the control task saves each display list in memory without dispatching a bitmap of the template or sub-template to the printer.
- the merge task is initiated which accesses a copy of the template display list from memory and begins processing the rendering commands in the display list to create a bitmap of the template.
- the merge task accesses a variable data record from a merge file; associates the variable data record to the graphic states in the cache and creates bitmaps for the data in the variable data record by applying the reserved graphics states to the data in the variable data record these bitmaps may be merged into the template bitmap or rendered directly onto the template bitmap during, before, or after the rendering of the template bitmap.
- the merge task When the merge task reaches the place holder in the cache associated with the sub-template display list, the merge task will access and begin processing the rendering commands in the sub-template display list to create a bitmap of the sub-template, which is then merged onto the template bitmap. When finished with the rendering commands of the sub-template display list, the merge task will return to the processing of the variable data record by applying the reserved graphic states thereto and merging the resulting bitmaps into the template bitmap. The merge task is repeated for each variable data record in the merge file to create a plurality of the merged bitmaps.
- the PDL specifications of the template and sub-templates need only be interpreted once, saving significant processing time for the variable printing operation, because the reserved graphic states may be utilized over and over again to create the variable bitmaps for each variable data record contained in the merge file. Similarly the display lists of the templates and sub-templates may be used over and over again to create the multiple merged bitmaps.
- a sub-template is a collection of graphic states or graphic attributes taken from another source (such as a PDL specification) and used collectively as a variable element inserted into a template PDL page.
- the sub-templates may be used to add variable graphics/logos, or other static images to a page; to add formatted pieces (such as graphs, charts, images, etc.), including any number of additional variable fields to a page, a page of variable coupons directly marketed to the end receiver, and the like.
- the sub-template is really just another PDL page used as an element drawn somewhere on another page. For example, one coulde have a PDL page that had a company logo drawn on it. One could then use that logo on demand whenever a printed page calls for it. Taken further, one could have several different logos, each drawn as a separate PDL page, which one could add (or not) to any page printed during the processing job.
- FIG. 1 is a schematic, block diagram representation of a high-speed printing system according to the present invention
- FIG. 2 is a schematic flow diagram illustrating the method of the control task according to the present invention.
- FIG. 3 is a schematic flow diagram representing the method of the merge task according to the present invention.
- FIG. 4 is an example of a job ticket file for use with the present invention.
- FIG. 5 is an example of a merge file for use with the present invention.
- FIG. 6 is an example of a sub-template file for use with the present invention.
- FIG. 7 is an example of a template file for use with the present invention.
- FIG. 8 is an example of a merged page created by the process of the present invention using the PDL specification of FIG. 7, the job ticket of FIG. 4, the sub-template specifications of FIG. 6 and the merge file of FIG. 5.
- a system for performing the method of the present invention includes a printer controller 10 having access to a job ticket file 12 a page description language (“PDL”) file of a template 14 , a plurality of PDL files for sub-templates 15 , a source of variable data such as a merge file 16 and an optional printer configuration file 18 .
- the system also contains an operator control terminal 20 for providing operator controls such as indicating the name and path of the job ticket file 12 for the specific print job.
- the job ticket file 12 contains the guidelines for the print job which can include the names and locations of the PDL files 14 , 15 , the merge files 16 , the configuration files 18 , etc.; and may also include special instructions pertaining to the print job such as identifying and locating sub-templates, defining additional graphical attributes for variable data areas identified during the process, and the like, all of which is described in greater detail below.
- the PDL files 14 , 15 are preferably PostScript® specifications created by an application program such as a wordprocessor, illustrator, or computer aided design system.
- the merge file 16 contains platform independent data, such as text data, image data, bar-code data and the like, which is to merged into a template bitmap defined by the PDL template specification 14 or the PDL sub-template specifications 15 during the merging task, as will be described in detail below.
- the configuration file 18 defines the print engines and the post processing equipment and other options to be executed.
- the path and name of the job ticket file 12 is specified by the operator using the operator control terminal 20 .
- the printer controller 10 retrieves the job ticket file 12 and then retrieves the PDL files 14 , 15 specified in the job ticket file.
- the controller 10 initiates a control task 22 in conjunction with a page description language interpreter program.
- the control task 22 interprets the PDL specifications from the PDL files 14 , 15 and monitors data areas defined in the PDL specifications to watch areas defined by the specifications to become variable. If the control task identifies a data area as being a variable data area, it reserves the graphic states and/or other associated graphic attributes 23 of that variable data area in a cache or memory 24 and then moves on to the next data area defined by the particular PDL specification, usually without allowing any data defined by the variable data area to be added to the template bitmap. The control task also looks for predetermined attributes defined in the data areas to determine if the data area is defining the importation of a sub-template bitmap.
- the control task detects such an attribute, rather than storing the graphic states associated with the data area in the cache 24 , it stores a placeholder 23 ′ in memory, which will instruct the merge task that a sub-template is to be incorporated into the present template or sub-template bitmap during the merge task 28 , and will also include information identifying the one or a group of the sub-templates that may be merged into the present template or sub-template bitmap.
- the control task saves the template display list 25 or sub-template display list 27 in memory 26 .
- the template and sub-template display lists 25 , 27 will include a plurality of rendering commands for the static data defined in their respective PDL specifications. Each rendering command designates a particular static data area or object to be rendered, the graphic states and/or graphic attributes to be applied to the static data area and the offset address at which the rendered object, if any, in the static data area is to be over written onto the final bitmap.
- a merge task 28 having access to the variable data records 17 from the merge file 16 is executed to apply the reserved graphic states and/or graphic attributes 23 to the variable data records 17 , creating rendering commands for that variable data record as defined by the graphic states.
- the merge task 28 retrieves a copy 25 ′ of the template display list from the memory 26 and merges the variable data rendering commands with the template display list to create a merged display list 30 .
- the merge task will also look for place holders 23 ′ among the graphic states stored in the memory 24 during this merging operation.
- the merge task will access a copy 27 ′ of the display list of the sub-template corresponding to the place holder and will then merge the rendering commands from the display list of the sub-template 27 ′ with the merged display list 30 .
- the sub-template may also include an associated cache of graphic states and/or graphic attributes corresponding to variable data areas (or even additional levels of sub-templates) defined within the sub-template. Therefore, if such a cache is present with a particular sub-template, the merge task will apply such stored graphic states and/or graphic attributes to the present variable data fields in the variable data record 17 linked to the graphic states to therefore create rendering commands for such variable data fields. These rendering commands are also merged into the display list 30 .
- the controller 10 performs a rendering task 32 to render the merged display list 30 into a plurality of bitmap bands 34 for dispatching to at least one print engine 36 .
- a rendering task 32 to render the merged display list 30 into a plurality of bitmap bands 34 for dispatching to at least one print engine 36 .
- a general method for performing the above control task is described in U.S. Pat. No. 5,729,665, the disclosure which is incorporated herein by reference.
- a method and system architecture for performing the above merging, banding and dispatching operations are respectively described in U.S. Pat. Nos. 5,594,860 and 5,796,930, the disclosures of which are also incorporated herein by reference.
- FIG. 2 a graphical flow diagram representation of the control task is illustrated.
- the primary function of the control task is to monitor a PDL interpreter program which interprets the PDL specifications for the template ( 14 ) and the sub-templates 15 to create display lists 25 , 27 , containing the rendering commands for the static data in the PDL specifications, and a cache of graphic states and/or graphic attributes corresponding to the variable data areas identified by the PDL specifications.
- the PDL specifications are typically in the form of a list of PDL commands (as described above) the specifications 14 , 15 a and 15 b shown in FIG. 2 are shown, for clarity, as they would have appeared to the artist using the application program (such as QuarkXPress®) to create such PDL specifications.
- the template PDL file 14 includes a plurality of static data areas 38 and a plurality of variable data areas 40 .
- the variable data areas are identified by the control task as a text string surrounded by special characters, “ ⁇ ” and “>>”.
- the phrase or word within the special characters corresponds to the field name for the particular variable data area.
- These strings may also be followed by an attribute command string 42 , which may define special attributes to be applied to the particular variable data area.
- the variable data identifier with the field name “PICTURE” is followed by the attribute command string “SELECT”, which, as will be discussed below, informs the control task that the particular variable data area corresponds to the insertion of a sub-template.
- the rendering commands for the static data areas 38 in the template PDL file are stored in a template display list 25 and the graphic states 23 of the variable data areas 40 are stored in a cache 24 .
- the graphic state stored in the cache for the variable data area having the “select” attribute string is merely a place holder 23 ′, which will instruct the merge file to insert a sub-template bit map into the template bit map being rendered.
- the control task will also interpret the sub-template PDL files 15 a , 15 b , shown as sub-template “A” and sub-template “B” in FIG. 2.
- Sub-template “A” 15 a includes two static data areas 38 , and therefore a sub-template display list 27 a is created for the sub-template “A” PDL file, including the rendering commands for such static data areas.
- the sub-template “B” PDL file 15 b includes a static data area 38 and a variable data area 40 . Therefore, the control task will create a sub-template display list 27 b , including the rendering command for the static data area and will cache the graphic states 23 ′ for the variable data area.
- variable data identifiers in the sub-template PDL specifications may also include attribute strings for special processing, such as specifying additional levels of sub-template files.
- attribute strings for special processing such as specifying additional levels of sub-template files.
- the present example is shown with only one level of sub-templates.
- the merge task will access a copy 25 ′ of the template display list and will also access a first record 46 from the merge file 16 .
- the first record has record fields, in the form of text strings, for each of the field names VAR1, VAR2, VAR3 and VAR4.
- the record includes a name (in this example either A or B) corresponding to the sub-template to be inserted for the variable data identifier having the field name “PICTURE.”
- the merge task accesses the rendering commands from the copy of the template display list 25 ′ to add to a merged display list 30 .
- Such rendering commands will be processed by the rendering task 32 to generate the bit maps 48 for the static data areas from the template PDL specification 14 to appear in the merged bitmap 52 .
- the merge task will link the cached graphic states 23 to the to the record fields by matching the field names associated with the cached graphic state to the field names in the merge file. For example, the cached graphic states for the variable data identifier 40 having the field name “VAR1” will be linked to the record fields in the merge file under the field name “VAR1.”
- the merge task will apply the graphic states 23 to the data in the associated record field to create rendering commands for such data, which are to merged into the merged display list 30 .
- Such rendering commands will be processed by the rendering task 32 to generate the bit maps 50 in the merged bitmap 52 . This is done for each of the graphic states in the cache.
- the merge task When the merge task reaches the place holder 23 ′ in the template graphic states cache, it will link the place holder 23 ′ to the to the record fields by matching the field name associated with the the place holder 23 ′ to a field name in the merge file. For example, the he place holder 23 ′ for the variable data identifier 40 having the field name “PICTURE” will be linked to the record fields in the merge file under the field name “PICTURE.” The field name in the record will identify which of the sub-templates to merge into the merged display list 30 and eventually into the merged bitmap 52 .
- the merge task accesses the sub-template display list 44 b and merges its rendering commands into the merged display list 30 .
- Such rendering commands will be processed by the rendering task 32 to generate the bit maps 54 in the merged bitmap 52 .
- the merge task also accesses the associated cache of graphic states for the sub-template, and applies the graphic states to the record fields linked to the graphic states so as to generate rendering commands for the data of the record fields that are to be merged into the merged display list 30 .
- Such rendering commands will be processed by the rendering task 32 to generate the bit maps 56 in the merged bitmap 52 .
- the cache graphic states for the sub-template would also include a place holder, and the merge task would access the sub-templates associated with this place holder for another level of sub-template processing.
- the final merged big map 52 includes the static data bitmaps 48 defined by the template PDL file 14 , the static data bitmaps 54 defined by the sub-template “B” PDL file 15 b , the variable data bitmaps 50 having the graphic attributes corresponding to the cached graphic states for the variable data identifiers 40 in the template PDL file 50 , and the variable data bitmaps 56 having the graphic attributes corresponding to the cached graphic states for the variable data identifiers 40 in the sub-template “B” PDL file 15 b .
- the location of the bit maps 54 , 56 from the sub-template “B” PDL specification can be defined by the job ticket file (see the Appendix to this disclosure).
- this graphic attribute may also include other information such as orientation, size, etc.
- This additional graphic attribute may be stored with the place holder and applied to the bit map data from the sub-template file during the merging operation.
- a graphic state corresponding to the location of the variable data identifier having the attribute 42 corresponding to the sub-template may be stored with the place holder in the graphic state cache to direct the merge task to place the bit maps from the sub-template in the merge bit map 52 in the location directed by the stored graphic state.
- the job ticket file 12 contains a group header 60 “[PageDescriptionLanguageFile]” indicating that the phrases below that group header 60 are the names of page description language files to be processed by the control task.
- the job ticket file 12 includes a group header 66 “[letter_master],” under which are defined the location and attributes for that PDL file. Note that with this PDL file no attributes are defined and only the path location for the file is indicated.
- the job ticket also includes a group header 74 “[MergeFiles]” identifying the names of the merge files to be used in the merge task.
- a single merge file is named “merge.”
- a group header 78 “[merge]” is given, under which the attributes and location of the merge file is set forth.
- the attribute strings for this merge file indicate that the merge file is delimited and includes merge headers.
- the attribute strings also indicate that the records are delimited by a carriage-return/line-feed character and the particular fields in each record are delimited by a tab character.
- the merge file 16 has a platform-independent data file that contains the “variable” data to be merged into the path defined in the PDL specification, and also includes names associated with the sub-templates to be merged into the PDL specification during the merge task.
- the merge file in the present example includes a plurality of rows of merge records separated by carriage-return/line space characters, where each record includes the following fields: “fname,” “lname,” “prefix,” “title,” “company,” “address,” “zip,” “region,” “city” and “state.”
- the data in the field “region” doubles as variable data and also as a name of a sub-template to be merged into the final bit maps.
- variable data identifiers 80 each include a field name surrounded by special characters, “ ⁇ ” and “ >>”, and may also include an attribute string 82 following the field name and special characters.
- the attribute string will be described below.
- the PDL specification generated by the application program will include the graphic states of the variable data identifiers 80 . These graphic states can include the font size (i.e., 12 point), the type-font (i.e., Helvetica), the orientation (i.e., horizontal), the location such as x and y coordinates, and the like.
- control task will create a display list with the rendering commands for the static data in the PDL specification and will cache the graphic states for the variable data identifiers without transferring the rendering commands for the variable data identifiers to the display list.
- the variable data identifier in the bottom center portion of the page includes the “select” attribute, indicating to the control task that a sub-template bit map is to be inserted into the document.
- the field name “region” associated with this variable data identifier indicates that the sub-template name will be under the heading “region” in the merge file.
- the regions named in the merge file are South, East, West and Midwest. Therefore, referring to FIG. 4, the sub-templates having the name South, East, West and Midwest are found in the PDL file defined under the “all_maps” group header ( 68 ) in the job ticket. Note that the attributes defined under the “all_maps” group header do not include an attribute directing the location of the sub-template. Therefore, the lower left-hand corner of the sub-template merged into the final document will be directed by the locational graphic states of the variable data identifier stored along with the place holder in the graphic state cache.
- FIG. 7 illustrates the sub-template PDL file 15 , including the four sub-templates: South 84 a , East 84 b , West 84 c and Midwest 84 d .
- the merge task will access a variable data record 86 from the merge file 16 and a copy of the display list for the template PDL file 25 .
- the merge task will generate rendering commands for the variable data records in the merge file by applying the cached graphic states linked to the variable data records. These rendering commands will be merged into the merged display list along with the rendering commands from the display list for the template PDL file.
- the merge task will also merge the rendering commands from the display list of the sub-template named by the variable data records into the merged display list.
- the rendering task will process the rendering commands in the merged display list to generate the final merged bit map for the present variable data record 86 . This bit map appears in FIG. 8.
- the merge task will apply the cached graphic states linked to the variable data fields in the variable data record 86 as follows.
- the first graphic state in the cache will be for the first variable data identifier 80 a .
- the field name for this variable data identifier 80 a is “fname,” which in the particular variable data record, corresponds to “Shannon.” Therefore, the final merged bit map will include a bit map of the text, “Shannon” 88 a , having the graphic states for the variable data identifier 80 a .
- the second cached graphic state will be for the variable data identifier 80 b which includes a field name “lname,” corresponding to the term “Janzen” in the particular variable data record 86 .
- the final merged bit map will include a bit map of the text, “Janzen” 88 b , - 15 having the graphic states for the variable data identifier 80 b .
- the remaining graphic states except for those of variable data identifier 88 m , which is the variable data identifier including the sub-template attribute 82 , will be processed in the same way resulting in bit maps 88 c - 88 n in the merged bitmap.
- the merge task When the merge task reaches the place holder in the graphic state cache associated with the variable data identifier 80 m , it will refer to the merge record for the name of the sub-template under the field name “Region,” which in the present example is “South.” Referring to FIG. 7, the sub-template having the name “South” is sub-template 84 a . Accordingly, the merge file will then merge the rendering commands from the display list of the sub-template 84 a into the merged display list. Some or all of these rendering commands will also be modified by a graphic attribute corresponding to the location that the sub-template is to be merged into the merged bit map. As discussed above, this graphic attribute may be taken from the graphic state of the variable data identifier 80 m or may be defined in the job ticket file.
- the present invention also provides for the flowing of sub-templates into a path defined by the template specification.
- a feature is based upon the invention disclosed in U.S. patent application Ser. No. 08/897,467, filed Jul. 18, 1997.
- the feature includes the steps of: associating a path defined by the template PDL specification with the variable data identifier with the “sub-template” attribute string; and merging the sub-template(s) into the path according to the path boundary and according to a predefined flow rule (as will be defined in the job ticket).
- the path may be associated with the attribute string, for example, by having the PDL command for the path immediately follow the PDL command for the attribute string in the PDL specification, or by having the PDL command for the path “grouped” with the PDL command for the attribute string using a GROUP command provided by the application program.
- Appendix provides a preferred compilation of commands and parameter definitions that can be specified in the job ticket file 12 for the sub-template application as described above. Each entry provides a particular command header, the syntax for the command, any relevant remarks for the use of the command, examples, etc. As will be appreciated by one of ordinary skill in the art, the present invention includes any and all additional functions, features and attributes detailed in the Appendix.
- APPENDIX [PageDescriptionLanguageFile] A group that provides a list of tags which you create to describe the PDL file(s) to be used in the print job. Each tag will become a user-defined group to give additional information about a specific PDL file.
- Example [PageDescriptionLanguageFile] Cover Form Contents Form Letter Form A user-defined tag name for a group that provides information about a PDL file and corresponds to a descriptive tag that you created under the initial [PageDescriptionLanguageFile] group.
- Each tag that appears as a parameter of Templates may become a user- defined group name listed elsewhere in the Job Ticket.
- the Templates statement simply lets VariScript know that it is to look for user-defined groups and then provides the names (tags) of these groups. Therefore, in theory, a PDL file with ten pages could have up to ten template tags listed within the Templates element. If any templates need not be named, the order of templates can be preserved by inserting blank template tags into the list.
- Explanation Template Tag A Create a descriptive name for the first template in this PDL file. This tag is for use within the Job Ticket.
- Template Tag B Create a descriptive name for the next template in this PDL file. This tag is for use within the Job Ticket. And so on.
- Example Templates tempA, tempB, ,tempD SUBTEMPLATE An element that identifies the templates within the specified PDL file as being subtemplates.
- SubTemplate ⁇ True
- a subtemplate is a template or PDL page that is used as an object to be inserted on another page.
- a default value for SubTemplate is False. Explanation ⁇ True
- Example SubTemplate True SUBTEMPLATE AREA An element that assigns a subtemplate name and describes the portion of a template to be used as a subtemplate.
- Explanation Name “ ⁇ SubName>” This value assigns a specific name to the subtemplate. Type the word Name followed by a space. For “ ⁇ SubName>”, type the name to be assigned to this subtemplate. Enclose the subtemplate name in double quotation marks (“”).
- a subtemplate will be known by the official name of the template, unless it is given another name through the SubTemplate Area element. The official template name is defined by the method of highest precedence. The template name of lowest precedence is the default system-generated template name, followed by the template name you physically define on the PDL template.
- Possible ⁇ Unit Type> values are: cm for centimeters dm for decimeters dots for dots ft for feet in for inch (default value) m for meters mils for mils mm for millimeter nm for nanometers pixels for pixels pts for points pulses for pulses yds for yards
- the default value for X is 0.
- Y ⁇ Units> ⁇ UnitType> This value identifies the vertical distance between the bottom of the template and the area to be extracted. Type the character Y followed by a space. For ⁇ Units>, type the vertical distance from the bottom of the template to the beginning of the area to be extracted. A Y value of 0 represents a location flush along the bottom of the template.
- Y locates the area to be extracted the defined distance above the bottom of the template.
- the Y value is expressed in unitized format if the unit type is different from the default unit type defined in the Units element. Possible ⁇ Unit Type> values are listed above.
- the default value for Y is 0.
- Width ⁇ Unit> ⁇ Unit Type> This value identifies the width of the portion to be extracted (starting at the X, Y coordinates).
- Type the word Width followed by a space.
- ⁇ Units> The value identifies the height (length) of the portion to be extracted (starting at the X, Y coordinates).
- Type the word Height followed by a space.
- type the height of the area to be extracted from the template. This measurement is the Y (vertical) dimension of the area to be extracted. This value is expressed in unitized format if the unit type is different from the default unit type defined in the Units element. Possible ⁇ Unit Type> values are listed above. The default value for Height is equal to the width of the template.
- SubTemplateArea The same area (SubTemplateArea) on each template is ps2 will be defined as a subtemplate. This area represents a 3-inch wide by 4-inch long portion starting from 1 inch to the right and 2 inches above the lower left corner of the template. Since no Name ⁇ SubName> value is given, each subtemplate will take the official name of its template.
- a rendering parameter applied within this group has the highest precedence. It will override the definition of the same parameter in the configuration file, in the [JobSetup] group, and in the [PDLFileTag] group.
- NewName See the NewName element description
- SubTemplate See the SubTemplate element description.
- SubTemplate Area See the SubTemplate Area element description.
- the template receives its name in one of three ways:
- the system automatically generates a default template name.
- VariScript will recognize only one template name for each template. Therefore, a template name assigned by using a method of higher precedence will overwrite a name of lower precedence. For example, a name defined directly on the template will overwrite the system- generated default, and, in turn, be overwritten by a name defined using the NewName element. The NewName element does NOT have a default value.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Record Information Processing For Printing (AREA)
Abstract
A computer implemented method includes the steps of: a) generating a template PDL (page description language) specification, the template specification including template data and associated graphic attributes (i.e., graphic states) defining how the template data is to appear on a printed page, the template specification including at least one variable data identifier; b) generating a plurality of sub-template PDL specifications, each sub-template specification including sub-template data and associated graphic attributes defining how the sub-template data is to appear on a portion of a printed page; c) interpreting the template specification so as to generate a template bitmap or a plurality of template rendering commands (display list), and during the interpreting step, identifying the variable data identifier; d) saving the template bitmap or the plurality of template rendering commands into memory; e) associating the variable data identifier with the sub-template specifications; f) accessing a first sub-template specification from the plurality of sub-template specifications; g) processing the first sub-template specification so as to generate a sub-template bitmap or a plurality of first sub-template rendering commands; h) accessing a copy of the template bitmap or the plurality of template rendering commands from memory; i) merging the copy of the template bitmap or template rendering commands with the sub-template bitmap or sub-template rendering commands so as to provide a first merged bitmap or first merged plurality of rendering commands; j) generating a first merged bitmap from the first merged plurality rendering commands (if necessary); k) accessing a next sub-template specification from the plurality of sub-template specifications; l) processing the next sub-template specification so as to generate a next sub-template bitmap or plurality of next sub-template rendering commands, m) accessing a copy of the template bitmap or template rendering commands from memory; n) merging the copy of the template bitmap or template rendering commands with the next sub-template bitmap or sub-template rendering commands so as to provide a next merged bitmap or next plurality of rendering commands; and o) generating a next merge bitmap from the next merged plurality of rendering commands, if necessary. The steps k-o may be repeated, as necessary, to generate a plurality of merged bitmaps.
Description
- The present patent application is a Continuation-In-Part of U.S. patent application Ser. No. 08/896,899, filed Jan. 18, 1997; which is a Continuation-In-Part of U.S. patent application Ser. No. 08/373,582, filed Jan. 18, 1995 and issued as U.S. Pat. No. 5,729,665.
- The present invention relates to the high-speed printing industry, and more particularly, to a system and method for merging variable data and images into a template image defined by a page description language file in a high speed printing environment.
- Application programs, such as wordprocessors, illustrators, and computer aided design systems are software packages used to create a document (text and graphics) on a computer screen and to simultaneously generate a page description language (“PDL”) specification, which is to be transferred to the printer, or to any other type of raster device or output device for creating a hard copy or copies of the document. Alternatively a PDL specification can be generated by a programmer without the assistance of an application program.
- The printer executes the PDL specification to generate a bitmap of the document, or a raster-data representation of a document, and eventually transfers the bitmap or raster-data to a physical medium such as paper. A typical PDL language, such as PostScript (a registered trademark of Adobe Corporation) defines a page of the document as containing a number of data areas, where each data area contains either graphic or alpha-numeric data. Each data area is defined by a “graphic state,” which is a collection of parameters or attributes for controlling the representation and appearance of text and graphics. For example, the graphic state can include a set of text attributes such as scale factor, type font, etc. In postscript an example of a PDL command used to build a graphic state can be:
- 20 rotate/Times-Roman findfont 14 scalefont setfont
- Examples of PDL commands used to define the graphic or alpha-numeric data that is displayed in the data area include:
- 0 0 moveto and (ABC) show
- The entire group of PDL commands used to define a document is hereinafter referred to as the “PDL specification.” Furthermore, the entire graphic state, or any particular attribute or combination of attributes included in a graphic state, or any similar attribute contained in a PDL specification for defining or controlling the representation, location and/or appearance of text and graphics in a final bitmap or raster image is hereinafter referred to as “graphic attributes.”
- In variable data printing each printed document shares a common template and there is at least one area in the template that changes for each printing of the template. Typical PDL languages are not designed for high-speed variable data printing because, with PDL languages and interpreters, even if a single item of data in the document changes, an entirely new PDL specification must be created and interpreted. For example, if 100,000 copies of a mass mailing advertisement were to be printed (i.e., each copy of which is identical except for the mailing address) it is typically necessary to generate a new PDL specification for each copy to be printed. Hence, to generate 100,000 advertisements, it would be necessary to generate 100,000 PDL specifications, even though each advertisement is virtually the same except for the variable data area. The processing time required to interpret and render 100,000 PDL specifications is enormous, significantly slowing the entire printing system.
- Furthermore, typical PDL languages do not include the capability of rapidly merging variable images or bitmaps (such as company logos, coupons, charts, and the like) along with variable text data into the template bitmaps. Accordingly, there is a need for a high-speed printing operation having the ability to merge variable data (which includes variable text data and bitmap images) into a template defined by a PDL specification.
- It is an object of the present invention to provide as system and method for merging variable text and bitmap images into a PDL specification in high-speed printing operation. It is a further object of the present invention to provide the ability to generate a plurality of merged bitmaps, which are each essentially a copy of the template, except for at least one portion of the template into which the variable data has been merged. In this portion, each merged bitmap can contain a different set of variable data merged into it. The template is defined by a PDL specification, and this template specification only needs to be processed or interpreted once before creating all of the merged bitmaps, thus providing an extremely high-speed variable data printing operation. The variable images to be merged into the template may also be defined by “sub-template” PDL specifications, which also need only be processed or interpreted once. Such sub-template specifications may also allow for variable data or images to be merged into them as well, before being merged into the primary template.
- A computer implemented method for merging variable data into an image defined by page description language specification (“PDL specification”), according to the present invention, generally comprises the steps of: processing (interpreting) the template PDL specification to produce a template; processing the sub-template specification (defining the variable bitmap image) to produce a sub-template; identifying a variable data identifier in the template specification; associating the sub-template with the variable data identifier; and merging the sub-template into a copy of a template to generate a merged bitmap.
- More specifically, a computer implemented method of the present invention comprises the steps of: a) generating a template PDL specification, the template specification including template data and associated graphic attributes (i.e., graphic states) defining how the template data is to appear on a printed page, the template specification including at least one variable data identifier; b) generating a plurality of sub-template PDL specifications, each sub-template specification including sub-template data and associated graphic attributes defining how the sub-template data is to appear on a portion of a printed page; c) interpreting the template specification so as to generate a template bitmap or a plurality of template rendering commands (display list), and during the interpreting step, identifying the variable data identifier; d) saving the template bitmap or the plurality of template rendering commands into memory; e) associating the variable data identifier with the sub-template specifications; f) accessing a first sub-template specification from the plurality of sub-template specifications; g) processing the first sub-template specification so as to generate a sub-template bitmap or a plurality of first sub-template rendering commands; h) accessing a copy of the template bitmap or the plurality of template rendering commands from memory; i) merging the copy of the template bitmap or template rendering commands with the sub-template bitmap or sub-template rendering commands so as to provide a first merged bitmap or first merged plurality of rendering commands; j) generating a first merged bitmap from the first merged plurality rendering commands (if necessary); k) accessing a next sub-template specification from the plurality of sub-template specifications; l) processing the next sub-template specification so as to generate a next sub-template bitmap or plurality of next sub-template rendering commands, m) accessing a copy of the template bitmap or template rendering commands from memory; n) merging the copy of the template bitmap or template rendering commands with the next sub-template bitmap or sub-template rendering commands so as to provide a next merged bitmap or next plurality of rendering commands; and o) generating a next merge bitmap from the next merged plurality of rendering commands, if necessary. The steps k-o may be repeated, as necessary, to generate a plurality of merged bitmaps.
- The method of the present invention is accomplished by executing a control task in conjunction with a PDL interpreter program. The control task generates a template display list based upon the PDL commands in the PDL specification. The display list includes a plurality of rendering commands, where each rendering command designates a particular data area or object to be rendered, the graphic states to be applied to the data area and the offset address at which the rendered object, if any, in the data area is to be over written onto the final bitmap. The graphic states for each data area re set forth in the PDL specification, and pertain to the print attributes that describe how particular graphic or alpha-numeric data is to appear on the printed page. These attributes can include size, font, position, orientation, location and the like. The control task also generates display lists for each of the sub-template PDL specifications.
- The control task, during the PDL interpretation procedures, monitors the data areas defined by the PDL specifications to watch for variable data identifiers defined by the PDL code. If the control task identifies a data area or object as being (or including) a variable data identifier, it reserves the graphic states associated with that variable data identifier in a cache and continues on with the interpretation procedure, preferably without adding the rendering commands for that variable data area into the display list. In this identification step, the control task will also watch for attributes associated with the variable data identifier. Such attributes may define the variable data identifier as identifying a sub-template bitmap, which is to be merged into the bitmap represented by the PDL specification. If the interpreter detects such an attribute, rather than saving off the graphic states associated with this variable data area, the control task will instead store a “place holder” in the graphic states cache corresponding to the sub-template PDL specification identified in the variable data identifier string. In certain embodiments of the invention, the control task may include certain graphic attributes associated with the variable data identifier in the cache, along with the place holder, such as a graphic attribute defining the location of the variable data identifier (which may be used to determine where to merge the sub-template bitmap into the template bitmap).
- Once the interpreter program completes its interpretation of the PDL specifications, the control task saves each display list in memory without dispatching a bitmap of the template or sub-template to the printer. Subsequently, the merge task is initiated which accesses a copy of the template display list from memory and begins processing the rendering commands in the display list to create a bitmap of the template. Also, the merge task accesses a variable data record from a merge file; associates the variable data record to the graphic states in the cache and creates bitmaps for the data in the variable data record by applying the reserved graphics states to the data in the variable data record these bitmaps may be merged into the template bitmap or rendered directly onto the template bitmap during, before, or after the rendering of the template bitmap. When the merge task reaches the place holder in the cache associated with the sub-template display list, the merge task will access and begin processing the rendering commands in the sub-template display list to create a bitmap of the sub-template, which is then merged onto the template bitmap. When finished with the rendering commands of the sub-template display list, the merge task will return to the processing of the variable data record by applying the reserved graphic states thereto and merging the resulting bitmaps into the template bitmap. The merge task is repeated for each variable data record in the merge file to create a plurality of the merged bitmaps.
- Therefore, the PDL specifications of the template and sub-templates need only be interpreted once, saving significant processing time for the variable printing operation, because the reserved graphic states may be utilized over and over again to create the variable bitmaps for each variable data record contained in the merge file. Similarly the display lists of the templates and sub-templates may be used over and over again to create the multiple merged bitmaps.
- In its simplest form a sub-template is a collection of graphic states or graphic attributes taken from another source (such as a PDL specification) and used collectively as a variable element inserted into a template PDL page. The sub-templates may be used to add variable graphics/logos, or other static images to a page; to add formatted pieces (such as graphs, charts, images, etc.), including any number of additional variable fields to a page, a page of variable coupons directly marketed to the end receiver, and the like. The sub-template is really just another PDL page used as an element drawn somewhere on another page. For example, one coulde have a PDL page that had a company logo drawn on it. One could then use that logo on demand whenever a printed page calls for it. Taken further, one could have several different logos, each drawn as a separate PDL page, which one could add (or not) to any page printed during the processing job.
- FIG. 1 is a schematic, block diagram representation of a high-speed printing system according to the present invention;
- FIG. 2 is a schematic flow diagram illustrating the method of the control task according to the present invention;
- FIG. 3 is a schematic flow diagram representing the method of the merge task according to the present invention;
- FIG. 4 is an example of a job ticket file for use with the present invention;
- FIG. 5 is an example of a merge file for use with the present invention;
- FIG. 6 is an example of a sub-template file for use with the present invention.
- FIG. 7 is an example of a template file for use with the present invention; and
- FIG. 8 is an example of a merged page created by the process of the present invention using the PDL specification of FIG. 7, the job ticket of FIG. 4, the sub-template specifications of FIG. 6 and the merge file of FIG. 5.
- As shown in FIG. 1, a system for performing the method of the present invention includes a
printer controller 10 having access to a job ticket file 12 a page description language (“PDL”) file of atemplate 14, a plurality of PDL files forsub-templates 15, a source of variable data such as amerge file 16 and an optionalprinter configuration file 18. The system also contains an operator control terminal 20 for providing operator controls such as indicating the name and path of thejob ticket file 12 for the specific print job. - The
job ticket file 12 contains the guidelines for the print job which can include the names and locations of the PDL files 14, 15, the merge files 16, the configuration files 18, etc.; and may also include special instructions pertaining to the print job such as identifying and locating sub-templates, defining additional graphical attributes for variable data areas identified during the process, and the like, all of which is described in greater detail below. The PDL files 14, 15 are preferably PostScript® specifications created by an application program such as a wordprocessor, illustrator, or computer aided design system. Themerge file 16 contains platform independent data, such as text data, image data, bar-code data and the like, which is to merged into a template bitmap defined by thePDL template specification 14 or the PDLsub-template specifications 15 during the merging task, as will be described in detail below. Theconfiguration file 18, defines the print engines and the post processing equipment and other options to be executed. - Initially, the path and name of the
job ticket file 12 is specified by the operator using the operator control terminal 20. Theprinter controller 10 retrieves thejob ticket file 12 and then retrieves the PDL files 14, 15 specified in the job ticket file. Next, thecontroller 10 initiates acontrol task 22 in conjunction with a page description language interpreter program. - The
control task 22 interprets the PDL specifications from the PDL files 14, 15 and monitors data areas defined in the PDL specifications to watch areas defined by the specifications to become variable. If the control task identifies a data area as being a variable data area, it reserves the graphic states and/or other associatedgraphic attributes 23 of that variable data area in a cache ormemory 24 and then moves on to the next data area defined by the particular PDL specification, usually without allowing any data defined by the variable data area to be added to the template bitmap. The control task also looks for predetermined attributes defined in the data areas to determine if the data area is defining the importation of a sub-template bitmap. If the control task detects such an attribute, rather than storing the graphic states associated with the data area in thecache 24, it stores aplaceholder 23′ in memory, which will instruct the merge task that a sub-template is to be incorporated into the present template or sub-template bitmap during themerge task 28, and will also include information identifying the one or a group of the sub-templates that may be merged into the present template or sub-template bitmap. Once the control task completes its processing of the particular PDL specification, the control task saves thetemplate display list 25 orsub-template display list 27 inmemory 26. The template and sub-template display lists 25, 27 will include a plurality of rendering commands for the static data defined in their respective PDL specifications. Each rendering command designates a particular static data area or object to be rendered, the graphic states and/or graphic attributes to be applied to the static data area and the offset address at which the rendered object, if any, in the static data area is to be over written onto the final bitmap. - Next, a
merge task 28, having access to the variable data records 17 from themerge file 16 is executed to apply the reserved graphic states and/orgraphic attributes 23 to the variable data records 17, creating rendering commands for that variable data record as defined by the graphic states. Themerge task 28 retrieves acopy 25′ of the template display list from thememory 26 and merges the variable data rendering commands with the template display list to create amerged display list 30. The merge task will also look forplace holders 23′ among the graphic states stored in thememory 24 during this merging operation. If aplace holder 23′ is detected, the merge task will access acopy 27′ of the display list of the sub-template corresponding to the place holder and will then merge the rendering commands from the display list of the sub-template 27′ with themerged display list 30. It is noted that the sub-template may also include an associated cache of graphic states and/or graphic attributes corresponding to variable data areas (or even additional levels of sub-templates) defined within the sub-template. Therefore, if such a cache is present with a particular sub-template, the merge task will apply such stored graphic states and/or graphic attributes to the present variable data fields in thevariable data record 17 linked to the graphic states to therefore create rendering commands for such variable data fields. These rendering commands are also merged into thedisplay list 30. - Once the
merged display list 30 is created, thecontroller 10 performs arendering task 32 to render themerged display list 30 into a plurality ofbitmap bands 34 for dispatching to at least oneprint engine 36. A general method for performing the above control task is described in U.S. Pat. No. 5,729,665, the disclosure which is incorporated herein by reference. A method and system architecture for performing the above merging, banding and dispatching operations are respectively described in U.S. Pat. Nos. 5,594,860 and 5,796,930, the disclosures of which are also incorporated herein by reference. - As shown in FIG. 2, a graphical flow diagram representation of the control task is illustrated. As discussed above, the primary function of the control task is to monitor a PDL interpreter program which interprets the PDL specifications for the template (14) and the sub-templates 15 to create display lists 25, 27, containing the rendering commands for the static data in the PDL specifications, and a cache of graphic states and/or graphic attributes corresponding to the variable data areas identified by the PDL specifications. While the PDL specifications are typically in the form of a list of PDL commands (as described above) the
specifications 14, 15 a and 15 b shown in FIG. 2 are shown, for clarity, as they would have appeared to the artist using the application program (such as QuarkXPress®) to create such PDL specifications. - As shown in FIG. 2 the
template PDL file 14 includes a plurality ofstatic data areas 38 and a plurality ofvariable data areas 40. The variable data areas are identified by the control task as a text string surrounded by special characters, “<<” and “>>”. The phrase or word within the special characters corresponds to the field name for the particular variable data area. These strings may also be followed by anattribute command string 42, which may define special attributes to be applied to the particular variable data area. With respect to the template PDL file shown in FIG. 2, the variable data identifier with the field name “PICTURE” is followed by the attribute command string “SELECT”, which, as will be discussed below, informs the control task that the particular variable data area corresponds to the insertion of a sub-template. - As discussed above, the rendering commands for the
static data areas 38 in the template PDL file are stored in atemplate display list 25 and thegraphic states 23 of thevariable data areas 40 are stored in acache 24. As also discussed above, and as will be discussed in detail below, the graphic state stored in the cache for the variable data area having the “select” attribute string is merely aplace holder 23′, which will instruct the merge file to insert a sub-template bit map into the template bit map being rendered. - The control task will also interpret the sub-template PDL files15 a, 15 b, shown as sub-template “A” and sub-template “B” in FIG. 2. Sub-template “A” 15 a includes two
static data areas 38, and therefore a sub-template display list 27 a is created for the sub-template “A” PDL file, including the rendering commands for such static data areas. The sub-template “B” PDL file 15 b includes astatic data area 38 and avariable data area 40. Therefore, the control task will create a sub-template display list 27 b, including the rendering command for the static data area and will cache thegraphic states 23′ for the variable data area. It is noted here that the variable data identifiers in the sub-template PDL specifications may also include attribute strings for special processing, such as specifying additional levels of sub-template files. For the purposes of simplicity, the present example is shown with only one level of sub-templates. - As shown in FIG. 3, the merge task will access a
copy 25′ of the template display list and will also access a first record 46 from themerge file 16. Note that the first record has record fields, in the form of text strings, for each of the field names VAR1, VAR2, VAR3 and VAR4. For the field name PICTURE, the record includes a name (in this example either A or B) corresponding to the sub-template to be inserted for the variable data identifier having the field name “PICTURE.” The merge task accesses the rendering commands from the copy of thetemplate display list 25′ to add to amerged display list 30. Such rendering commands will be processed by therendering task 32 to generate the bit maps 48 for the static data areas from thetemplate PDL specification 14 to appear in themerged bitmap 52. The merge task will link the cachedgraphic states 23 to the to the record fields by matching the field names associated with the cached graphic state to the field names in the merge file. For example, the cached graphic states for thevariable data identifier 40 having the field name “VAR1” will be linked to the record fields in the merge file under the field name “VAR1.” Once linked, the merge task will apply thegraphic states 23 to the data in the associated record field to create rendering commands for such data, which are to merged into themerged display list 30. Such rendering commands will be processed by therendering task 32 to generate the bit maps 50 in themerged bitmap 52. This is done for each of the graphic states in the cache. - When the merge task reaches the
place holder 23′ in the template graphic states cache, it will link theplace holder 23′ to the to the record fields by matching the field name associated with the theplace holder 23′ to a field name in the merge file. For example, the heplace holder 23′ for thevariable data identifier 40 having the field name “PICTURE” will be linked to the record fields in the merge file under the field name “PICTURE.” The field name in the record will identify which of the sub-templates to merge into themerged display list 30 and eventually into themerged bitmap 52. Because the merge record 46 indicates that the sub-template “B” is to be used, the merge task accesses the sub-template display list 44 b and merges its rendering commands into themerged display list 30. Such rendering commands will be processed by therendering task 32 to generate the bit maps 54 in themerged bitmap 52. The merge task also accesses the associated cache of graphic states for the sub-template, and applies the graphic states to the record fields linked to the graphic states so as to generate rendering commands for the data of the record fields that are to be merged into themerged display list 30. Such rendering commands will be processed by therendering task 32 to generate the bit maps 56 in themerged bitmap 52. - Note that if this sub-template “B” included a further level of sub-templates, the cache graphic states for the sub-template would also include a place holder, and the merge task would access the sub-templates associated with this place holder for another level of sub-template processing.
- The final merged
big map 52 includes the static data bitmaps 48 defined by thetemplate PDL file 14, the static data bitmaps 54 defined by the sub-template “B” PDL file 15 b, the variable data bitmaps 50 having the graphic attributes corresponding to the cached graphic states for thevariable data identifiers 40 in thetemplate PDL file 50, and the variable data bitmaps 56 having the graphic attributes corresponding to the cached graphic states for thevariable data identifiers 40 in the sub-template “B” PDL file 15 b. The location of the bit maps 54, 56 from the sub-template “B” PDL specification can be defined by the job ticket file (see the Appendix to this disclosure). Furthermore, it is within the scope of the invention to include a graphic state or graphic attribute with the place holder that corresponds to the location of the variable data identifier (this graphic attribute may also include other information such as orientation, size, etc.). This additional graphic attribute may be stored with the place holder and applied to the bit map data from the sub-template file during the merging operation. For example, a graphic state corresponding to the location of the variable data identifier having theattribute 42 corresponding to the sub-template may be stored with the place holder in the graphic state cache to direct the merge task to place the bit maps from the sub-template in themerge bit map 52 in the location directed by the stored graphic state. - An embodiment of the present invention is illustrated by way of example in FIGS.4-8. As illustrated in FIG. 4, the
job ticket file 12 contains agroup header 60 “[PageDescriptionLanguageFile]” indicating that the phrases below thatgroup header 60 are the names of page description language files to be processed by the control task. In the present example, there are two page description language files: a file “letter_master” 62 and a file “all_maps” 64. Thejob ticket file 12 includes agroup header 66 “[letter_master],” under which are defined the location and attributes for that PDL file. Note that with this PDL file no attributes are defined and only the path location for the file is indicated. Another group header “[all_maps]” defines the path and attributes for the all_maps PDL file. Note that anattribute string 70 “SubTemplate=true” indicates that this file is a sub-template file and theattribute string 72 “Templates=South, East, West, Midwest” indicates that the file includes four sub-templates, named South, East, West and Midwest. - The job ticket also includes a
group header 74 “[MergeFiles]” identifying the names of the merge files to be used in the merge task. In the present case a single merge file is named “merge.” Below that, agroup header 78 “[merge]” is given, under which the attributes and location of the merge file is set forth. The attribute strings for this merge file indicate that the merge file is delimited and includes merge headers. The attribute strings also indicate that the records are delimited by a carriage-return/line-feed character and the particular fields in each record are delimited by a tab character. A complete description of the different attributes that can be defined for the PDL files is described in detail in the Appendix below. - As illustrated in FIG. 5, the
merge file 16 has a platform-independent data file that contains the “variable” data to be merged into the path defined in the PDL specification, and also includes names associated with the sub-templates to be merged into the PDL specification during the merge task. The merge file in the present example includes a plurality of rows of merge records separated by carriage-return/line space characters, where each record includes the following fields: “fname,” “lname,” “prefix,” “title,” “company,” “address,” “zip,” “region,” “city” and “state.” As will be described below, the data in the field “region” doubles as variable data and also as a name of a sub-template to be merged into the final bit maps. - As illustrated in FIG. 6, the designer will utilize an application program to create a document containing static data and variable data identifiers. The application program will then be directed to create a PDL specification of the document by the designer. The
variable data identifiers 80 each include a field name surrounded by special characters, “<<” and “ >>”, and may also include an attribute string 82 following the field name and special characters. The attribute string will be described below. The PDL specification generated by the application program will include the graphic states of thevariable data identifiers 80. These graphic states can include the font size (i.e., 12 point), the type-font (i.e., Helvetica), the orientation (i.e., horizontal), the location such as x and y coordinates, and the like. As discussed above, the control task will create a display list with the rendering commands for the static data in the PDL specification and will cache the graphic states for the variable data identifiers without transferring the rendering commands for the variable data identifiers to the display list. The variable data identifier in the bottom center portion of the page includes the “select” attribute, indicating to the control task that a sub-template bit map is to be inserted into the document. The field name “region” associated with this variable data identifier indicates that the sub-template name will be under the heading “region” in the merge file. - Referring to FIG. 5, the regions named in the merge file are South, East, West and Midwest. Therefore, referring to FIG. 4, the sub-templates having the name South, East, West and Midwest are found in the PDL file defined under the “all_maps” group header (68) in the job ticket. Note that the attributes defined under the “all_maps” group header do not include an attribute directing the location of the sub-template. Therefore, the lower left-hand corner of the sub-template merged into the final document will be directed by the locational graphic states of the variable data identifier stored along with the place holder in the graphic state cache.
- FIG. 7 illustrates the
sub-template PDL file 15, including the four sub-templates: South 84 a, East 84 b, West 84 c and Midwest 84 d. The merge task will access avariable data record 86 from themerge file 16 and a copy of the display list for thetemplate PDL file 25. As discussed above, the merge task will generate rendering commands for the variable data records in the merge file by applying the cached graphic states linked to the variable data records. These rendering commands will be merged into the merged display list along with the rendering commands from the display list for the template PDL file. The merge task will also merge the rendering commands from the display list of the sub-template named by the variable data records into the merged display list. The rendering task will process the rendering commands in the merged display list to generate the final merged bit map for the presentvariable data record 86. This bit map appears in FIG. 8. - Referring to FIGS. 5, 6 and8, the merge task will apply the cached graphic states linked to the variable data fields in the
variable data record 86 as follows. The first graphic state in the cache will be for the first variable data identifier 80 a. The field name for this variable data identifier 80 a is “fname,” which in the particular variable data record, corresponds to “Shannon.” Therefore, the final merged bit map will include a bit map of the text, “Shannon” 88 a, having the graphic states for the variable data identifier 80 a. Likewise, the second cached graphic state will be for the variable data identifier 80 b which includes a field name “lname,” corresponding to the term “Janzen” in the particularvariable data record 86. Therefore, the final merged bit map will include a bit map of the text, “Janzen” 88 b, -15 having the graphic states for the variable data identifier 80 b. Correspondingly, the remaining graphic states, except for those ofvariable data identifier 88 m, which is the variable data identifier including the sub-template attribute 82, will be processed in the same way resulting in bit maps 88 c-88 n in the merged bitmap. - When the merge task reaches the place holder in the graphic state cache associated with the variable data identifier80 m, it will refer to the merge record for the name of the sub-template under the field name “Region,” which in the present example is “South.” Referring to FIG. 7, the sub-template having the name “South” is sub-template 84 a. Accordingly, the merge file will then merge the rendering commands from the display list of the sub-template 84 a into the merged display list. Some or all of these rendering commands will also be modified by a graphic attribute corresponding to the location that the sub-template is to be merged into the merged bit map. As discussed above, this graphic attribute may be taken from the graphic state of the variable data identifier 80 m or may be defined in the job ticket file.
- The present invention also provides for the flowing of sub-templates into a path defined by the template specification. Such a feature is based upon the invention disclosed in U.S. patent application Ser. No. 08/897,467, filed Jul. 18, 1997. Specifically, the feature includes the steps of: associating a path defined by the template PDL specification with the variable data identifier with the “sub-template” attribute string; and merging the sub-template(s) into the path according to the path boundary and according to a predefined flow rule (as will be defined in the job ticket). The path may be associated with the attribute string, for example, by having the PDL command for the path immediately follow the PDL command for the attribute string in the PDL specification, or by having the PDL command for the path “grouped” with the PDL command for the attribute string using a GROUP command provided by the application program.
- The following Appendix provides a preferred compilation of commands and parameter definitions that can be specified in the
job ticket file 12 for the sub-template application as described above. Each entry provides a particular command header, the syntax for the command, any relevant remarks for the use of the command, examples, etc. As will be appreciated by one of ordinary skill in the art, the present invention includes any and all additional functions, features and attributes detailed in the Appendix.APPENDIX [PageDescriptionLanguageFile] A group that provides a list of tags which you create to describe the PDL file(s) to be used in the print job. Each tag will become a user-defined group to give additional information about a specific PDL file. Syntax [PageDescriptionLanguageFile] PDL File Tag A PDL File Tag B Remarks Required The number of tags listed equals the number of PDL files that VariScript is to interpret during the job. Every tag that appears under this initial [PageDescriptionLanguageFile] group will become a new group name in succeeding sections of the Job Ticket. Explanation PDL File Tag A Create a descriptive name for the first PDL file used in the print job. This tag is for use within the Job Ticket only and is not used outside of that context. PDL File Tag B Create a descriptive name for the next PDL file used in the print job. This tag is for use within the Job Ticket only and is not used outside of that context. Example [PageDescriptionLanguageFile] Cover Form Contents Form Letter Form A user-defined tag name for a group that provides information about a PDL file and corresponds to a descriptive tag that you created under the initial [PageDescriptionLanguageFile] group. Syntax [PDL File Tag] File Path = <other host access parameters> <VariScript rendering parameters> Templates = Sub Template = Sub Template Area = See Also Templates Remarks A separate [PDL File Tag] group is required for each descriptive tag listed under the initial [PageDescriptionLanguageFile] group. Case sensitivity of the values that you define depends on the host operating system. Explanation [PDL File Tag] Take the descriptive tag under the initial [PageDescriptionLanguageFile] group and write it here as a group name within brackets []. File Path = Write the drive, path, and file name for the PDL file being described. The format of your notation is dependent on your host computer. See the FilePath element description in Chapter 3.<other host access parameters> Define values for any other host access parameter for which the default value is not accurate for access to this PDL file. See the element descriptions in Chapter 3.<VariScript rendering parameters> Define a value for any VariScript rendering parameter which will be applied to all of the templates in this specific PDL file. These elements include PSAnchor, PSLength, PSN Planes, PSOrientation, PSResX, PSResY, PSRotation, PSScale, PSScaleX, PSScaleY, PSTranslateX, PSTranslate Y, and PSWidth. See the element descriptions in Chapter 4.Applying a VariScript rendering parameter here will override the definition of the same parameter in the configuration file and in the [JobSetup] group This definition, in turn, can be overridden by the definition of the same parameter in the [Template Tag] group. Templates = See the Templates element description. SubTemplate = See the Sub Template element description. SubTemplate Area = See the Sub Template Area element description. Example [Cover Form] File pate = forms/cover.ps Templates = tempA, tempB, tempC, tempD TEMPLATES An element that provides a list of descriptive tags which you create to represent the names of the templates in a PDL file. Syntax Templates = Template Tag A, Template Tag B, Template Tag Z Remarks Templates is an element within the user-defined [PDL File Tag] group. NOTE: Each descriptive template tag that you create is for use within the Job Ticket only and is not used outside of that context. The template tags must be unique within the print job and must appear in the order in which the templates are defined in the PDL file(s). A template that requires no further definition can be represented by a blank tag. Each tag that appears as a parameter of Templates may become a user- defined group name listed elsewhere in the Job Ticket. The Templates statement simply lets VariScript know that it is to look for user-defined groups and then provides the names (tags) of these groups. Therefore, in theory, a PDL file with ten pages could have up to ten template tags listed within the Templates element. If any templates need not be named, the order of templates can be preserved by inserting blank template tags into the list. Explanation Template Tag A Create a descriptive name for the first template in this PDL file. This tag is for use within the Job Ticket. Template Tag B Create a descriptive name for the next template in this PDL file. This tag is for use within the Job Ticket. And so on. Example Templates = tempA, tempB, ,tempD SUBTEMPLATE An element that identifies the templates within the specified PDL file as being subtemplates. Syntax SubTemplate = {True | False} Remarks Optional. A subtemplate is a template or PDL page that is used as an object to be inserted on another page. A default value for SubTemplate is False. Explanation {True | False} If all (or most) of the templates within the specified PDL ffie are to be identified as subtemplates, type True. If all (or most) of the templates within the specified PDL file are NOT subtemplates, type False. Example SubTemplate = True SUBTEMPLATE AREA An element that assigns a subtemplate name and describes the portion of a template to be used as a subtemplate. Syntax SubTemplate Area = Name “<SubName>” X <Units> <Unit Type>\ Y<Units × Unit Type> Width <Units> <Unit Type>\ Height <Unit> <Unit Type> See Also SubTemplate Remarks Optional if SubTemplate = True. Ignored if SubTemplate = False. This element may be used to specify what part of a template should be used as a subtemplate and to give that extracted portion a subtemplate name. When this element is defined at a PDL file level, the system will recognize the same extracted portion of each template in the file as being a subtemplate. Explanation Name “<SubName>” This value assigns a specific name to the subtemplate. Type the word Name followed by a space. For “<SubName>”, type the name to be assigned to this subtemplate. Enclose the subtemplate name in double quotation marks (“”). NOTE: A subtemplate will be known by the official name of the template, unless it is given another name through the SubTemplate Area element. The official template name is defined by the method of highest precedence. The template name of lowest precedence is the default system-generated template name, followed by the template name you physically define on the PDL template. Of highest precedence is the template name defined using the NewName element in the [Template Tag] group. Example: Name “mysub1” X<Unit> <Unit Type> This value identifies the subtemplate's offset, the horizontal distance between the left side of the template and the area to be extracted. Type the character X followed by a space. For <Units>, type the horizontal distance from the template's left side to the beginning of the area to be extracted. An X value of 0 represents a location flush along the left side of the template. Increasing the value of X locates the area to be extracted the defined distance to the right. This value is expressed in unitized format if the unit type is different from the default unit type defined in the Units element. Possible <Unit Type> values are: cm for centimeters dm for decimeters dots for dots ft for feet in for inch (default value) m for meters mils for mils mm for millimeter nm for nanometers pixels for pixels pts for points pulses for pulses yds for yards The default value for X is 0. Y <Units> <UnitType> This value identifies the vertical distance between the bottom of the template and the area to be extracted. Type the character Y followed by a space. For <Units>, type the vertical distance from the bottom of the template to the beginning of the area to be extracted. A Y value of 0 represents a location flush along the bottom of the template. Increasing the value of Y locates the area to be extracted the defined distance above the bottom of the template. The Y value is expressed in unitized format if the unit type is different from the default unit type defined in the Units element. Possible <Unit Type> values are listed above. The default value for Y is 0. Width <Unit> <Unit Type> This value identifies the width of the portion to be extracted (starting at the X, Y coordinates). Type the word Width followed by a space. For <Units>, type the width of area to be extracted from the template. This measurement is the X (horizontal) dimension of the area to be extracted. This default value for Width is equal to the width of the template. Heights <Units> <Unit Type> The value identifies the height (length) of the portion to be extracted (starting at the X, Y coordinates). Type the word Height followed by a space. For <Units>, type the height of the area to be extracted from the template. This measurement is the Y (vertical) dimension of the area to be extracted. This value is expressed in unitized format if the unit type is different from the default unit type defined in the Units element. Possible <Unit Type> values are listed above. The default value for Height is equal to the width of the template. Example [PageDescriptionLanguageFile] ps1 ps2 [ps1] File Path = /mydir/mypsfile.ps Templates = temp1, temp2 PSScale = .8 [ps2] File Path = /mydir/mysubtmp.ps SubTemplate = True Templates = temp3, temp4, temp5, temp6 SubTemplate Area - X 1in Y 2in Width 3in Height 4in This example depicts two PDL files. File ps1 is a “normal” PDL file containing two “normal” templates File ps2 is identified as a subtemplate file (SubTemplate = True). The same area (SubTemplateArea) on each template is ps2 will be defined as a subtemplate. This area represents a 3-inch wide by 4-inch long portion starting from 1 inch to the right and 2 inches above the lower left corner of the template. Since no Name <SubName> value is given, each subtemplate will take the official name of its template. [TEMPLATE TAG] A user-defined tag name for a group that provides information about a template and corresponds to a descriptive tag that you create within the Templates element. Syntax [Template Tag] <VariScript rendering parameters> New Name = <Template New Name> Sub Template = Sub Template Area = See Also Templates Remarks Optional. A separate [Template Tag] group is required for each descriptive tag listed in the Templates element which you will identify as a subtemplate or assign a new template name or a template-level marketing parameter. Explanation [Template Tag] Take the descriptive tag within the TempleNames element and write it here as a group name within brackets []. <VariScript rendering parameters> Define a value for any VariScript rendering parameter which will be applied to this specific template. These elements include PSAnchor, PSLength, PSNPlanes, PSOrientation, PSResX, PSResY, PSRotation, PSScale, PSScaleX; PSScale Y, PSTranslater X, PSTranslate Y, and PSWidth. See the element descriptions in Chapter 4. A rendering parameter applied within this group has the highest precedence. It will override the definition of the same parameter in the configuration file, in the [JobSetup] group, and in the [PDLFileTag] group. NewName = See the NewName element description SubTemplate = See the SubTemplate element description. SubTemplate Area = See the SubTemplate Area element description. Example [TempA] NewName = lotto_tikt PSScale = 0.8125 SubTemplate = True NEWNAME An element that defines a new name for the specified template. This new name overrides the system-generated default template name or the template name that you may have placed directly on this template within the PDL file. Syntax NewName = <TemplateNewName> Remarks Optional. The template receives its name in one of three ways: The system automatically generates a default template name. (lowest precedence) You can physically name the template when you are working in your design application (for example, QuarkXPress) before you output to a PDL file. You can define a new template name in the Job Ticket within the NewName element. (highest precedence) VariScript will recognize only one template name for each template. Therefore, a template name assigned by using a method of higher precedence will overwrite a name of lower precedence. For example, a name defined directly on the template will overwrite the system- generated default, and, in turn, be overwritten by a name defined using the NewName element. The NewName element does NOT have a default value. Explanation <TemplateNewName> Specify the template's new name. Example NewName = lotto_tikt SUBTEMPLATE An element that identifies this templates as being a subtemplate. Syntax SubTemplate = {True | False} Remarks Optional. A subtemplate is a template or PDL page that is used as an object to be inserted on another page. The default value for SubTemplate is False. Explanation {True | False} If this template is to be identified as a subtemplate, type True. If this template is NOT a subtemplate, type False. Example SubTemplate = True - While the forms of apparatus and procedure herein described constitute preferred embodiments of the invention, it is to be understood that the invention is not limited to such precise embodiments, and that variations can be made therein without departing from the scope of the invention.
Claims (8)
1. A method for generating a plurality of bitmaps comprising the steps of:
(a) generating a template page description language specification, the template specification including template data and associated graphic attributes defining how the template data is to appear on a printed page, the template specification including at least one variable data identifier;
(b) generating a plurality of sub-template page description language specifications, each sub-template specification including sub-template data and associated graphic attributes defining how the sub-template data is to appear on a portion of a printed page;
(c) interpreting the template specification so as to generate a plurality of template rendering commands, and during the interpreting step, identifying the variable data identifier;
(d) saving the plurality of template rendering commands into memory;
(e) associating the variable data identifier with the plurality sub-template specifications;
(f) accessing a first sub-template specification from the plurality of sub-template specifications;
(g) processing the first sub-template specification so as to generate a plurality of first sub-template rendering commands;
(h) accessing a copy of the plurality of template rendering commands from memory;
(i) merging the copy of the plurality of template rendering commands with the plurality of first sub-template rendering commands so as to provide a first merged plurality of rendering commands;
(j) generating a first merged bitmap from the first merged plurality of rendering commands;
(k) accessing a next sub-template specification from the plurality of sub-template specifications;
(l) processing the next sub-template specification so as to generate a plurality of first sub-template rendering commands;
(m) accessing a copy of the plurality of template rendering commands from memory;
(n) merging the copy of the plurality of template rendering commands with the plurality of next sub-template rendering commands so as to provide a next merged plurality of rendering commands; and
(o) generating a next merged bitmap from the next merged plurality of rendering commands.
2. The method of claim 1 , wherein steps (k) through (o) are repeated for the remaining plurality of sub-template specifications.
3. The method of claim 1 , wherein:
the variable data identifier includes a associated graphic attribute;
prior to the merging step (i), the graphic attribute associated with the variable data identifier is saved to memory;
the merging step (i) includes the steps of accessing the graphic attribute associated with the variable data identifier from memory and applying it to the plurality of first sub-template rendering commands so that a bitmap generated by the plurality of first sub-template rendering commands will include the graphic attribute associated with the variable data identifier; and
the merging step (p) includes the steps of accessing the graphic attribute associated with the variable data identifier from memory and applying it to the plurality of next sub-template rendering commands so that a bitmap generated by the plurality of next sub-template rendering commands will include the graphic attribute associated with the variable data identifier.
4. The method of claim 1 , wherein the variable data identifier includes an associated graphic attribute that is discarded during the processing step.
5. The method of claim 1 , wherein:
wherein the associating step includes the step of referring to a file containing a name corresponding to at least one of the locations and identities of sub-template specifications; and
the file includes a definition of a new graphic attribute to be applied to the sub-template specifications associated with the name.
6. The method of claim 5 , wherein the new graphic attribute includes the location of sub-template bitmaps in merged bitmaps.
7. The method of claim 5 , wherein the new graphic attribute includes the size of sub-template bitmaps in merged bitmaps.
8. A method for generating a plurality of bitmaps comprising the steps of:
(a) generating a template page description language specification, the template specification including template data and associated graphic attributes defining how the template data is to appear on a printed page, the template specification including at least one variable data identifier;
(b) generating a plurality of sub-template page description language specifications, each sub-template specification including sub-template data and associated graphic attributes defining how the sub-template data is to appear on a portion of a printed page;
(c) processing the template specification so as to generate a template bitmap, and during the processing step, identifying the variable data identifier;
(d) saving the template bitmap into memory;
(e) associating the variable data identifier with the plurality of sub-template specifications;
(f) accessing a first sub-template specification from the plurality of sub-template specifications;
(g) processing the first sub-template specification so as to generate a first sub-template bitmap;
(h) accessing a copy of the template bitmap from memory;
(i) merging the copy of the template bitmap with the first sub-template bitmap so as to provide a first merged bitmap;
(j) accessing a next sub-template specification from the plurality of sub-template specifications;
(k) processing the next sub-template specification so as to generate a next sub-template bitmap;
(l) accessing a copy of the template bitmap from memory; and
(m) merging the copy of the template bitmap with the next sub-template bitmap so as to provide a next merged bitmap.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/874,895 US20020149792A1 (en) | 1995-01-18 | 2001-06-05 | Method and system for merging variable text and images into bitmaps defined by a page description language |
US11/226,049 US7532355B2 (en) | 1995-01-18 | 2005-09-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/373,582 US5729665A (en) | 1995-01-18 | 1995-01-18 | Method of utilizing variable data fields with a page description language |
US08/896,899 US5937153A (en) | 1995-01-18 | 1997-07-18 | Method of utilizing variable data fields with a page description language |
US09/291,121 US6243172B1 (en) | 1995-01-18 | 1999-04-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
US09/874,895 US20020149792A1 (en) | 1995-01-18 | 2001-06-05 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/291,121 Continuation US6243172B1 (en) | 1995-01-18 | 1999-04-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/226,049 Continuation US7532355B2 (en) | 1995-01-18 | 2005-09-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Publications (1)
Publication Number | Publication Date |
---|---|
US20020149792A1 true US20020149792A1 (en) | 2002-10-17 |
Family
ID=23118950
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/291,121 Expired - Lifetime US6243172B1 (en) | 1995-01-18 | 1999-04-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
US09/874,895 Abandoned US20020149792A1 (en) | 1995-01-18 | 2001-06-05 | Method and system for merging variable text and images into bitmaps defined by a page description language |
US11/226,049 Expired - Fee Related US7532355B2 (en) | 1995-01-18 | 2005-09-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/291,121 Expired - Lifetime US6243172B1 (en) | 1995-01-18 | 1999-04-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/226,049 Expired - Fee Related US7532355B2 (en) | 1995-01-18 | 2005-09-14 | Method and system for merging variable text and images into bitmaps defined by a page description language |
Country Status (3)
Country | Link |
---|---|
US (3) | US6243172B1 (en) |
AU (1) | AU4454600A (en) |
WO (1) | WO2000062178A1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020036788A1 (en) * | 2000-09-12 | 2002-03-28 | Yasuhiro Hino | Image processing apparatus, server apparatus, image processing method and memory medium |
US20020186396A1 (en) * | 2001-06-07 | 2002-12-12 | Fuji Photo Film Co., Ltd. | Image processing apparatus, image processing system and image processing program storage medium |
US20040130751A1 (en) * | 2002-11-13 | 2004-07-08 | Klaus Hirtenreiter | Method and system to generate document templates with resource administration |
US20060106662A1 (en) * | 2004-11-12 | 2006-05-18 | Hewlett-Packard Development Company, L.P. | Rendering variable data at a point-of-purchase |
US20060156232A1 (en) * | 2004-12-07 | 2006-07-13 | Fabio Giannetti | Method and apparatus for preparing variable-data documents for publishing |
US20060184876A1 (en) * | 2005-02-14 | 2006-08-17 | Canon Kabushiki Kaisha | Information processing apparatus, control method therefor, and program |
US20080018935A1 (en) * | 1995-01-18 | 2008-01-24 | Gauthier Forrest P | Method and system for merging variable text and images into bitmaps defined by a page description language |
US20080155394A1 (en) * | 2006-10-31 | 2008-06-26 | Hewlett-Packard Development Company, L. P. | Variable data printing |
US20080239366A1 (en) * | 2007-03-28 | 2008-10-02 | Cyman Theodore F | Systems and methods for managing print jobs |
US20080320385A1 (en) * | 2006-09-29 | 2008-12-25 | Colorquick, L.L.C. | Graphical Object Insertion During Preparation of Production Data for a Print Job Using a Still Image Proxy of a Page Description Language Image File |
US20090153905A1 (en) * | 2007-12-18 | 2009-06-18 | Cyman Jr Theodore F | Systems and methods for processing of variable documents |
US20090290187A1 (en) * | 2008-05-23 | 2009-11-26 | Xerox Corporation | Enhancements to vi record job ticketing and processing |
US20100110467A1 (en) * | 2008-11-06 | 2010-05-06 | Coniglio Paul A | System and Method of Rasterizing PDF Files using Multiple Processors |
US20120036427A1 (en) * | 2005-02-28 | 2012-02-09 | Canon Kabushiki Kaisha | Document processing apparatus, document processing method and computer program |
US8184304B2 (en) | 2007-11-19 | 2012-05-22 | Moore Wallace North America, Inc. | System and method of operating a raster image processor |
EP2808830A1 (en) * | 2013-05-24 | 2014-12-03 | Seiko Epson Corporation | Printing apparatus, printing control system and control method of the printing apparatus |
US9489155B2 (en) * | 2014-04-30 | 2016-11-08 | Riso Kagaku Corporation | Image processing device |
US9817620B2 (en) | 2014-12-19 | 2017-11-14 | Canon Kabushiki Kaisha | Predictive object-sequence caching from prior page content |
US20240005083A1 (en) * | 2021-04-19 | 2024-01-04 | Fujian Foxit Software Development Joint Stock Co., Ltd. | Method and system for merging pdf files in a large batch |
Families Citing this family (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6952801B2 (en) * | 1995-06-07 | 2005-10-04 | R.R. Donnelley | Book assembly process and apparatus for variable imaging system |
US6912311B2 (en) * | 1998-06-30 | 2005-06-28 | Flashpoint Technology, Inc. | Creation and use of complex image templates |
US6791572B1 (en) * | 1999-06-18 | 2004-09-14 | Phoenix Technologies Ltd. | Generating media output during BIOS boot-up |
US7278094B1 (en) | 2000-05-03 | 2007-10-02 | R. R. Donnelley & Sons Co. | Variable text processing for an electronic press |
US6542173B1 (en) * | 2000-01-19 | 2003-04-01 | Xerox Corporation | Systems, methods and graphical user interfaces for printing object optimized images based on document type |
JP2003522359A (en) | 2000-02-03 | 2003-07-22 | エックスエムパイ・インコーポレーテッド | System and method for efficiently generating dynamic documents |
US7227655B1 (en) * | 2000-05-01 | 2007-06-05 | Ricoh Company, Ltd. | Utilizing otherwise unused space on cover or partition sheets |
SE517132C2 (en) * | 2000-06-27 | 2002-04-16 | Printon Ab | Procedure and system for creating a PDF document |
US7495794B1 (en) * | 2000-07-21 | 2009-02-24 | Hewlett-Packard Development Company, L.P. | System for printing a document with recurring images |
US6751589B1 (en) * | 2000-09-18 | 2004-06-15 | Hewlett-Packard Development Company, L.P. | Voice-actuated generation of documents containing photographic identification |
JP3862949B2 (en) * | 2000-11-28 | 2006-12-27 | 株式会社マツモト | Printed material production method and printed material obtained thereby |
US7532357B2 (en) * | 2000-12-26 | 2009-05-12 | Xerox Corporation | Job submission system and method for controlling multiple job renderings with a single master or “super” ticket |
US7405836B2 (en) * | 2000-12-26 | 2008-07-29 | Xerox Corporation | Job submission system and method for controlling multiple job renderings with a single master or “super” ticket |
US20030226114A1 (en) * | 2001-02-20 | 2003-12-04 | Sharp Laboratories Of America, Inc. | System and method for composing documents |
US6957423B1 (en) * | 2001-05-15 | 2005-10-18 | Xilinx, Inc. | Method of inlining a VHDL function call into Verilog |
US7181747B2 (en) | 2001-10-01 | 2007-02-20 | Canon Kabushiki Kaisha | Method and device for executing a function with selection and sending of multiple results in a client-server environment |
FR2830349B1 (en) * | 2001-10-01 | 2004-09-10 | Canon Kk | METHOD AND DEVICE FOR EXECUTING A FUNCTION IN A COMPUTER SERVER, SAID FUNCTION RETURNING SELECTED MULTIPLE RESULTS |
US7327487B2 (en) * | 2001-10-23 | 2008-02-05 | Eastman Kodak Company | Banded compositor for variable data |
US6965445B2 (en) * | 2002-01-16 | 2005-11-15 | Xerox Corporation | Systems and methods of automating job ticketing in printing, copying or imaging devices |
US20030189725A1 (en) * | 2002-04-09 | 2003-10-09 | Nexpress Solutions Llc | Variable data printing using family groupings |
US20030189726A1 (en) * | 2002-04-09 | 2003-10-09 | Nexpress Solutions Llc | Variable data printing dynamic imposition template |
US7375842B2 (en) * | 2002-04-09 | 2008-05-20 | Eastman Kodak Company | Variable data printing using variants |
US20030189727A1 (en) * | 2002-04-09 | 2003-10-09 | Nexpress Solutions Llc | Method and apparatus for using fields of data to organize variable data print jobs |
US7213245B2 (en) * | 2002-05-14 | 2007-05-01 | Microsoft Corporation | Software on demand system |
US20030237054A1 (en) * | 2002-06-21 | 2003-12-25 | Nexpress Solutions Llc | Concept for automated scatter proofing of content elements used in personalized print jobs |
US20040007868A1 (en) * | 2002-07-10 | 2004-01-15 | Sue Ann Werling | Methods and devices for identifying individual products |
US20030011799A1 (en) * | 2002-07-29 | 2003-01-16 | Kobziar Andrew M | Command protocol for two color thermal printing |
JP3938530B2 (en) * | 2002-08-23 | 2007-06-27 | 富士フイルム株式会社 | Variable printing processing apparatus and variable printing processing program |
US20040066527A1 (en) * | 2002-10-02 | 2004-04-08 | Nexpress Solutions Llc | Finish verification in printing |
EP1522948A1 (en) * | 2003-10-10 | 2005-04-13 | JetMobile SAS | Method for generating barcode patterns |
GB2408612A (en) * | 2003-11-26 | 2005-06-01 | Hewlett Packard Development Co | Incremental rendering of documents |
US7434160B2 (en) * | 2003-12-03 | 2008-10-07 | Hewlett-Packard Development Company, L.P. | PDF document to PPML template translation |
US20050179945A1 (en) * | 2004-02-12 | 2005-08-18 | Sharp Laboratories Of America, Inc. | System and method for variable text overlay |
US7817302B2 (en) * | 2004-03-26 | 2010-10-19 | Lexmark International, Inc. | Optimizing raster operation functions during print job processing |
US20050213142A1 (en) * | 2004-03-26 | 2005-09-29 | Clark Raymond E | Optimization techniques during processing of print jobs |
US7385729B2 (en) * | 2004-03-26 | 2008-06-10 | Lexmark International, Inc. | Optimization techniques during processing of print jobs |
US7835030B2 (en) * | 2004-03-26 | 2010-11-16 | Lexmark International, Inc. | Processing print jobs |
US7859716B2 (en) * | 2004-03-26 | 2010-12-28 | Lexmark International, Inc. | Optimizing to-be-printed objects during print job processing |
AU2005201495B2 (en) * | 2004-04-13 | 2007-04-05 | Canon Kabushiki Kaisha | Display list colour conversion |
GB2430061A (en) * | 2005-09-08 | 2007-03-14 | Hewlett Packard Development Co | Templates for variable data printing |
US8438476B2 (en) * | 2005-10-14 | 2013-05-07 | Uhlig Llc | Dynamic variable-content publishing |
US7793285B2 (en) * | 2006-03-31 | 2010-09-07 | Ricoh Company, Ltd. | Web installer driver and management through a remote network |
US8264716B2 (en) * | 2006-04-26 | 2012-09-11 | Kyocera Document Solutions Inc. | Ringtone, voice, and sound notification of printer status |
US20070253027A1 (en) * | 2006-04-27 | 2007-11-01 | Hiebert Steven P | System and method for on-press merging of variable data printing documents |
US8208169B2 (en) | 2006-05-24 | 2012-06-26 | Lexmark International, Inc. | Method and system for rendering a transparent object in an image |
JP4764271B2 (en) * | 2006-06-30 | 2011-08-31 | 株式会社リコー | Image forming apparatus, tray ID assigning method thereof, program, and recording medium |
US8711372B2 (en) * | 2006-08-31 | 2014-04-29 | Ricoh Co., Ltd. | Techniques for image segment accumulation in document rendering |
US8261259B2 (en) | 2007-03-01 | 2012-09-04 | Ricoh Company, Ltd. | Dynamic printing system, apparatus and method |
US20080263071A1 (en) * | 2007-04-19 | 2008-10-23 | Sharp Laboratories Of America, Inc. | Systems and methods for driverless imaging of documents |
US8120803B2 (en) * | 2007-05-24 | 2012-02-21 | Ricoh Company, Ltd. | Dynamic advertisement allocation |
US8228540B2 (en) * | 2007-07-31 | 2012-07-24 | Esko Ip Nv | Rasterizing variable and non-variable data for printing |
US8786628B2 (en) * | 2007-09-14 | 2014-07-22 | Microsoft Corporation | Rendering electronic chart objects |
US20090080025A1 (en) * | 2007-09-20 | 2009-03-26 | Boris Aronshtam | Parallel processing of page description language |
US20090086256A1 (en) * | 2007-10-02 | 2009-04-02 | Xerox Corporation | Conditional content printing |
JP5252933B2 (en) * | 2008-01-24 | 2013-07-31 | キヤノン株式会社 | Document processing apparatus, document processing method, and program |
US8160992B2 (en) | 2008-05-15 | 2012-04-17 | Xerox Corporation | System and method for selecting a package structural design |
US8915831B2 (en) * | 2008-05-15 | 2014-12-23 | Xerox Corporation | System and method for automating package assembly |
US9132599B2 (en) | 2008-09-05 | 2015-09-15 | Xerox Corporation | System and method for image registration for packaging |
US7983792B2 (en) * | 2008-10-22 | 2011-07-19 | Xerox Corporation | Method and system for the production of variable-dimensional printed substrates |
US8174720B2 (en) * | 2008-11-06 | 2012-05-08 | Xerox Corporation | Packaging digital front end |
US9493024B2 (en) * | 2008-12-16 | 2016-11-15 | Xerox Corporation | System and method to derive structure from image |
US20100202008A1 (en) * | 2009-02-11 | 2010-08-12 | Boris Aronshtam | Comprehensive print job skeleton creation |
US8170706B2 (en) | 2009-02-27 | 2012-05-01 | Xerox Corporation | Package generation system |
US8638343B2 (en) * | 2009-04-30 | 2014-01-28 | Microsoft Corporation | Data visualization platform performance optimization |
US9250926B2 (en) * | 2009-04-30 | 2016-02-02 | Microsoft Technology Licensing, Llc | Platform extensibility framework |
US8775130B2 (en) * | 2009-08-27 | 2014-07-08 | Xerox Corporation | System for automatically generating package designs and concepts |
US20110096367A1 (en) * | 2009-10-23 | 2011-04-28 | Jason Charles Walp | Print Settings Verification Mechanism |
US20110119570A1 (en) * | 2009-11-18 | 2011-05-19 | Xerox Corporation | Automated variable dimension digital document advisor |
US9082207B2 (en) * | 2009-11-18 | 2015-07-14 | Xerox Corporation | System and method for automatic layout of printed material on a three-dimensional structure |
US8328706B2 (en) * | 2009-12-17 | 2012-12-11 | Xerox Corporation | System and method for converting a printed substrate |
US8643874B2 (en) * | 2009-12-18 | 2014-02-04 | Xerox Corporation | Method and system for generating a workflow to produce a dimensional document |
US8572496B2 (en) * | 2010-04-27 | 2013-10-29 | Go Daddy Operating Company, LLC | Embedding variable fields in individual email messages sent via a web-based graphical user interface |
US8488183B2 (en) * | 2011-03-10 | 2013-07-16 | Konica Minolta Laboratory U.S.A., Inc. | Moving labels in graphical output to avoid overprinting |
JP5686292B2 (en) * | 2011-03-29 | 2015-03-18 | 富士ゼロックス株式会社 | Information processing apparatus and processing program |
US8773428B2 (en) | 2011-06-08 | 2014-07-08 | Robert John Rolleston | Systems and methods for visually previewing variable information 3-D structural documents or packages |
US9001373B2 (en) * | 2012-03-30 | 2015-04-07 | Xerox Corporation | Parallel printing system |
US9052854B2 (en) * | 2012-03-30 | 2015-06-09 | Xerox Corporation | Parallel printing system |
US8994734B2 (en) | 2012-07-31 | 2015-03-31 | Xerox Corporation | Package definition system |
US9158875B2 (en) | 2012-07-31 | 2015-10-13 | Xerox Corporation | Package definition system |
US8757479B2 (en) | 2012-07-31 | 2014-06-24 | Xerox Corporation | Method and system for creating personalized packaging |
JP6036040B2 (en) * | 2012-09-07 | 2016-11-30 | セイコーエプソン株式会社 | RECORDING DEVICE, RECORDING DEVICE CONTROL METHOD, AND PROGRAM |
US9314986B2 (en) | 2012-10-31 | 2016-04-19 | Xerox Corporation | Method and system for applying an adaptive perforation cut to a substrate |
US9245209B2 (en) | 2012-11-21 | 2016-01-26 | Xerox Corporation | Dynamic bleed area definition for printing of multi-dimensional substrates |
US10380239B2 (en) * | 2013-12-03 | 2019-08-13 | Sharethrough Inc. | Dynamic native advertisment insertion |
US9912767B1 (en) | 2013-12-30 | 2018-03-06 | Sharethrough Inc. | Third-party cross-site data sharing |
US9760659B2 (en) | 2014-01-30 | 2017-09-12 | Xerox Corporation | Package definition system with non-symmetric functional elements as a function of package edge property |
JP6320146B2 (en) * | 2014-04-17 | 2018-05-09 | キヤノン株式会社 | Information processing system, information processing apparatus, information processing method, and program |
US9892212B2 (en) | 2014-05-19 | 2018-02-13 | Xerox Corporation | Creation of variable cut files for package design |
US9565147B2 (en) | 2014-06-30 | 2017-02-07 | Go Daddy Operating Company, LLC | System and methods for multiple email services having a common domain |
US20160110321A1 (en) * | 2014-10-17 | 2016-04-21 | Karol Kalisz | Application customization through linked embedded areas |
JP6168311B2 (en) * | 2015-01-13 | 2017-07-26 | コニカミノルタ株式会社 | Image forming apparatus, image forming system, and image forming method |
JP2016139982A (en) * | 2015-01-28 | 2016-08-04 | 富士ゼロックス株式会社 | Image processing apparatus and image forming system |
US9916401B2 (en) | 2015-05-18 | 2018-03-13 | Xerox Corporation | Creation of cut files for personalized package design using multiple substrates |
US9916402B2 (en) | 2015-05-18 | 2018-03-13 | Xerox Corporation | Creation of cut files to fit a large package flat on one or more substrates |
US11605187B1 (en) * | 2020-08-18 | 2023-03-14 | Corel Corporation | Drawing function identification in graphics applications |
CN113408657B (en) * | 2021-07-14 | 2024-01-30 | 福建天晴在线互动科技有限公司 | Method and system for dynamic planning and merging of game atlas |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4944614A (en) * | 1983-07-18 | 1990-07-31 | Kanzaki Paper Mfg. | Form overlay type printing apparatus |
US5103490A (en) * | 1990-06-13 | 1992-04-07 | National Computer Systems, Inc. | Method and apparatus for storing and merging multiple optically scanned images |
US5134669A (en) * | 1990-06-13 | 1992-07-28 | National Computer Systems | Image processing system for documentary data |
US5157765A (en) * | 1989-11-15 | 1992-10-20 | International Business Machines Corporation | Method and apparatus for pipelined parallel rasterization |
US5202206A (en) * | 1991-10-04 | 1993-04-13 | Xerox Corporation | Process for simultaneous printing of fixed data and variable data |
US5222236A (en) * | 1988-04-29 | 1993-06-22 | Overdrive Systems, Inc. | Multiple integrated document assembly data processing system |
US5291243A (en) * | 1993-02-05 | 1994-03-01 | Xerox Corporation | System for electronically printing plural-color tamper-resistant documents |
US5455599A (en) * | 1993-11-02 | 1995-10-03 | Taligent Inc. | Object-oriented graphic system |
US5459819A (en) * | 1993-09-24 | 1995-10-17 | Eastman Kodak Company | System for custom imprinting a variety of articles with images obtained from a variety of different sources |
US5459826A (en) * | 1990-05-25 | 1995-10-17 | Archibald; Delbert M. | System and method for preparing text and pictorial materials for printing using predetermined coding and merging regimen |
US5483624A (en) * | 1992-03-27 | 1996-01-09 | Monarch Marking Systems, Inc. | Programmable hand held labeler |
US5500928A (en) * | 1993-03-01 | 1996-03-19 | Xionics Document Technologies, Inc. | Digital printing system and process using adaptive compression |
US5506697A (en) * | 1990-01-05 | 1996-04-09 | Symbol Technologies, Inc. | Apparatus for processing human-readable and machine-readable documents |
US5544287A (en) * | 1993-06-03 | 1996-08-06 | Monarch Marking Systems, Inc. | On-line barcode printer system with multi-level user printer commands |
US5611035A (en) * | 1992-10-16 | 1997-03-11 | International Business Machines Corporation | Relational data base system for conveniently constructing graphical images |
US5729665A (en) * | 1995-01-18 | 1998-03-17 | Varis Corporation | Method of utilizing variable data fields with a page description language |
US5740338A (en) * | 1995-11-13 | 1998-04-14 | Varis Corporation | Method for merging variable image data into a template image |
US5796411A (en) * | 1995-07-10 | 1998-08-18 | Moore Business Forms, Inc. | High resolution real time raster image processing system and method |
US5852673A (en) * | 1996-03-27 | 1998-12-22 | Chroma Graphics, Inc. | Method for general image manipulation and composition |
US5926185A (en) * | 1996-05-03 | 1999-07-20 | Barco Graphics N.V. | Method for processing a set of page description language commands to reduce complexity |
US6016380A (en) * | 1992-09-24 | 2000-01-18 | Avid Technology, Inc. | Template-based edit decision list management system |
US6064397A (en) * | 1994-09-13 | 2000-05-16 | Agfa Gevaert N.V. | Method for creating multiple documents having identical background regions and page specific image regions |
US6243172B1 (en) * | 1995-01-18 | 2001-06-05 | Varis Corporation | Method and system for merging variable text and images into bitmaps defined by a page description language |
Family Cites Families (145)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2002A (en) * | 1841-03-12 | Tor and planter for plowing | ||
US2005A (en) * | 1841-03-16 | Improvement in the manner of constructing molds for casting butt-hinges | ||
US2004A (en) * | 1841-03-12 | Improvement in the manner of constructing and propelling steam-vessels | ||
US3576367A (en) | 1968-09-06 | 1971-04-27 | Ibm | Machine for preparing documents |
US3744899A (en) | 1968-09-06 | 1973-07-10 | Ibm | Method of preparing documents |
US4085445A (en) | 1976-06-07 | 1978-04-18 | International Business Machines Corporation | Text merge with copies and envelopes |
US4300206A (en) | 1977-06-30 | 1981-11-10 | International Business Machines Corporation | Flexible text and image generator for a raster printer |
US4203154A (en) | 1978-04-24 | 1980-05-13 | Xerox Corporation | Electronic image processing system |
JPS54153442A (en) | 1978-05-22 | 1979-12-03 | Nissan Motor Co Ltd | Steering lock apparatus |
JPS554073A (en) | 1978-06-26 | 1980-01-12 | Konishiroku Photo Ind Co Ltd | Original position assignment mechanism of information compound recorder |
JPS5588129A (en) | 1978-12-27 | 1980-07-03 | Fuji Photo Film Co Ltd | Form synthesizer-recorder |
JPS5636676A (en) | 1979-09-03 | 1981-04-09 | Ricoh Co Ltd | Copying machine |
US4454576A (en) | 1981-05-18 | 1984-06-12 | International Business Machines Corporation | Report preparation |
US4493049A (en) | 1981-06-05 | 1985-01-08 | Xerox Corporation | Shared resource clustered printing system |
US4417322A (en) | 1981-06-16 | 1983-11-22 | International Business Machines Corporation | Report generation control system for text processing machines |
US4445795A (en) | 1981-09-24 | 1984-05-01 | International Business Machines | Method and apparatus for merge processing in a text processing system |
US4441829A (en) | 1981-09-24 | 1984-04-10 | International Business Machines | Method for performing a multiple page get operation in a text processing system |
US4470129A (en) | 1982-01-29 | 1984-09-04 | International Business Machines Corporation | Page modification method in a printer subsystem of the partial page buffer composing type |
JPS5947627A (en) | 1982-09-10 | 1984-03-17 | Brother Ind Ltd | Text processor |
US4460975A (en) | 1982-09-17 | 1984-07-17 | Saga Data, Inc. | Easily accessible formating of computer printouts |
JPS59128666A (en) | 1983-01-14 | 1984-07-24 | Fuji Xerox Co Ltd | Issuing device of slip, form or the like |
US4539653A (en) | 1983-04-11 | 1985-09-03 | International Business Machines Corporation | Formatting text/graphics using plural independent formatting mechanisms |
US4509826A (en) | 1983-04-11 | 1985-04-09 | Xerox Corporation | Optical image staggering/destaggering arrangement for multiple array scanning system |
US4959769A (en) | 1983-10-03 | 1990-09-25 | Wang Laboratories, Inc. | Structures and methods for representing and processing documents |
US4996662A (en) | 1983-10-03 | 1991-02-26 | Wang Laboratories, Inc. | Method for generating document using tables storing pointers and indexes |
US4870611A (en) | 1983-11-15 | 1989-09-26 | International Business Machines Corporation | Apparatus and method for system printing mode control |
US4809220A (en) | 1984-03-30 | 1989-02-28 | Wang Laboratories, Inc. | Electronic processing system using printer and microprocessor to create forms template with pre-printed forms |
US4723210A (en) | 1984-08-30 | 1988-02-02 | International Business Machines Corp. | Superblock structure in a multiple in a data editor |
US4723211A (en) | 1984-08-30 | 1988-02-02 | International Business Machines Corp. | Editing of a superblock data structure |
US4723209A (en) | 1984-08-30 | 1988-02-02 | International Business Machines Corp. | Flow attribute for text objects |
US4739477A (en) | 1984-08-30 | 1988-04-19 | International Business Machines Corp. | Implicit creation of a superblock data structure |
US4839814A (en) | 1985-01-29 | 1989-06-13 | Moore Business Forms, Inc. | Size independent modular web processing line and modules |
US4651278A (en) | 1985-02-11 | 1987-03-17 | International Business Machines Corporation | Interface process for an all points addressable printer |
US5282269A (en) * | 1985-09-27 | 1994-01-25 | Oce-Nederland B.V. | Raster image memory |
US4745560A (en) | 1985-10-15 | 1988-05-17 | International Business Machines Corporation | Method of controlling a bit-image printer |
US5222211A (en) | 1986-01-24 | 1993-06-22 | Siemens Nixdorf Informationssysteme Ag | Form generating method and apparatus |
US4745415A (en) | 1986-03-07 | 1988-05-17 | Minolta Camera Kabushiki Kaisha | Thermal printer having thermal head for transferring ink of ink film onto transfer paper |
US4864516A (en) | 1986-03-10 | 1989-09-05 | International Business Machines Corporation | Method for implementing an on-line presentation in an information processing system |
US5157773A (en) | 1986-03-14 | 1992-10-20 | Canon Kabushiki Kaisha | Image data output apparatus |
NL8600888A (en) | 1986-04-09 | 1987-11-02 | Oce Nederland Bv | DEVICE AND METHOD FOR PRINTING INFORMATION. |
JPS6320622A (en) | 1986-07-15 | 1988-01-28 | Brother Ind Ltd | Document editing device |
JP2690075B2 (en) | 1986-08-21 | 1997-12-10 | 松下電送 株式会社 | Color image recording device |
US4718784A (en) | 1986-11-10 | 1988-01-12 | Electronic Programming Corporation | Rating plate printing apparatus and method |
US5218539A (en) | 1986-12-01 | 1993-06-08 | International Business Machines Corporation | Forms processor with controlled remote revision |
US5290109A (en) * | 1986-12-26 | 1994-03-01 | Seiko Epson Corporation | Electronic typewriter for printing of documents having a fixed format |
US4903229A (en) | 1987-03-13 | 1990-02-20 | Pitney Bowes Inc. | Forms generating and information retrieval system |
US4862386A (en) | 1987-03-13 | 1989-08-29 | Pitney Bowes Inc. | Apparatus for preparing a letter |
DE3884271T2 (en) | 1987-04-28 | 1994-03-31 | Canon Kk | Device for multi-image generation. |
US4770972A (en) | 1987-05-19 | 1988-09-13 | The Mead Corporation | Imaging process involving hardening of imaging web border area photosensitive microcapsules and an apparatus useful therein |
US4825251A (en) | 1987-05-19 | 1989-04-25 | The Mead Corporation | Imaging process involving hardening of imaging web border area photosensitive microcapsules and an apparatus useful therein |
US4912491A (en) | 1987-05-30 | 1990-03-27 | Canon Kabushiki Kaisha | Apparatus for forming superimposed images |
US5226161A (en) | 1987-08-21 | 1993-07-06 | Wang Laboratories, Inc. | Integration of data between typed data structures by mutual direct invocation between data managers corresponding to data types |
US5206951A (en) * | 1987-08-21 | 1993-04-27 | Wang Laboratories, Inc. | Integration of data between typed objects by mutual, direct invocation between object managers corresponding to object types |
US4857955A (en) | 1987-09-28 | 1989-08-15 | Eastman Kodak Company | Electronic printer apparatus with intelligent accent color |
US4992956A (en) | 1987-10-08 | 1991-02-12 | Advanced Micro Devices, Inc. | Apparatus for assembling data for supply to a scanning output device |
US4963459A (en) | 1987-10-08 | 1990-10-16 | The Mead Corporation | System for registering to a moving web |
JP2633877B2 (en) | 1987-11-30 | 1997-07-23 | キヤノン株式会社 | Image forming device |
US5107423A (en) | 1988-03-26 | 1992-04-21 | Brother Kogyo Kabushiki Kaisha | Document processing device with merge function |
US4939674A (en) | 1988-04-22 | 1990-07-03 | Engineered Data Products, Inc. | Label generation apparatus |
US4933880A (en) | 1988-06-15 | 1990-06-12 | International Business Machines Corp. | Method for dynamically processing non-text components in compound documents |
US5204946A (en) | 1988-06-17 | 1993-04-20 | Canon Kabushiki Kaisha | Mixed text and image data processing |
US4969093A (en) | 1988-06-30 | 1990-11-06 | International Business Machines Corporation | Method of data stream construct management utilizing format shells and shell fragments |
GB2220511B (en) | 1988-07-08 | 1992-04-15 | Canon Kk | Recording control apparatus |
JP2796628B2 (en) | 1988-11-29 | 1998-09-10 | カシオ計算機株式会社 | Printing device |
US5208906A (en) | 1988-12-30 | 1993-05-04 | Chipsoft Ca, Corp. | Method and apparatus for representing bordered areas of a generic form with records |
JPH02185475A (en) | 1989-01-13 | 1990-07-19 | Casio Electron Mfg Co Ltd | Printing apparatus |
JPH0628022B2 (en) | 1989-02-09 | 1994-04-13 | セイコー電子工業株式会社 | Character / graphic output device |
JP2855207B2 (en) | 1989-02-23 | 1999-02-10 | カシオ計算機株式会社 | Form output device |
US5033009A (en) | 1989-03-03 | 1991-07-16 | Dubnoff Steven J | System for generating worksheet files for electronic spreadsheets |
US5025396A (en) | 1989-03-21 | 1991-06-18 | International Business Machines Corporation | Method and apparatus for merging a digitized image with an alphanumeric character string |
JPH0792796B2 (en) | 1989-03-30 | 1995-10-09 | ブラザー工業株式会社 | Document creation device |
US5280574A (en) * | 1989-05-26 | 1994-01-18 | Hitachi, Ltd. | Text document management method adapted for generating plural text documents derived from the same original text document |
US4965748A (en) | 1989-07-12 | 1990-10-23 | Ricoh Company, Ltd. | Laser printer controller flexible frame buffer architecture which allows offsetting different input/output data widths |
JPH0345076A (en) | 1989-07-12 | 1991-02-26 | Minolta Camera Co Ltd | Processing system for picture data |
US5287444A (en) * | 1989-08-14 | 1994-02-15 | International Business Machines Corporation | Message processing system |
JP2501355B2 (en) | 1989-09-07 | 1996-05-29 | 株式会社テック | Printer |
US5001653A (en) | 1989-09-08 | 1991-03-19 | International Business Machines Corporation | Merging plotter graphics within a text environment on a page printer |
US4963899A (en) | 1989-10-11 | 1990-10-16 | Eastman Kodak Company | Method and apparatus for image frame registration |
US5148366A (en) | 1989-10-16 | 1992-09-15 | Medical Documenting Systems, Inc. | Computer-assisted documentation system for enhancing or replacing the process of dictating and transcribing |
US5181162A (en) | 1989-12-06 | 1993-01-19 | Eastman Kodak Company | Document management and production system |
US5136316A (en) | 1989-12-29 | 1992-08-04 | Am International Incorporated | Printing press and method |
US5043749A (en) | 1989-12-29 | 1991-08-27 | Am International Inc. | Printing press and method |
US5222235A (en) | 1990-02-01 | 1993-06-22 | Bmc Software, Inc. | Databases system for permitting concurrent indexing and reloading of data by early simulating the reload process to determine final locations of the data |
DE4003907A1 (en) | 1990-02-09 | 1991-08-14 | Schwarzkopf Gmbh Hans | 5-Tri:fluoromethyl-1,3-di:aminobenzene(s) as hair colourant - have good stability to heat and light, and are compatible with other colourants for shade modification |
US5404294A (en) * | 1990-02-26 | 1995-04-04 | Karnik; Jayant D. | Tag method for moving information between computers & forms |
GB9005697D0 (en) | 1990-03-14 | 1990-05-09 | Digital Equipment Int | Data format conversion |
JPH0412874A (en) | 1990-05-01 | 1992-01-17 | Minolta Camera Co Ltd | Printer controlling apparatus |
US5060980A (en) | 1990-05-30 | 1991-10-29 | Xerox Corporation | Form utilizing encoded indications for form field processing |
JP2855797B2 (en) * | 1990-06-15 | 1999-02-10 | 富士ゼロックス株式会社 | Document processing device |
US5237655A (en) | 1990-07-05 | 1993-08-17 | Eastman Kodak Company | Raster image processor for all points addressable printer |
US5801716A (en) * | 1990-08-16 | 1998-09-01 | Canon Kabushiki Kaisha | Pipeline structures for full-color computer graphics |
US5241464A (en) | 1990-08-17 | 1993-08-31 | Moore Business Forms, Inc. | Desktop forms order system |
JP2895184B2 (en) * | 1990-08-22 | 1999-05-24 | 株式会社日立製作所 | Document processing system and document processing method |
US5077795A (en) | 1990-09-28 | 1991-12-31 | Xerox Corporation | Security system for electronic printing systems |
US5191429A (en) | 1990-09-28 | 1993-03-02 | Xerox Corporation | Electronic printing system for printing multiple images with determination of the maximum number of reduced size images to be optimally printed on a sheet of detected size without interference |
KR950000233B1 (en) | 1990-09-28 | 1995-01-12 | 미쓰비시덴키 가부시키가이샤 | Distributor assembly for internal combustion engine |
US5142667A (en) | 1990-09-28 | 1992-08-25 | Xerox Corporation | Resource and memory management algorithms for electric printing and electronic reprographic systems |
JP2554395B2 (en) * | 1990-11-30 | 1996-11-13 | 株式会社日立製作所 | Print format management system |
US5490243A (en) * | 1990-12-13 | 1996-02-06 | F3 Software Corporation | Data processing system for multi-platform print control and electronic data fill |
US5239625A (en) | 1991-03-05 | 1993-08-24 | Rampage Systems, Inc. | Apparatus and method to merge images rasterized at different resolutions |
US5231698A (en) | 1991-03-20 | 1993-07-27 | Forcier Mitchell D | Script/binary-encoded-character processing method and system |
US5384886A (en) * | 1991-04-01 | 1995-01-24 | Xerox Corporation | Process for electronically printing envelopes |
US5243518A (en) | 1991-05-03 | 1993-09-07 | Xerox Corporation | Document services architecture |
US5143362A (en) | 1991-07-15 | 1992-09-01 | Moore Business Forms, Inc. | Publication personalization |
JP2964469B2 (en) * | 1991-07-20 | 1999-10-18 | ブラザー工業株式会社 | Printing device |
US5204916A (en) | 1991-08-06 | 1993-04-20 | Eastman Kodak Company | Tile-oriented technique for collectively performing image rotation, scaling and digital halftone screening |
US5506985A (en) * | 1991-10-17 | 1996-04-09 | Ricoh Company, Ltd. | Method and apparatus for format conversion of a hierarchically structured page description language document |
US5504891A (en) * | 1991-10-17 | 1996-04-02 | Ricoh Company, Ltd. | Method and apparatus for format conversion of a hierarchically structured page description language document |
US5487165A (en) * | 1992-04-30 | 1996-01-23 | Ricoh Company, Ltd. | Standard page description language cleartext structure generator |
EP0539135B1 (en) * | 1991-10-24 | 1997-12-29 | Canon Kabushiki Kaisha | Printing apparatus |
US5303341A (en) * | 1991-10-29 | 1994-04-12 | Xerox Corporation | Video processor for a printing apparatus |
US5276799A (en) * | 1991-10-29 | 1994-01-04 | Xerox Corporation | Expandable electronic subsystem for a printing machine |
US5307458A (en) * | 1991-12-23 | 1994-04-26 | Xerox Corporation | Input/output coprocessor for printing machine |
US5235654A (en) | 1992-04-30 | 1993-08-10 | International Business Machines Corporation | Advanced data capture architecture data processing system and method for scanned images of document forms |
US5483629A (en) * | 1992-04-30 | 1996-01-09 | Ricoh Company, Ltd. | Method and system to handle dictionaries in a document processing language |
US5499329A (en) * | 1992-04-30 | 1996-03-12 | Ricoh Company, Ltd. | Method and system to handle context of interpretation in a document processing language |
US5493634A (en) * | 1992-06-12 | 1996-02-20 | Xerox Corporation | Apparatus and method for multi-stage/multi-process decomposing |
US5515481A (en) * | 1992-07-08 | 1996-05-07 | Canon Kabushiki Kaisha | Method and apparatus for printing according to a graphic language |
US5611024A (en) * | 1992-08-28 | 1997-03-11 | Compaq Computer Corporation | Data compression of bit map images |
US5287128A (en) * | 1992-08-28 | 1994-02-15 | Moore Business Forms, Inc. | Method to manufacture multiple part imaged documents |
US5384901A (en) * | 1992-10-22 | 1995-01-24 | Xerox Corporation | Method of rendering a color image for an output medium from symbolic image data |
US5734915A (en) * | 1992-11-25 | 1998-03-31 | Eastman Kodak Company | Method and apparatus for composing digital medical imagery |
JP3360905B2 (en) * | 1993-01-04 | 2003-01-07 | ゼロックス・コーポレーション | Printing system |
US5866286A (en) * | 1993-04-16 | 1999-02-02 | Moore Business Forms, Inc. | Color selection by mixing primary toners |
US5745910A (en) * | 1993-05-10 | 1998-04-28 | Apple Computer, Inc. | Frame structure which provides an interface between parts of a compound document |
US5632009A (en) * | 1993-09-17 | 1997-05-20 | Xerox Corporation | Method and system for producing a table image showing indirect data representations |
JPH07117284A (en) * | 1993-10-26 | 1995-05-09 | Canon Inc | Image processor and method thereof |
US5592683A (en) * | 1994-03-18 | 1997-01-07 | Ibm Corporation | System for selectively processing nested print commands and buffered post-print commands thereafter and resending selected portion of data stream upon error detection |
US5495565A (en) * | 1994-06-21 | 1996-02-27 | Wang Laboratories, Inc. | Integrated form document editor with form descriptor table, background bitmap, graphics editor and text editor, composite image generator and intelligent autofill |
US5896462A (en) * | 1994-10-04 | 1999-04-20 | Stern; Yonatan | Method for storing and retrieving images in/from a database |
US5594860A (en) * | 1995-01-27 | 1997-01-14 | Varis Corporation | Method for banding and rasterizing an image in a multiprocessor printing system |
US5729674A (en) * | 1995-04-07 | 1998-03-17 | Computer Humor Systems, Inc. | Method and apparatus for producing personalized graphics and personalized text printed materials |
US5706365A (en) * | 1995-04-10 | 1998-01-06 | Rebus Technology, Inc. | System and method for portable document indexing using n-gram word decomposition |
US5600768A (en) * | 1995-06-06 | 1997-02-04 | Apple Computer, Inc. | Image generation with dynamically consolidated list of image data |
US6332149B1 (en) * | 1995-06-07 | 2001-12-18 | R. R. Donnelley & Sons | Imposition process and apparatus for variable imaging system |
US5895455A (en) * | 1995-08-11 | 1999-04-20 | Wachovia Corporation | Document image display system and method |
US5727220A (en) * | 1995-11-29 | 1998-03-10 | International Business Machines Corporation | Method and system for caching and referencing cached document pages utilizing a presentation data stream |
US6684188B1 (en) * | 1996-02-02 | 2004-01-27 | Geoffrey C Mitchell | Method for production of medical records and other technical documents |
US5621020A (en) * | 1996-06-19 | 1997-04-15 | Moore Business Forms, Inc. | Release composition for printable linerless labels |
US6027195A (en) * | 1996-11-12 | 2000-02-22 | Varis Corporation | System and method for synchronizing the piezoelectric clock sources of a plurality of ink jet printheads |
US6018774A (en) * | 1997-07-03 | 2000-01-25 | Yobaby Productions, Llc | Method and system for creating messages including image information |
US6209010B1 (en) * | 1997-07-18 | 2001-03-27 | Varis Corporation | Computer implemented method for wrapping data to an arbitrary path defined by a page description language |
US6487568B1 (en) * | 1997-07-18 | 2002-11-26 | Tesseron, Ltd. | Method and system for flowing data to an arbitrary path defined by a page description language |
US6707572B1 (en) * | 1997-09-12 | 2004-03-16 | Tesseron, Ltd. | Filtering method to reduce pixel density |
GB9903074D0 (en) * | 1999-02-12 | 1999-03-31 | Silver Fox Ltd | Computer system for producing series of sequential images for labelling |
-
1999
- 1999-04-14 US US09/291,121 patent/US6243172B1/en not_active Expired - Lifetime
-
2000
- 2000-04-11 AU AU44546/00A patent/AU4454600A/en not_active Abandoned
- 2000-04-11 WO PCT/US2000/009646 patent/WO2000062178A1/en active Application Filing
-
2001
- 2001-06-05 US US09/874,895 patent/US20020149792A1/en not_active Abandoned
-
2005
- 2005-09-14 US US11/226,049 patent/US7532355B2/en not_active Expired - Fee Related
Patent Citations (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4944614A (en) * | 1983-07-18 | 1990-07-31 | Kanzaki Paper Mfg. | Form overlay type printing apparatus |
US5222236A (en) * | 1988-04-29 | 1993-06-22 | Overdrive Systems, Inc. | Multiple integrated document assembly data processing system |
US5157765A (en) * | 1989-11-15 | 1992-10-20 | International Business Machines Corporation | Method and apparatus for pipelined parallel rasterization |
US5506697A (en) * | 1990-01-05 | 1996-04-09 | Symbol Technologies, Inc. | Apparatus for processing human-readable and machine-readable documents |
US5459826A (en) * | 1990-05-25 | 1995-10-17 | Archibald; Delbert M. | System and method for preparing text and pictorial materials for printing using predetermined coding and merging regimen |
US5103490A (en) * | 1990-06-13 | 1992-04-07 | National Computer Systems, Inc. | Method and apparatus for storing and merging multiple optically scanned images |
US5134669A (en) * | 1990-06-13 | 1992-07-28 | National Computer Systems | Image processing system for documentary data |
US5202206A (en) * | 1991-10-04 | 1993-04-13 | Xerox Corporation | Process for simultaneous printing of fixed data and variable data |
US5483624A (en) * | 1992-03-27 | 1996-01-09 | Monarch Marking Systems, Inc. | Programmable hand held labeler |
US6016380A (en) * | 1992-09-24 | 2000-01-18 | Avid Technology, Inc. | Template-based edit decision list management system |
US5611035A (en) * | 1992-10-16 | 1997-03-11 | International Business Machines Corporation | Relational data base system for conveniently constructing graphical images |
US5291243A (en) * | 1993-02-05 | 1994-03-01 | Xerox Corporation | System for electronically printing plural-color tamper-resistant documents |
US5500928A (en) * | 1993-03-01 | 1996-03-19 | Xionics Document Technologies, Inc. | Digital printing system and process using adaptive compression |
US5544287A (en) * | 1993-06-03 | 1996-08-06 | Monarch Marking Systems, Inc. | On-line barcode printer system with multi-level user printer commands |
US5459819A (en) * | 1993-09-24 | 1995-10-17 | Eastman Kodak Company | System for custom imprinting a variety of articles with images obtained from a variety of different sources |
US5455599A (en) * | 1993-11-02 | 1995-10-03 | Taligent Inc. | Object-oriented graphic system |
US6064397A (en) * | 1994-09-13 | 2000-05-16 | Agfa Gevaert N.V. | Method for creating multiple documents having identical background regions and page specific image regions |
US5729665A (en) * | 1995-01-18 | 1998-03-17 | Varis Corporation | Method of utilizing variable data fields with a page description language |
US5937153A (en) * | 1995-01-18 | 1999-08-10 | Varis Corporation | Method of utilizing variable data fields with a page description language |
US6243172B1 (en) * | 1995-01-18 | 2001-06-05 | Varis Corporation | Method and system for merging variable text and images into bitmaps defined by a page description language |
US6381028B1 (en) * | 1995-01-18 | 2002-04-30 | Tesseron Ltd. | Method of utilizing variable data fields with a page description language |
US6771387B2 (en) * | 1995-01-18 | 2004-08-03 | Tesseron, Ltd. | Method of utilizing variable data fields with a page description language |
US5796411A (en) * | 1995-07-10 | 1998-08-18 | Moore Business Forms, Inc. | High resolution real time raster image processing system and method |
US5740338A (en) * | 1995-11-13 | 1998-04-14 | Varis Corporation | Method for merging variable image data into a template image |
US5852673A (en) * | 1996-03-27 | 1998-12-22 | Chroma Graphics, Inc. | Method for general image manipulation and composition |
US5926185A (en) * | 1996-05-03 | 1999-07-20 | Barco Graphics N.V. | Method for processing a set of page description language commands to reduce complexity |
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080018935A1 (en) * | 1995-01-18 | 2008-01-24 | Gauthier Forrest P | Method and system for merging variable text and images into bitmaps defined by a page description language |
US20020036788A1 (en) * | 2000-09-12 | 2002-03-28 | Yasuhiro Hino | Image processing apparatus, server apparatus, image processing method and memory medium |
US7386790B2 (en) * | 2000-09-12 | 2008-06-10 | Canon Kabushiki Kaisha | Image processing apparatus, server apparatus, image processing method and memory medium |
US20020186396A1 (en) * | 2001-06-07 | 2002-12-12 | Fuji Photo Film Co., Ltd. | Image processing apparatus, image processing system and image processing program storage medium |
US7672010B2 (en) * | 2002-11-13 | 2010-03-02 | Oce Printing Systems Gmbh | Method and system to generate document templates with resource administration |
US20040130751A1 (en) * | 2002-11-13 | 2004-07-08 | Klaus Hirtenreiter | Method and system to generate document templates with resource administration |
US20060106662A1 (en) * | 2004-11-12 | 2006-05-18 | Hewlett-Packard Development Company, L.P. | Rendering variable data at a point-of-purchase |
US20060156232A1 (en) * | 2004-12-07 | 2006-07-13 | Fabio Giannetti | Method and apparatus for preparing variable-data documents for publishing |
US20060184876A1 (en) * | 2005-02-14 | 2006-08-17 | Canon Kabushiki Kaisha | Information processing apparatus, control method therefor, and program |
US7853872B2 (en) * | 2005-02-14 | 2010-12-14 | Canon Kabushiki Kaisha | Laying out field regions in a page for insertion of data |
US8578269B2 (en) * | 2005-02-28 | 2013-11-05 | Canon Kabushiki Kaisha | Information processing apparatus for performing a layout processing of sub-templates, information processing method and computer-readable medium |
US20120036427A1 (en) * | 2005-02-28 | 2012-02-09 | Canon Kabushiki Kaisha | Document processing apparatus, document processing method and computer program |
US20080320385A1 (en) * | 2006-09-29 | 2008-12-25 | Colorquick, L.L.C. | Graphical Object Insertion During Preparation of Production Data for a Print Job Using a Still Image Proxy of a Page Description Language Image File |
US20080155394A1 (en) * | 2006-10-31 | 2008-06-26 | Hewlett-Packard Development Company, L. P. | Variable data printing |
EP1975772A3 (en) * | 2007-03-28 | 2009-01-21 | Rr Donnelley | Systems and methods for managing print jobs |
US8289538B2 (en) | 2007-03-28 | 2012-10-16 | Moore Wallace North America, Inc. | Systems and methods for managing print jobs |
US20080239366A1 (en) * | 2007-03-28 | 2008-10-02 | Cyman Theodore F | Systems and methods for managing print jobs |
US8184304B2 (en) | 2007-11-19 | 2012-05-22 | Moore Wallace North America, Inc. | System and method of operating a raster image processor |
US20090153905A1 (en) * | 2007-12-18 | 2009-06-18 | Cyman Jr Theodore F | Systems and methods for processing of variable documents |
US8564808B2 (en) | 2007-12-18 | 2013-10-22 | R. R. Donnelley & Sons Company | Systems and methods for processing of variable documents |
US8115956B2 (en) * | 2008-05-23 | 2012-02-14 | Xerox Corporation | Enhancements to VI record job ticketing and processing |
US20090290187A1 (en) * | 2008-05-23 | 2009-11-26 | Xerox Corporation | Enhancements to vi record job ticketing and processing |
US20100110467A1 (en) * | 2008-11-06 | 2010-05-06 | Coniglio Paul A | System and Method of Rasterizing PDF Files using Multiple Processors |
EP2808830A1 (en) * | 2013-05-24 | 2014-12-03 | Seiko Epson Corporation | Printing apparatus, printing control system and control method of the printing apparatus |
CN104175727A (en) * | 2013-05-24 | 2014-12-03 | 精工爱普生株式会社 | Printing apparatus, printing control system and control method of the printing apparatus |
US9365035B2 (en) | 2013-05-24 | 2016-06-14 | Seiko Epson Corporation | Printing apparatus, printing control system and control method of the printing apparatus |
US9751330B2 (en) | 2013-05-24 | 2017-09-05 | Seiko Epson Corporation | Printing apparatus, printing control system and control method of the printing apparatus |
US9489155B2 (en) * | 2014-04-30 | 2016-11-08 | Riso Kagaku Corporation | Image processing device |
US9817620B2 (en) | 2014-12-19 | 2017-11-14 | Canon Kabushiki Kaisha | Predictive object-sequence caching from prior page content |
US20240005083A1 (en) * | 2021-04-19 | 2024-01-04 | Fujian Foxit Software Development Joint Stock Co., Ltd. | Method and system for merging pdf files in a large batch |
Also Published As
Publication number | Publication date |
---|---|
WO2000062178A1 (en) | 2000-10-19 |
US6243172B1 (en) | 2001-06-05 |
AU4454600A (en) | 2000-11-14 |
US20080018935A1 (en) | 2008-01-24 |
US7532355B2 (en) | 2009-05-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6243172B1 (en) | Method and system for merging variable text and images into bitmaps defined by a page description language | |
US20050286065A1 (en) | Method and system for flowing data to an arbitrary path defined by a page description language | |
US20150082154A1 (en) | Method and system for dynamic flowing data to an arbitrary path defined by a page description language | |
US7456990B2 (en) | Method of utilizing variable data fields with a page description language | |
US6209010B1 (en) | Computer implemented method for wrapping data to an arbitrary path defined by a page description language | |
US5600768A (en) | Image generation with dynamically consolidated list of image data | |
US7302438B1 (en) | Method and system for flowing data to an arbitrary path defined by a page description language | |
JP2817687B2 (en) | Image forming device | |
EP0440359B1 (en) | Output apparatus | |
JP3775130B2 (en) | Document processing apparatus and method | |
JP4325339B2 (en) | Printing system, host computer and printer driver | |
JP2580965B2 (en) | Printer device | |
WO2000028435A2 (en) | Method and system for dynamic flowing data to an arbitrary path defined by a page description language | |
AU2004216608B2 (en) | Method for generating a display list | |
JPH05281946A (en) | Method and device for character output | |
JPH0499666A (en) | Plotting system for page printer | |
JPH11338453A (en) | Character pattern output device, method and storage medium | |
JPH0999595A (en) | Character output system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: EXPRESSLY ABANDONED -- DURING PUBLICATION PROCESS |