JP2010004531A - Multifunctional peripheral print container modification - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To append element files to a print container in a multifunctional peripheral (MFP). <P>SOLUTION: A multifunctional peripheral (MFP) 200 includes: a source interface 203 for inputting a file; a container module 206 for creating a print container with the inputted file as an element file; and functional modules 212-220 for generating and supplying another file while using a function that the MFP 200 has, inside the MFP 200. The container module 206 inputs the other file (first element file) generated by the functional modules, modifies and outputs the print container so as to include the inputted first element file and an element file (second element file) in the print container as separate entities. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a multifunction peripheral (MFP) and a method for changing a print container, and more particularly, an MFP capable of changing a print container that stores entities as separate elements in the print container, and a method for changing the same. About. Generally, such a change can be realized by incorporating a program for making such a change into the software of the electronic document incorporated in the MFP.

  Some conventional methods integrate multiple print containers into a single print container. In an application such as SharpDesk®, the user can print the document and save the resulting command as a print container (ie, SharpDisk® document). Furthermore, in Sharp Desk®, the user can see all such print containers. SharpDesk® has a useful feature that integrates a print container into a new print container. This feature allows the user to consolidate multiple related print containers into a single print container that can be printed, sent as an email, or used in various ways in document management functions.

  More generally, each printing operation requires a single application to print a single document that creates a single print container. Normally, in the printing operation, the print container is flowed to the spooler or directly to the printer, and the user cannot use the print container. However, most OSs have a “Print to File” function that saves the print container. For the sake of clarity, some terms derived from XML Paper Specification (XPS) are listed. For example, the operation of printing a single document in an application creates a print container with a single fixed document, which includes a print command that renders a page of the document. Fixed documents include fixed pages or print commands that render each page. Thus, since a print container contains only print commands associated with a single fixed document, the print container is described as a single print document. The problem with merged print containers is that the distinct fixed documents that were used to create the merged print container are lost.

  A further problem is merging print settings. The print setting affects the execution method of the print command, for example, whether it is horizontal or vertical, 1UP or 2UP. Conventionally (for example, in GDI printing), print settings are applied at the beginning of a printed document, possibly as a specific command between pages (reset DC). In this method, in order to create a merged print container by adding a print document, it is necessary to insert a reset DC before adding a new page.

  Due to application merging, most print settings are lost except for essential ones such as landscape or portrait. Therefore, merging of multiple print containers into one print container is usually consistent with the print document format built into the OS, and this print container includes fixed pages that do not have the characteristics of the original print container. The print settings are a series of reset DCs, which are not related to the original print container.

  Another problem with conventional printing is that electronic documents often look different when viewed on a monitor screen than when printed. In addition, many of the documents depend on locally installed software, fonts and other resources. When a document is viewed on another computer, the form of the document, such as page layout, image color, and font style, can change, so the document looks different. Therefore, the appearance of a document depends greatly on where and how the document is viewed.

  The appearance of the printed document may vary depending on the printer used. Unfortunately, there is no guarantee that users using different printers on different devices will see the document printed on the paper and the document viewed on the monitor screen look exactly the same.

  The above problems are dealt with in a document technology called XML Paper Specification (XPS). The specification is designed to provide users with a consistent document appearance regardless of where or how they view the document, and also supports a new document structure for distribution and archiving. This new document structure can include documents created by different applications, all collected in a single XPS file called a “container”. Currently, there is a problem that there is no simple method for integrating such a set of documents into a single XPS container (file).

  The included documents exist in various application formats. When the user wants to maintain an XPS container as an archiveable entity, the document must be converted into an XPS (XML) document format. is there.

  Currently, it is possible to manually build an XPS container that contains a mixture of documents from an application. However, this operation is complicated and easy to make mistakes. Also, to do this manually, it is difficult to include print tickets for the entire container (job level), for a specific document (document level), and in a specific part of a specific document. Also, it is unclear whether Microsoft® supports adding documents from non-Microsoft applications, but XPS supports such a mixture of documents.

  Finally, whether such capabilities include accessing specific files in the XPS container to add print ticket options without the application that was originally used to create the document. Is not certain.

  XPS documents use a fixed page layout to maintain a consistent appearance of the document regardless of environmental changes. An XPS document is a document in a certain format described in a language based on XML. This means that the document layout is constant and the document is visible as it is when printed on paper. As a result, the XPS viewer and the XPS print path can provide the document to the user in the same way, regardless of whether they are looking on the window or paper. Custom resources and other application-specific metadata can also be included in the XPS document, and the application can create and use XPS document packages. Unlike other file formats, XPS container files can be stored and archived without compromising all content and design details. The content of the XPS document package is described in a data format based on plain text and XML, unlike the binary format of proprietary.

  To replace the EMF (Enhanced Metafile) format, which is the print spooler format previously used in the GDI print path, the XPS document format is the same as the spooler format used in the XPS print path. This functions as a page description language (PDL) for the printer. This eliminates the need for intermediate conversion into a printer-specific language in a printer that supports XPS, improving the reliability and accuracy of print output. The document format consists of structured XML markup that represents the rules for delivering, archiving, rendering, processing, and printing the document, as well as defining the document layout and the visual appearance of each page. In particular, the markup language for XPS is a subset of XAML, and it is possible to incorporate vector graphic elements into a document using XAML for marking up the basic elements of WPF. The elements used here are described by paths and other geometric basic elements.

  The XPS document package is a compressed ZIP archive that allows the resulting file to regain some of the space efficiency lost through the use of XML-based languages. The XPS document package conforms to OPC (Open Packaging Conven- tions).

  XPS documents are stored in files called packages, which consist of a set of document components known as parts. The package has a physical and logical configuration. The physical structure is composed of document parts and folders in the package, and the logical structure is a hierarchical structure described by the document parts. XML Paper Specification applies specific configuration and naming conventions to the logical layer of XPS documents.

  The parts of an XPS document are configured in a logical layer with a FixedDocumentSequence part on top. A package of XPS documents can contain more than one document, and a series of these documents is described by a FixedDocumentSequence part. The FixedDocumentSequence part refers to the FixedDocument part that sequentially refers to the pages of each document in the package.

  Each FixedDocument part refers to the page of the document as a FixedPage part. Each FixedPage part includes text markup and document page layout, and references images, fonts, and other custom resources used on the page. Resources such as images and fonts are stored in the package, but are stored outside the FixedPage part and can be shared with other pages. This is particularly useful for font resources, but also for any image resource used on more than one page, such as a watermark or letterhead logo.

  FIG. 1 is a diagram showing a logical hierarchical structure (prior art) of an XPS document. This example shows the contents of a package containing two separate documents, each with two pages. In the package of this example, FixedDocument_1 includes a slide, and FixedDocument_2 indicates background information.

  Japanese Patent Application Laid-Open No. 2004-228561 generates print data based on first print job data sent from a host device, stores the print data in a predetermined storage device, and sends data for operating the first job sent from the host device. According to the second print job data, the print data is integrated and printing is disclosed. In this way, a plurality of jobs stored on the printer side can be operated from the host device side so that the plurality of jobs can be handled as one new job.

  In Patent Document 2, in an information processing method in which a plurality of data having different formats are integrated and processed, the plurality of data is registered in the integrated application, and edited on the integrated application using the application corresponding to the registered data. It is disclosed that the data registered in the integrated application is updated to the edited data.

JP 2001-125757 A JP 2001-337943 A

  As used herein, an MFP is a device that can perform functions such as printing, copying, scanning, faxing, email, display, storage, and networked communication. In general, an MFP performs two or more functions. Conventionally, MFP electronic documents and / or images are stored and / or managed by a document management system (DMS). DMS is a type of computer system that can store and retrieve electronic documents and / or images. Documents and images stored in the DMS are maintained in a wide variety of formats or in multiple graphic locations. The DMS is configured to be able to control and store changes to the document. Furthermore, the DMS is configured to measure the amount of document usage stored and / or retrieved. In general, a DMS is a large-scale storage system based on a server configured to centrally store and share information. Thus, in addition to image forming devices, DMS generally requires separate hardware and / or software for managing electronic documents and images. Thus, conventional DMS is not a convenient solution for personal management of electronic documents and images.

  It would be advantageous if the MFP had the ability to change the print container so that the print container could hold multiple files separated as separate entities.

  However, the technologies described in Patent Documents 1 and 2 can only integrate different files as one collective file, and do not have such ability.

  The present invention has been made in view of the above situation, and an object of the present invention is to provide an element in a print container so that the print container holds a plurality of element files separated as separate entities in the MFP. It is an object of the present invention to provide a system and method capable of making a change to attach a file.

  In order to solve the above-described problems, a first technical means of the present invention includes a container module for creating a source interface for inputting a file and a print container having the file input by the source interface as an element file in a multi-function peripheral. And a function module that generates and supplies another file with the function of the multifunction device, and the container module inputs the first element file that is the other file supplied by the function module. The print container is changed and output so that the input first element file and the second element file which is an element file in the print container are included as separate entities. .

  According to a second technical means, in the first technical means, the source interface inputs an existing print container, and the container module is the first element file and an element file in the existing print container. It is characterized by having a module for changing and outputting the existing print container so as to include a two-element file as a separate entity.

  According to a third technical means, in the first technical means, the first element file and the second element file are a print container, a fixed document which is a document including a print command for rendering the document, and an application specific document. , A page description language (PDL) document, an extensible markup language (XML) Paper Specification (XPS) fixed document, a scanned document, a facsimile document, and a combination of the above elements. It is characterized by that.

  According to a fourth technical means, in the first technical means, the container module adds a document, adds a page to an existing document, deletes a document, and deletes a selected page of the documents. Changing the name of the document, changing the image format of at least part of the document, changing the name of the print container, changing the order of the pages in the document, dividing the document into a number of documents Selected from the group consisting of: changing the format of the document, saving the document in another format, performing image enhancement on the document, performing optical character recognition on the document Execution The Rukoto is obtained by and changing the print container.

  According to a fifth technical means, in the second technical means, the container module executes access to the print container by extracting a document or extracting a selected page of the document. It is what.

  According to a sixth technical means, in the first technical means, the functional module includes any one of a printer module, a scanner module, a photocopy module, a facsimile module, an e-mail module, and a memory module. The function module is supplied with the print container to be changed, and the first element file is added to the print container.

  The seventh technical means further includes a scan engine that reads the document described in the original in the first technical means, the scan engine scans the document described in the original, and the scanned document Is supplied to the source interface as the second element file.

  An eighth technical means includes a print engine that captures a print job and supplies an intermediate file that is completely rendered and ready for printing to the source interface as the second element file in the first technical means. Furthermore, it is characterized by having.

  A ninth technical means is the first technical means, wherein the container module includes a job in the print container, a fixed document in the job, and a page in the fixed document including a print command for rendering a page. The first element file is stored as an entity separate from the second element file in the print container by creating a hierarchical structure of the elements of the print container, which is a fixed page. Is.

  A tenth technical means is the ninth technical means, wherein the container module changes the print container by changing a hierarchy of the print container elements.

  In an eleventh technical means according to the first technical means, the container module creates a print container resource for repeatedly using the same element without repeatedly describing the same element in the print container. A pointer for associating the resource with the first element file is created.

  A twelfth technical means is the first technical means, wherein the source interface supplies a PT disposition indicating that the first element file has a print ticket (PT) which is information indicating print settings, The container module is characterized in that the PT disposition of the first element file is selectively stored in the print container.

  A thirteenth technical means is the twelfth technical means, wherein the container module is configured to render a job PT in the print container, a fixed document PT in the job, and a print in the fixed document for rendering a page. The PT disposition of the first element file is selectively stored in the print container by creating a PT hierarchical structure composed of fixed page PTs, which are pages including commands. is there.

  A fourteenth technical means is the twelfth technical means, wherein the container module is configured to render a PT of a job in the print container, a PT of a fixed document in the job, and a page in the fixed document for rendering a page. The PT disposition is selectively stored by changing a PT hierarchical structure including a fixed page PT which is a page including a command.

  A fifteenth technical means is a method for changing a print container executed in a multi-function peripheral, wherein a source interface inputs a file and a container module inputs the file input in the input step as an element file. A creation step for creating a print container, a supply step for the function module to generate and supply another file with the function of the multifunction device, and the another file supplied by the function module to the container module. The first element file is input, and the print container is changed and output so that the input first element file and the second element file that is the element file in the print container are included as separate entities. Change step and storage means change in the change step Is obtained by comprising: the step of storing the print container in a memory medium which, a.

  A sixteenth technical means is the fifteenth technical means, wherein the first element file and the second element file are a print container, a fixed document which is a document including a print command for rendering the document, and an application specific document. , A page description language (PDL) document, an extensible markup language (XML) Paper Specification (XPS) fixed document, a scanned document, a facsimile document, and a combination of the above elements. It is characterized by that.

  A seventeenth technical means is the fifteenth technical means, wherein the changing step includes adding a document, adding a page to an existing document, deleting a document, and deleting a selected page of the document. Changing the name of the document, changing the image format of at least part of the document, changing the name of the print container, changing the order of the pages in the document, dividing the document into a number of documents Selected from the group consisting of: changing the format of the document, saving the document in another format, performing image enhancement on the document, performing optical character recognition on the document Execute By, is obtained by means changes the print container.

  An eighteenth technical means is the fifteenth technical means, wherein the changing step includes a job in the print container, a fixed document in the job, and a page in the fixed document including a print command for rendering the page. The first element file is stored as an entity separate from the second element file in the print container by creating a hierarchical structure of the elements of the print container, which is a fixed page. Is.

  According to a nineteenth technical means, in the fifteenth technical means, the container module creates a print container resource for repeatedly using the element without repeatedly describing the same element in the print container. A creation step for creating a pointer for associating a resource with the first element file is further included, and the changing step includes a step of adding the print container resource created by the creation step to the print container. It is characterized by that.

  According to the present invention, it is possible to make a modification of attaching an element file to a print container so that the print container holds a plurality of element files separated as separate entities in the MFP. In addition, by assigning different print setting information to each entity, different print settings can be made for a plurality of element files (document data, etc.) in one print container. Print settings can be made flexibly.

It is a figure which shows the logical hierarchical structure (prior art) of an XPS document. 1 is a schematic block diagram illustrating an example of a system for attaching an element file to a print container in an MFP. It is a table explaining the comparative example of the document distribute | arranged to a GDI print container, and the print container of this invention. 10 is a table for explaining a comparative example of a document arranged in a GDI print container and a print container of the present invention. FIG. 3 is a diagram illustrating an example of a hierarchical structure of print container elements. 6 is a flowchart for explaining a method for attaching an element file to a print container in an MFP device.

  A method is disclosed that meets the need for a convenient print container that can be used to store and manage scanned documents and images in an MFP. Instead of relying on Extensible Markup Language (XML) Paper Specification (XPS), print files or other document management formats can be used with the print container. The print container can store many documents as a series of pages. By embedding document information, such as the document name or page number, the print container can support many different documents, just like XPS. Thumbnails, digital signatures, and rights management information can also be embedded. This MFP can create a print container or change the print container existing at that time.

  Accordingly, a method for attaching an element file to a print container in an MFP is provided. The method receives a first element file and a print container that includes a second element file. Examples of element files include a print container, a fixed document that is a document containing print commands for rendering the document, an application specific document, a page description language (PDL) document, an XPS fixed document, and a facsimile document. , Scanned documents. The method modifies the print container to include a first element file and a second element file stored as separate entities and stores the modified print container in a tangible memory medium. Here, the entity refers to a group of data handled as a unit in the print container, and some kind of indicator (for example, a display icon to be displayed for causing the user to select each element or a display icon for designating the display icon). (Information) refers to a set of data that is the entity.

Changing the print container includes adding a document, adding a page to an existing document, deleting a document, deleting a selected page of a document, renaming a document, Changing some image formats, changing the name of a personal document container (synonymous with "print container", and so on), changing the order of pages in a document, dividing a document into multiple documents May include actions such as changing the format of the document, saving in another format of the document, performing image enhancement on the document, performing optical character recognition on the document
Further details of the above method are described below.

  Various embodiments will be described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it will be apparent that embodiments may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing these embodiments.

  As used herein, the terms “processor”, “processing device”, “component”, “module”, “system” and the like refer to computer-related entities, hardware, firmware, a combination of hardware and firmware, software, execution It is intended to mention any of the software inside. For example, a component may be any one or more of a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer, but is not limited thereto. . By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and / or thread of execution, and the components can be localized on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures. A component is one or more data packets (eg, data from one component that interacts with any one or more other components in a local system, in a distributed system, in a network such as the Internet with other systems). Communicating by local and / or remote processes in response to signals having

  Various embodiments are given by a system comprising many components, modules, etc. It will be appreciated and understood that various systems may include additional components, modules, and / or the like, and / or may not include all of the components, modules, and the like described in connection with the drawings. A combination of these approaches can also be used.

  The various logic blocks, modules and circuits described above can be any general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, individually It can be implemented and performed using gate or transistor logic, discrete hardware components, or combinations thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors coupled to a DSP core, or other such configuration. Is possible.

  The methods and algorithms described in connection with the embodiments described herein may be implemented directly in hardware, in software modules executed by a processor, or in a combination of both. The software modules can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. The storage medium is coupled to the processor so that the processor can read and write information from and to the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium can be resident in the ASIC. The ASIC can reside at a node or elsewhere. In the alternative, the processor and the storage medium may reside as discrete components in a node or elsewhere in an access network.

  FIG. 2 is a schematic block diagram showing an example of a system for attaching an element file to a print container in the MFP. A system 202 provided in the MFP 200 includes a source interface 203 connected through a line 204 for inputting a file (referred to as a second element file for convenience). A container module 206 is connected to the source interface 203 on the line 208 so as to capture the second element file. The container module 206 creates a print container having the second element file input from the source interface 203 as an element. The MFP 200 includes functional modules exemplified by the modules 212 to 222. The function module refers to a module that generates and supplies another file (referred to as a first element file for convenience) in the MFP 200 with a function of the MFP 200. For example, at least one of the illustrated examples is provided in the MFP. I just need it. The container module 206 adds this first element file to the created print container. In doing so, the container module 206 modifies the print container to include the second element file and the first element file stored as separate entities. That is, the container module 206 inputs the first element file from the function module, and includes the print container so that the input first element file and the element file (second element file) in the print container are included as separate entities. change. An output on line 210 is provided to supply the modified print container.

  In addition to the change function, the container module 206 can access a pre-existing print container. In particular, an existing print container can be input at the source interface 203 and passed to the container module 206. Then, the container module 206 modifies the existing print container to include the first element file and the element file in the existing print container (corresponding to the second element file described above) as separate entities. You may comprise so that it may have a module to output.

  A print container, as used herein, is an electronic folder with an electronic file that contains sufficient information to print or view content. The print container typically includes individual pages and a set of instructions how to print the pages. In newer formats, the print container can contain multiple collections of pages or documents. The print command can be applied to the entire print container, a single document or individual pages. A print container is different from an electronic document because it does not contain information on how to edit the document. For example, a word document distinguishes text headers and footers from the body, in which case the print container simply contains the text in a different location without differing from the original intent. A print container can efficiently compose repetitive data (such as headers and footers), but its main purpose is to print and view, not editability. Finally, the print container can be searched and indexed, and the print container can contain extra non-print related data, but the main purpose of the print container is related to printing and browsing To do.

  The container module 206 can add a document, add a page to an existing document, delete a document, delete a selected page of a document, rename a document, or at least part of a document Change the image format, change the name of the personal document container, rearrange the order of the pages in the document, split one document into many documents, change the document format, The print container is changed by saving the file in the format of the document, performing image enhancement on the document, or performing optical character recognition (OCR) on the document.

  The first element file and the second element file are (other) print containers, fixed documents, application specific (unique) documents, PDL documents, XPS fixed documents, scanned documents, facsimile documents, combinations of the above elements It can be. For example, a Microsoft Word® financial report can be an example of an application specific document.

  Container module 206 includes one of the following functional modules: printer module 212, scanner module 214, photocopy module 216, fax module 218, email module 220, memory module 222, a combination of these modules, A print container to be changed may be supplied to cause the function module to add the first element file.

  For example, if the print container to be changed is supplied to the printer module 212 or the photocopy module 216, the printer module 212 or the photocopy module 216 includes the first page containing the printed or photocopied page (ie, the result of the print job). The element file is added to the print container and returned to the container module 206. When the print container to be changed is supplied to the scanner module 214, the scanner module 214 adds the first element file containing the scanned page to the print container and returns it to the container module 206. When the print container to be changed is supplied to the fax module 218, the fax module 218 adds the first element file containing the received incoming fax page to the print container and returns it to the container module 206. When the print container to be changed is supplied to the email module 220, the email module 220 sends a first element file containing one or more sent or received emails or their attachments to the print container. Add and return to container module 206. When the print container to be changed is supplied to the memory module 222, the memory module 222 adds the first element file in the memory to the print container and returns it to the container module 206. The memory module 222 can also store the print container supplied from the container module 206 as it is or after adding the first element file. Therefore, the memory module 222 can also store a print container to which the first element file has been added by the other modules 212 to 220, for example.

  Thus, by adding each first element file to the print container in each module, the first element files can be stored in the print container in a state of being separated. Although the print container can perform printing, each page can be added as a separate section according to the print instruction in each module as described above, so the user can print out which module is based on the print instruction in which module. You can check it from the print container later.

  According to one aspect, the container module 206 (or a functional module instructed by the container module 206; also in each of the following aspects) includes a job in the print container, a fixed document in the job, and a fixed document in the fixed document. The first element file is stored as an entity separate from the second element file in the print container by creating a hierarchical structure of the elements of the print container including any one or a plurality of fixed pages. Next, the container module 206 can change the print container by changing the hierarchical structure of the elements of the print container. Here, the fixed document is defined as a document including a print command for rendering a document of one page or more. That is, the fixed document includes fixed pages and / or print comments (eg, PDL) for rendering each page. Similarly, the fixed page is a page including a print command for rendering the page. Examples of fixed documents include PDF files, raster images, and XPS fixed documents.

  In another aspect, the functional module provides a PT disposition to the first element file indicating that it has a print ticket (PT), and the container module 206 includes the PT of the first element file in the print container. Save the disposition selectively. The PT is information indicating print settings, and the element file has either a PT or no PT. More specifically, the container module 206 is a PT composed of one or more of a PT of a job in a personal document container, a PT of a fixed document in a job, and a PT of a fixed page in a fixed document. By creating the hierarchical structure, the PT disposition of the first element file can be selectively stored in the personal document container. Next, the container module 206 changes the PT hierarchical structure including any one or more of the PT of the job in the personal document container, the PT of the fixed document in the job, and the PT of the fixed page in the fixed document. Thus, PT disposition can be selectively stored.

  In one aspect, the MFP 200 includes a scan engine 224 that inputs image data from a line 226 that includes means for capturing an image of a document on a physical medium (ie, a document written on a manuscript). The scan engine 224 scans the document on the document, and supplies the scanned document to the source interface 203 as a second element file on the line 204. As a result, the second element file is supplied to the container module 206.

  In another aspect, the MFP 200 includes a print engine driver 228 having an input on line 230 for capturing a print job. Print jobs can be provided by a computer, server, or memory media interface (not shown). The print engine driver 228 supplies a fully rendered printer-ready intermediate file (ie, an intermediate file that is fully rendered and ready for printing) to the source interface 203 on line 204 as a second element file. . For example, a fully rendered printer-ready intermediate file may be halftoned before being supplied. As a result, the second element file is supplied to the container module 206.

  In another aspect, the container module 206 creates a pointer corresponding to the print container resource and the first element file in the print container, and associates the first element file with the print container resource. Here, the print container resource refers to information for repeatedly using the same element without repeatedly describing the same element in the print container. Examples of print container resources include fonts, images, and custom resources (for example, PDF files) that are stored separately. The pointer is information for associating an element in the print container with a printer container resource. For example, the pointer indicates information indicating a storage destination of a font or the like stored separately.

  In one aspect, the MFP 200 includes a front panel, a browser, a user interface, or a graphic user interface (GUI). The GUI can be composed of a display 240 and interface means 242 including a GUI program and operating means that allow a user to interact or respond to the displayed GUI image. The operation unit of the interface unit 242 may be a keyboard, a keypad, a mouse, or a touch screen, for example.

  Thus, the UI can be opened and used to select a specific file. The list of files selected by the user can be combined into a single file called a print container. If the file is not in the desired format, selective conversion is performed to generate a fixed document. A print ticket can be added or changed for the file of the selected element. For example, a job level set of print tickets can be created in a print container container. Also, a print ticket job level set may be created sequentially for each document, or a print ticket page level set may be a selected page within each document.

  The user uses the GUI to sequentially access individual documents and containers, make conventional selections of printing and finishing options, create a fixed document as output, and place the document in a print container. Without closing the print container, the user can continue the process of accessing another document and building a print ticket for that document, and saving the result in the same print container file as the previous document. .

  In one mode of operation, the container module 206 accumulates individual element files one at a time, providing the user with an opportunity to add, modify (change) or delete existing print tickets. The user can store the modified document in the print container and select a new element file, and can continue this operation until all elements are in the container and the container is stored or sent to the printer. .

  The user is then prompted to make a job level selection via the UI. The container module 206 then translates the job level selections into job level print tickets and places these tickets in the correct location within the print container file.

Functional Description The MFP allows a user to scan multiple pages into an existing document or create a new document. The print container can be imported into a USB flash drive, or the print container can be accessed over the network. The MFP can then be used for basic document management tasks such as adding a document, deleting a document, printing a document, sending a document image, and the like. In addition, basic page level tasks such as adding pages, deleting pages, printing pages, and sending images of pages can be performed. In addition, pages can be added to the print container, along with metadata-readable summaries. In one aspect, the MFP uses a modified version of a conventional XPS file as a wrapper for element files.

  The print container of the present invention can store a large number of scanned documents. Each element file in the print container can be treated as an individual page, or the element file can be distinguished as an individual document by using a special tag. The print container can also manage thumbnails, digital signatures, and rights management information by using special tags to support these functions.

  The user can create a new container, modify an existing container, or access an existing print container in the MFP. Users can access containers on a shared network holder, portable USB flash drive or MFP hard drive. For example, on the front panel of the MFP, the user can display that he wanted to create a print container. The user then selects the location of the container and enters or captures the default file name. The user then sets up the document for scanning into the container.

  The user enters or selects a default name for the first document and selects one of the available image formats. Any additional scanning options such as exposure, color mode, resolution or compression are also selected. Scan a page for the first document (1-n). The user interface can change the image format for each page. When the first document is complete, the user can close the container or add another document. When all documents have been scanned, the container is closed and the user completes the process.

  The front panel of the MFP can also be used to change the print container. The user selects an existing print container by location and file name. The user can then add, for example, a new document, add a page to an existing document, delete a document, delete pages 1-n from the document, or extract pages 1-n of an existing document into a new document. Or change type such as changing the document name. The user interface guides the user by making the selected change. When all changes are complete, close the container.

  In order to access a print container using the front panel of the MFP, the user selects an existing print container by location and file name. For example, the user selects an operation such as printing a document (or 1 to n pages of the document) or transmitting an image of the document (or 1 to n pages of the document).

  Many print files contain comment commands that were previously ignored by the MFP. For example, a PCLXL document has a comment identified by “??”. PostScript comments are identified by percent (%) symbols and PDF comments are identified by percent (%) symbols. Such comments are used to include document information in the print container.

  When realizing a print container as an XPS wrapper, each element file can be handled as an XPS fixed document. In another aspect, visible metadata can be used within the print container. Rather than hiding documents, thumbnails, digital signatures, and rights management information in comments, cover pages or multiple pages can be interspersed within jobs added to personal containers. These additional pages contain a human readable description of the metadata. In addition to document name and page number, thumbnails can be rendered for all pages or the first page of each document.

Using the print container GUI associated with the front panel of the MFP, the following two new functions can be used to print a document.
a) There are extra levels of hierarchy in the print container. That is, one job can contain a multi-element file.
b) Print settings can be organized by job, document and page instead of reset DC.

  The user can distinguish which of the original documents the section of the printout belongs by using the print container construction process. Furthermore, the user can easily set print settings at different levels. For example, the user can set the first document up to 2UP while keeping the second document at 1UP. This type of hierarchical manipulation of print settings is more intuitive than inserting a reset DC.

  It is worth noting that there are several conventional applications that allow XPS container merging. However, these merge applications do not maintain individual document or print settings separately.

  3A and 3B are tables for explaining a comparative example of a document arranged in the GDI print container and a document arranged in the print container of the present invention. “MY PEPORT.DOC” and “MY INVOICE.XLS” illustrated in FIG. 3A are both documents supplied to the source interface 203. Each document has print settings for each page. In this example, “MY PEPORT.DOC” includes three separate pages, and the vertical, horizontal, vertical, and print directions are set in order, and “MY INVOICE.XLS” includes two separate pages. In both cases, the printing direction is set to horizontal.

  Two such source documents are divided into pages using a reset DC in order to call page orientation (landscape / portrait) in the GDI print container. In the GDI print container of this example, it is described that the print setting is vertical in the print job of “MY PEPORT.DOC”, the print command for page 1, the reset DC (horizontal), the print command for page 2, the reset DC (Vertical), the print commands for page 3 are described in order. Further, in the GDI print container of this example, in the print job “MY INVOICE.XLS”, it is described that the print setting is horizontal, and the print command for page 1 and the print command for page 2 are described in order.

  On the other hand, in the print container of the present invention, a print ticket can be used for orientation. In the print container of this example, a print command for each page of the first source document is described in the print job of the first source document “MY PEPORT.DOC”, followed by the entire first source document. The print ticket is described as being in the vertical direction, and the print ticket for page 2 is described as being in the horizontal direction. In the print container of this example, the print command for each page of the second source document is described in the print job of the second source document “MY INVOICE.XLS”, and then the second source document. It is described that the print ticket for the entire document is in the horizontal direction.

  A case where two such source documents are merged will be described with reference to FIG. 3B. When two source documents are selected and instructed to be printed by a normal printing process and merged, a merged document is generated. Although the merged document is illustrated as “MERGEDDOC.PRN” in FIG. 3B, the merged document is only a print command, and the user cannot confirm the print contents later.

  In the case of a GDI print container, the second source after the reset DC is described after the print setting and print command for the first source document “MY PEPORT.DOC” shown in FIG. A print setting and a print command for the document “MY INVOICE.XLS” are described. As described above, in the GDI print container, when a new page is added by merging, it is necessary to insert a reset DC before the new page.

  On the other hand, in the print container of the present invention, a print ticket can be used for orientation. Accordingly, the document print command and the print ticket relating to the print setting can be separated. In this example, a print command for the first source document and a print command for the second source document are described in the merged print job of the two documents, followed by a print ticket. The print ticket described here includes the print ticket for the entire first source document (vertical), the print ticket for page 2 of the first source document (horizontal), and the entire second source document. Print tickets (horizontal) are described in order. Thus, in the print container of the present invention, when adding a new page by merging, it is not necessary to insert a reset DC before the new page.

  FIG. 4 is a diagram illustrating an example of a hierarchical structure of print container elements. Documents can be combinations created by different applications. That is, a set of documents is not limited to the same vendor and is not limited to the same application. The user can construct a print container from a combination of existing print containers, fixed documents, and application specific documents. The user can configure the print container at the job level, document level, and page level all at the same time using commonly used (printer driver) software with intuitive extensions.

  The printer driver automates many manual functions, such as launching applications associated with the document being worked on, to facilitate image processing interactions between the application and the printer driver.

  FIG. 5 is a flowchart for explaining a method for attaching an element file to a print container in the MFP device. For simplicity, this method is shown as a sequence of numbered steps, but the numbers do not necessarily indicate the order of the steps. Some of these steps may be skipped, performed in parallel, or performed without maintaining a strict sequence order. The method starts at step 500.

  Step 502 captures a print container whose source interface contains a second element file (or source interface captures a second element file and generates a container module containing it), and a functional module captures the first element file. . Step 504 modifies and outputs the print container so that the container module includes a first element file and a second element file saved as separate entities. In step 506, the storage means stores the changed print container in a tangible memory medium. For example, the memory module 222 in FIG. 2 stores the changed print container in the internal memory.

  In one aspect, capturing the first element file and the print container in step 502 includes first and second element files, a fixed document, and an application specific document that can potentially be a print container. , PDL documents and capturing XPS fixed documents, facsimile documents, scanned documents, and combinations of the above elements. JPEG, TIFF, PNG and HD photos are some of the examples of scanned document formats.

  In another aspect, changing the print container in step 504 can include performing one of the following actions. Ie adding a document, adding a page to an existing document, deleting a document, deleting a selected page of a document, renaming a document, an image format of at least a part of a document Change the name of a personal document container, change the order of pages in a document, split a document into multiple documents, change the format of a document, save a document in another format , Performing image enhancement on the document, or performing OCR on the document.

  In another aspect, storing the first and second element files as separate entities in the print container (step 504) includes: a job in the print container, a fixed document in the job, and a fixed page in the fixed document. Creating a hierarchical structure of the elements of the print container.

  In one variation, step 503 creates a print container resource and a pointer corresponding to the first element file in the print container for associating the first element file with the print container resource. create. Next, changing the print container in step 504 includes adding the print container resource to the print container. The print container resource and the pointer are as described above.

  The system and method for changing the print container for use in the MFP device have been described above. Examples of specific structures and process steps are given to illustrate the present invention. However, the present invention is not limited to these examples. Those skilled in the art will appreciate other variations and embodiments of the present invention.

200 ... MFP, 202 ... system, 203 ... source interface, 204, 208, 210, 226 ... line, 206 ... container module, 212 ... printer module, 214 ... scanner module, 216 ... photocopy module, 218 ... fax module, 220 ... E-mail module, 222 ... Memory module, 224 ... Scan engine, 228 ... Print engine driver, 230 ... Line, 240 ... Display, 242 ... Interface means.

Claims (19)

In the multifunction machine,
A source interface for entering files,
A container module for creating a print container having the file input at the source interface as an element file;
A function module that generates and supplies another file with the functions of the MFP;
Have
The container module inputs a first element file that is the other file supplied by the function module, and separates the input first element file from a second element file that is an element file in the print container. A multi-function machine that changes and outputs the print container so as to be included as an entity.   The source interface inputs an existing print container, and the container module includes the first element file and a second element file that is an element file in the existing print container as separate entities. The multifunction device according to claim 1, further comprising a module that changes an existing print container to output.   The first element file and the second element file are a print container, a fixed document that is a document including a print command for rendering the document, an application specific document, a page description language (PDL) document, and extensible markup. 2. The multi-function peripheral according to claim 1, wherein the multi-function peripheral is a file selected from the group consisting of a language (XML) Paper Specification (XPS) fixed document, a scanned document, a facsimile document, and a combination of the above elements.   The container module can add a document, add a page to an existing document, delete a document, delete a selected page of the document, rename a document, and / or change at least one of the documents. Changing the image format of the part, changing the name of the print container, changing the order of the pages in the document, dividing the document into multiple documents, changing the format of the document, Modify the print container by performing an action selected from the group consisting of: saving in format; performing image enhancement on the document; performing optical character recognition on the document. Multifunction machine according to claim 1, characterized in Rukoto.   The multifunction device according to claim 2, wherein the container module executes access to the print container by extracting a document or extracting a selected page of the document. The function module includes any one of a printer module, a scanner module, a photocopy module, a facsimile module, an email module, and a memory module,
The multifunction device according to claim 1, wherein the container module supplies the print module to be changed to the function module and adds the first element file to the print container.   A scan engine for reading a document described in the manuscript, wherein the scan engine scans the document described in the manuscript and supplies the scanned document to the source interface as the second element file; The multifunction device according to claim 1.   The composite of claim 1, further comprising a print engine that captures a print job and supplies an intermediate file that is fully rendered and ready for printing to the source interface as the second element file. Machine.   The container module is a hierarchical structure of elements of a print container comprising a job in the print container, a fixed document in the job, and a fixed page that is a page including a print command for rendering a page in the fixed document. 2. The multifunction device according to claim 1, wherein the first element file is saved as an entity separate from the second element file in the print container.   The multifunction device according to claim 9, wherein the container module changes the print container by changing a hierarchy of the print container elements.   The container module creates a print container resource for repeatedly using the same element without repeatedly describing the same element in the print container, and sets a pointer for associating the printer container resource with the first element file. The multifunction device according to claim 1, wherein the multifunction device is created. The functional module supplies a PT disposition indicating that the first element file has a print ticket (PT) that is information indicating print settings;
The multi-function peripheral according to claim 1, wherein the container module selectively saves the PT disposition of the first element file in the print container.   The container module includes a PT of a job in the print container, a PT of a fixed document in the job, and a PT of a fixed page that is a page including a print command for rendering a page in the fixed document. 13. The multi-function apparatus according to claim 12, wherein the PT disposition of the first element file is selectively stored in the print container by creating a hierarchical structure.   The container module includes a PT of a job in the print container, a PT of a fixed document in the job, and a PT of a fixed page that is a page including a print command for rendering a page in the fixed document. 13. The multifunction device according to claim 12, wherein the PT disposition is selectively stored by changing a hierarchical structure. A method of changing a print container executed in a multifunction device,
An input step where the source interface inputs a file;
A creation step in which the container module creates a print container having the file input in the input step as an element file;
A supply step in which the function module generates and supplies another file with the function of the multifunction peripheral;
The container module inputs the first element file, which is the other file supplied by the function module, and separates the input first element file from the input second element file, which is an element file in the print container. A change step of changing and outputting the print container so that it is included as an entity of
A storage unit storing the print container changed in the changing step in a memory medium;
A method characterized by comprising:   The first element file and the second element file are a print container, a fixed document that is a document including a print command for rendering the document, an application specific document, a page description language (PDL) document, and extensible markup. 16. The method of claim 15, wherein the file is a file selected from the group consisting of a language (XML) Paper Specification (XPS) fixed document, a scanned document, a facsimile document, and a combination of the above elements.   The modifying step includes adding a document, adding a page to an existing document, deleting a document, deleting a selected page of the document, changing the name of the document, and at least one of the documents. Changing the image format of the part, changing the name of the print container, changing the order of the pages in the document, dividing the document into multiple documents, changing the format of the document, Modifying the print container by performing an operation selected from the group consisting of: saving in format; performing image enhancement on the document; performing optical character recognition on the document. The method of claim 15, wherein.   The change step includes a hierarchical structure of print container elements comprising a job in the print container, a fixed document in the job, and a fixed page in the fixed document that includes a print command for rendering a page. 16. The method of claim 15, wherein the first element file is saved as a separate entity from the second element file in the print container by creating a file. The container module creates a print container resource for repeatedly using the same element without repeatedly describing the same element in the print container, and sets a pointer for associating the printer container resource with the first element file. A creation step for creating,
16. The method according to claim 15, wherein the changing step includes the step of adding the print container resource created by the creating step to the print container.

Images