JP2010113596A - Document processing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve a problem in a prepress application capable of setting a print format for each chapter that, while a finish can be changed by the designation of "change a finish sheet" or "change a finish page" at a chapter break point, a wraparound etc. occurs at this setting, in a two page spread format with a start page designated, an intended format may not be obtained by only the designation at a chapter break point, and in such a case, while a blank page can be inserted to adjust imposition, a change of the number of impositions may require readjustment, thus resulting in poor efficiency. <P>SOLUTION: Whether the first page of a chapter always starts from the right or the left is determined, a blank page is automatically inserted so as not to adversely affect imposition, and a book file is generated. Thereby, a user is not required to insert a blank page, and work efficiency and system productivity are improved while human errors are prevented, thus allowing a high quality document to be created. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a document processing system and method for collecting output data generated by various programs such as a document processing program and an image editing program as one document and providing an editing function for the document.

Different types of data such as characters, tables, and images have different structures for defining the data and editing operations on the data. Therefore, various application programs corresponding to the types of data are provided. The user uses different applications depending on the type of data, such as a character processing program for editing characters, a spreadsheet program for editing tables, and an image editing program for editing images. For this reason, there are applications that can handle data of different applications in an integrated manner. This is called a bookbinding application. In addition to being able to handle the different application data, the bookbinding application is characterized in that it can be set at the time of printing. For example, it is possible to specify case binding with a front cover such as bookbinding or back cover, or to set N-UP printing so that a number of pages of data are embedded in one sheet. In such a function, if a page is added later or a setting different for each page is reflected, the page configuration may be corrupted. In order to avoid this, there is a means of logically providing a chapter structure, setting and determining whether or not a page break is designated for each chapter, and inserting a blank page as necessary.
Japanese Patent Laid-Open No. 2003-091521

  However, logic that inserts page breaks or blank pages for each chapter may not be applicable to special bookbinding. For example, a book where the first page of the chapter must come to the left. There are cases where such a configuration is used for reference books and practice questions.

  Since a book is assumed, it is assumed that the bookbinding setting has a front cover, a back cover, and a double-sided configuration. In the conventional method, there are a pattern for changing pages for chapter separation and a pattern for changing paper for chapter separation.

  FIG. 13 shows a bookbinding preview which is a problem applicable to this embodiment.

  The bookbinding application 104 has a preview unit 1102 for displaying a printed state, and 1102 includes electronic document files 1301 to 1309. The chapter structure by bookbinding application is as follows. Reference numeral 1301 denotes a cover, which is the beginning chapter. One chapter is two originals 1302 and 1303. Chapter 2 is three originals 1304, 1305, and 1306. Chapter 3 is 2 manuscripts 1307 and 1308. The last chapter is one manuscript of 1309, which is the last chapter. Since the structure is given in the bookbinding application 104 in this way, the configuration described in FIG. 13 is hereinafter referred to as a book file in FIG.

  FIG. 14 is a case binding preview which is a problem applicable to the present embodiment.

  The book file shown in FIG. 13 is further given a case binding structure by the bookbinding application 104 as shown in FIG. The case binding is a structure having a cover and an inner cover. The cover sheet is 1401, and the middle sheets are 1402, 1403, 1404, and 1405. Reference numeral 1401 denotes data output at A3. The left half of A3 paper has original data written “back cover”, and the right half has original data written “cover”. By folding it in the middle so that it binds to the left and sandwiching the inner paper inside, you can make a paper with a book cover and back cover. Reference numeral 1402 denotes the first middle sheet, which is document data output at A4. There are two document data, and both are drawn as “1”. The two original data are imposed on the front and back of A4 paper. 1403 has the same configuration as 1402, but both are drawn as “2”. 1404 has the same configuration as 1403, but data “2” is imposed on the front surface and data “3” is imposed on the back surface. 1405 has the same configuration as 1404, but “3” is imposed on the front surface and blank data is imposed on the back surface. With the above configuration, in the book file of FIG. 14, when the cover is opened, “1” “1” “2” “2” “2” “3” “3” “blank” is closed and “back cover” is displayed. Bookbinding to be printed.

  FIG. 15 is a blank paper insertion pattern for case binding preview, which is a problem applicable to this embodiment.

  Assume that the book file in FIG. 14 has a layout in which the first page of the chapter that is the subject must come to the left. In the case of FIG. 14, the front cover is opened and “front” 1402 comes to the right. In order to avoid this, the book file shown in FIG. 15 is obtained by inserting a blank page on the first page. The cover is the same as in FIG. Reference numeral 1501 denotes a first middle sheet, which is document data output at A4. There are two document data, and a blank sheet added to the front 1501f is imprinted with “1” on the back 1501b. Then, the subsequent pages are imposed so as to be shifted by one page from FIG. “1” is imposed on 1501 f which is the front surface of 1502, and “2” is imposed on 1502 b which is the back surface. “2” is imposed on 1503 f which is the front surface of 1503, and “2” is imposed on 1503 b which is the back surface. “3” is imposed on 1504 f which is the front surface of 1504, and “3” is imposed on 1504 b which is the back surface. With the above configuration, in the book file of FIG. 15, when the cover is opened, “blank”, “1”, “1”, “2”, “2”, “2”, “3”, and “3” are closed and “back cover” is displayed. Bookbinding to be printed.

  This is not a layout that requires the first page of the chapter in question to be on the left side. The first page 1501b of Chapter 1 and the first page 1502b of Chapter 2 are on the left side of the spread. However, 1504f, the first page of Chapter 3, comes to the right.

  In the conventional method, there are a pattern for changing pages for chapter breaks and a pattern for changing paper for chapter breaks.

  Even if the pattern for changing pages is applied to the chapter breaks in FIG. 15, nothing changes. This is because FIG. 14 originally has pages changed at chapter breaks. Next, apply a pattern to change the paper at the chapter break.

  FIG. 16 shows a paper switching pattern for case binding preview, which is a problem applicable to this embodiment.

  The book file in FIG. 16 is the book file in which the paper switching setting is performed in FIG. The cover is the same as in FIG. Reference numeral 1601 denotes the first middle sheet, which is document data output at A4. There are two document data, and a blank sheet added to the front surface 1601f is imprinted with “1” on the back surface 1601b. The subsequent pages are shifted as shown in FIG. 15 so as to be pushed by a blank sheet of 1601f. “1” is imposed on the front surface 1602 f of 1602, and “white paper” is imposed on the back surface 1602 b. The “blank paper” 1602b is automatically inserted to change the paper because 1602f is the last of the first chapter. “2” is imposed on the front surface 1603f of 1603, and “2” is imposed on the back surface 1603b. “1” is assigned to 1604 f which is the front surface of 1604, and “white paper” is assigned to 1604 b which is the back surface. The “white paper” of 1604b is automatically inserted to change the paper since 1604f is the last of the two chapters. “3” is imposed on 1605 f which is the front surface of 1605, and “3” is imposed on 1605 b which is the back surface. With the above configuration, in the book file of FIG. 16, when the cover is opened, “blank”, “1”, “1”, “blank”, “2”, “2”, “2”, “blank”, “3”, and “3” are closed. And “Back cover” can be printed.

  This is also a problem, and the first page of the chapter is not necessarily in the layout that must come to the left. The first page of Chapter 1 1601b is on the left side of the spread. However, 1603b, which is the first page of Chapter 2, and 1605b, which is the first page of Chapter 3, come to the right side of the spread.

  As shown in FIGS. 15 and 16, the conventional method cannot realize a layout in which the first page of the chapter must come to the left side.

  In order to achieve the above object, the present invention comprises the following arrangement.

  In the bookbinding application 104 and the book file as shown in FIG. 14, in addition to the conventional blank page insertion function, the function to change the page to the chapter separator, and the function to change the paper to the chapter separator, the first page of the chapter is always left side ( Or give it a function to make it come to the right).

  According to the present invention, it is determined whether the first page of the chapter always starts from the left or right side, and a blank page is automatically inserted to create a book file so that imposition does not collapse. This eliminates the need for the user to insert a blank page, improves work efficiency and system productivity, and prevents human error so that high-quality documents can be created. .

  Next, details of the present invention will be described in accordance with the description of the embodiments.

  First, the prerequisite technology will be described. The present invention requires a document processing system and an image forming apparatus. This document processing system includes an electronic manuscript writer that converts a data file created by a general application into an electronic manuscript file, and a bookbinding application that provides a function for editing the electronic manuscript file. It is possible to create and edit a combined document, improve the operability, and efficiently edit the document.

  FIG. 1 is a software configuration diagram of a system applicable to this embodiment.

  FIG. 1 is a diagram showing a software configuration of the document processing system according to the present embodiment. The document processing system is realized by a digital computer 101 (hereinafter also referred to as a host computer) which is a preferred embodiment of the information processing apparatus of the present invention. A general application 101 shown in FIG. 1 is an application program that provides functions such as word processing, spreadsheet, photo retouching, drawing, painting, presentation, and text editing, and has a printing function for the OS. These applications use a predetermined interface (generally called GDI) provided by an operating system (OS) when printing application data such as created document data and image data. That is, the application 101 transmits an OS-dependent output command (referred to as a GDI function) to the OS output module that provides the above-described interface in order to print the created data. . On the other hand, the output module that has received the output command converts the output command into a format that can be processed by an output device such as a printer, and outputs the converted command (referred to as a DDI function). Since the format that can be processed by the output device varies depending on the device type, manufacturer, model, etc., a device driver is provided for each device, and the OS uses that device driver to convert commands and generate print data. A print job is generated by enclosing with JL (Job Language). When using Microsoft Windows (WINDOWS (registered trademark)) as the OS, a module called GDI (Graphic Device Interface) corresponds to the output module described above.

  The electronic manuscript writer 102 is an improvement of the above-described device driver and is a software module provided for realizing the document processing system. However, the electronic document writer 102 is not intended for a specific output device, and converts the output command into a format that can be processed by the bookbinding application 104 and the printer driver 106 described later in detail. The format after conversion by the electronic document writer 102 (hereinafter referred to as an electronic document format) is not particularly limited as long as a document in units of pages can be expressed in a detailed format. Of substantial standard formats, for example, PDF format or SVG format can be adopted as the electronic document format.

  When using the electronic document writer 102 from the general application 101, the electronic document writer 102 is designated as a device driver used for output, and printing is executed. However, the electronic document file as created by the electronic document writer 102 does not have a complete format as an electronic document file. Therefore, the bookbinding application 104 designates the electronic document writer 102 as a device driver, and conversion of application data into an electronic document file is executed under the management of the bookbinding application 104. Then, the bookbinding application 104 completes the new incomplete electronic document file generated by the electronic document writer 102 as an electronic document file having a format described later. Hereinafter, when it is necessary to clearly identify this point, a file created by the electronic manuscript writer 102 is called an “electronic manuscript file”, and an electronic manuscript file given a structure by the bookbinding application 104 is called a “book file”. Call. If there is no need to distinguish between them, a document file, an electronic manuscript file, and a book file generated by an application are all referred to as a document file (or document data).

  In this way, by specifying the electronic document writer 102 as a device driver and printing data by the general application 101, the application data is electronic in units of pages (hereinafter referred to as logical pages or document pages) defined by the application 101. It is converted into a document format and stored as an electronic document file 103 in a storage medium such as a hard disk. The hard disk may be a local drive included in a computer that implements the document processing system of the present embodiment, or may be a drive provided on the network when connected to the network.

  The bookbinding application 104 reads an electronic original file (or book file) 103 and provides a user with a function for editing the electronic original file (or book file) 103. However, the bookbinding application 104 does not provide a function for editing the contents of each page, but provides a function for editing the structure of a chapter or book, which will be described later, configured with a page as a minimum unit.

  When the book file 103 edited by the bookbinding application 104 is printed, the bookbinding application 104 activates the electronic document despooler 105. The electronic document despooler 105 is a program module installed in the computer together with the bookbinding application, and is a module used to output drawing data to the printer driver when printing a document (book file) used in the bookbinding application. It is. The electronic manuscript despooler 105 reads out a designated book file from the hard disk and generates an output command suitable for the OS output module described above to print each page in the format described in the book file. Output to the output module. At that time, the printer driver 106 for the printer 107 used as the output device is designated as the device driver. The above-described output module converts the received output command into a device command and outputs the device command to the designated printer driver 106 for the printer 107, and the printer driver 106 converts the command into a command such as a page description language that can be interpreted by the printer 107. Convert. The converted command is transmitted from the printer driver 106 to the printer 107 via a system spooler (not shown), and the printer 107 prints an image corresponding to the command.

  FIG. 2 is a block diagram showing the configuration of a personal computer applicable to the present embodiment.

  2, a CPU 201 executes programs such as an OS, a general application, and a bookbinding application that are stored in a program ROM of the ROM 203 or loaded from the hard disk 211 to the RAM 202, and the software configuration in FIG. Realize the procedure. The RAM 202 functions as a main memory, work area, and the like for the CPU 201. A keyboard controller (KBC) 205 controls key input from a keyboard 209 or a pointing device (not shown). A CRT controller (CRTC) 206 controls display on the CRT display 210. A disk controller (DKC) 207 controls access to a hard disk (HD) 211, a flexible disk (FD), or the like that stores a boot program, various applications, font data, user files, edit files (to be described later), and the like. The PRTC 208 controls the exchange of signals with the connected printer 107. The NC 212 is connected to the network and executes communication control processing with other devices connected to the network.

<Electronic manuscript data format>
Before referring to details of the editing application 104, the data format of the book file will be described. The book file has a three-layer structure that mimics a paper medium book. First, the upper layer is called a “book”, imitating one book, and attributes related to the book in general are defined. The middle layer below it corresponds to the chapter in the book and is also called “chapter”. For each chapter, attributes for each chapter can be defined. The lower layer is “page”, which corresponds to each page defined by the application program. For each page, attributes for each page can be defined. Further, one book may include a plurality of chapters, and one chapter may include a plurality of pages.

  FIG. 3 is a format diagram of a book file applicable to this embodiment.

  FIG. 3A is a diagram schematically illustrating an example of a book file format. As shown in the figure, in this example, the book, chapter, and page in the book file are indicated by corresponding nodes. One book file contains one book. Since the book and chapter are concepts for defining the structure of the book, they include defined attribute values and links to lower layers as entities. The page has data for each page output by the application program as an entity. Therefore, a page includes a document page entity (document page data) and a link to each document page data in addition to the attribute value.

  Note that a print page when outputting to a paper medium or the like may include a plurality of document pages. This structure is not displayed by a link, but is displayed as an attribute in each hierarchy of a book, chapter, and page.

  In FIG. 3, a book 301 has a book attribute defined therein and two chapters 302A and 302B are linked. By this link, it is displayed that chapters 302A and 302B are included in book 301. The chapter 302A is linked to pages 303A and 303B, indicating that these pages are included. Each page 303A, 303B has an attribute value defined, and includes links to the original document page data (1), (2). These links indicate the data (1) and (2) of the original page data 304 as shown in (B) of FIG. 3, and the entities of the pages 303A and 303B are the original page data (1) and (2). Is displayed.

  FIG. 4 is a list of book attributes applicable to the present embodiment.

  For items that can be defined overlapping with the lower layer, the attribute value of the lower layer is preferentially adopted. Therefore, for items included only in the book attribute, the value defined in the book attribute becomes a valid value throughout the book. However, items that overlap the lower layer have meanings as default values when they are not defined in the lower layer. Each illustrated item does not specifically correspond to one item, but may include a plurality of related items.

  FIG. 5 is a list of chapter attributes applicable to the present embodiment.

  FIG. 6 is a list of page attributes applicable to this embodiment.

  The relationship between chapter attributes and page attributes is the same as the relationship between book attributes and lower layer attributes.

  As is apparent from FIGS. 4 to 6, items unique to the book attributes are six items: printing method, bookbinding details, front / back cover, index paper, slip sheet, and chapter break. These are items defined throughout the book. As printing method attributes, three values of single-sided printing, double-sided printing, and bookbinding printing can be designated. Here, bookbinding printing is a method of printing in a format that allows bookbinding by bundling a separately designated number of sheets into two and folding the bundle. As the bookbinding details attribute, when bookbinding printing is designated, the spread direction, the number of sheets to be bundled, and the like can be designated.

  FIG. 7 shows a processing flow in which a bookbinding application applicable to the present embodiment opens a book file.

  First, it is determined whether the book file to be opened is to be newly created or is an existing one (step S701). In the case of new creation, a new book file not including a chapter is created (step S702). In the example of FIG. 3, the newly created book file is a book node that has only the book node 301 and does not have a link to the chapter node. As the book attribute, a set of attributes prepared in advance for new creation is applied. Then, a user interface (UI) screen for editing the new book file is displayed (step S704). FIG. 11 shows an example of a UI screen when a book file is newly created. In this case, since the book file has no substantial content, nothing is displayed on the UI screen.

  On the other hand, if there is an existing book file, the designated book file is opened (step S703), and a user interface (UI) screen is displayed according to the structure, attributes, and contents of the book file. FIG. 10 is an example of a UI screen that displays a book file designated from an existing book file. The UI screen 1100 includes a tree portion 1101 that shows a book structure, and a preview portion 1102 that displays a printed state. The tree portion 1101 displays chapters included in the book and pages included in each chapter in a tree structure as shown in FIG. A page displayed in the tree portion 1101 is a manuscript page. In the preview area 1102, the contents of the print page are reduced and displayed. The display order reflects the book structure.

  In the opened book file, application data converted into an electronic manuscript file by the electronic manuscript writer 102 can be added as a new chapter. This function is called an electronic document import function. By importing an electronic document into a newly created book file by the procedure shown in FIG. 7, an entity is given to the book file. This function is activated by dragging and dropping application data on the screen of FIG.

  FIG. 8 is an electronic manuscript import process flow of the bookbinding application applicable to this embodiment.

  First, the application program that generated the specified application data is activated, the electronic document writer 102 is specified as a device driver, and the application data is printed out to be converted into electronic document data (step S801). When the conversion is completed, it is determined whether or not the converted data is image data (step S802). This determination is made based on the file extension of the application data under the Windows OS. For example, if the extension is “bmp”, it is determined to be Windows bitmap data, if “jpg”, it is determined to be jpg compressed image data, and if “tiff”, it is determined to be image data in the tif format. Further, in the case of such image data, it is possible to generate an electronic document file directly from the image data without activating an application, so that the processing of S801 can be omitted.

  If it is not image data, the electronic document file generated in step S801 is added as a new chapter to the book of the book file that is currently open (step S803). As the chapter attribute, the value of the book attribute is copied for those that are common to the book attribute, and for those that are not, the preset value is set in advance.

  In the case of image data in step S802, a new chapter is not added in principle, and each original page included in the electronic original file generated in step S801 is added to the designated chapter ( Step S804). However, if the book file is a newly created file, a new chapter is created, and each page of the electronic document file is added as a page belonging to the chapter. As for the page attribute, an attribute value is given to an attribute common to the upper layer attribute, and a value is given to an attribute that inherits the attribute defined in the application data in the electronic document file. For example, when Nup designation or the like is designated in the application data, the attribute value is inherited. In this way, a new book file is created or a new chapter is added.

  FIG. 9 is a processing flow for generating an electronic manuscript file by an electronic manuscript writer of a bookbinding application applicable to this embodiment.

  FIG. 9 is a flowchart of a procedure for generating an electronic document file by the electronic document writer 102 in step S801 shown in FIG. First, a new electronic document file is created and opened (step S901). An application corresponding to the designated application data is started, and an output command is transmitted to the output module of the OS using the electronic document writer as a device driver. The output module converts the received output command into electronic document format data by the electronic document writer 102 and outputs the converted data (step S902). The output destination is the electronic document file opened in step S901. It is determined whether the conversion has been completed for all the designated data (step S903). If the conversion has been completed, the electronic document file is closed (step S904). The electronic manuscript file generated by the electronic manuscript writer 102 is a file including the manuscript page data entity shown in FIG.

<Edit book file>
As described above, a book file can be created from application data. With respect to the generated book file, the following editing operations are possible for chapters and pages.

(1) New addition (2) Delete (3) Copy (4) Cut (5) Paste (6) Move (7) Rename chapter (8) Rename page number (9) Insert cover (10) Insert paper Insert (11) Insert index sheet (12) Page layout for each document page.

  In addition, an operation for canceling an editing operation once performed, and an operation for redoing the canceled operation are possible. With these editing functions, for example, integration of multiple book files, rearrangement of chapters and pages in the book file, deletion of chapters and pages in the book file, layout change of manuscript pages, insertion of slip sheets and index sheets, etc. Operation becomes possible. When these operations are performed, the operation results are reflected in the attributes shown in FIGS. 4 and 5, or in the book file structure. For example, if a blank page new addition operation is performed, a blank page is inserted at a designated location. This blank page is treated as a manuscript page. If the layout of the original page is changed, the changed content is reflected in attributes such as a printing method, N-up printing, front / back cover, index paper, slip sheet, and chapter break.

<Output book file>
The book file created and edited as described above has a final purpose of print output. Here, when the user selects a file menu from the UI screen 1100 of the bookbinding application shown in FIG. 10 and selects print from there, the output is printed by the designated output device. At this time, the bookbinding application 104 first creates a job ticket from the currently opened book file, and passes the job ticket to the electronic document despooler 105. On the other hand, the electronic document despooler 105 converts the job ticket into an OS output command, for example, a Windows GDI function, and transmits it to an output module, for example, GDI. The output module generates a command suitable for the device by the designated printer driver 106 and transmits the command to the device.

  Here, the job ticket is data having a structure in which the original page is a minimum unit. The structure in the job ticket defines the layout of the manuscript page on the paper. One job ticket is issued per job. For this reason, there is a document node at the top, and attributes of the entire document, such as double-sided printing / single-sided printing, are defined. Below that, a paper node belongs, and includes attributes such as an identifier of a paper to be used and designation of a paper feed port in the printer. Each paper node includes a node of a sheet printed on the paper. One sheet corresponds to one sheet. A print page (physical page) belongs to each sheet. For single-sided printing, one physical page belongs to one sheet, and for double-sided printing, two physical pages belong to one sheet. Each physical page has an original page arranged thereon. The physical page attribute includes the layout of the original page.

  The electronic document despooler 105 converts the above-described job ticket into an output command to the output module.

<Other system configurations>
The outline of the document processing system of this embodiment is as described above. Although this is a stand-alone system, a book file can be created and edited with almost the same configuration and procedure even on a server client system that is an expanded system. However, book files and print processing are managed by the server.

  FIG. 17 is a UI for designating a case binding method for case binding of a bookbinding application applicable to this embodiment.

  The bookbinding application 104 has a UI for designating a print style as shown in FIG. 17 in addition to the imposition preview screens shown in FIGS. A UI 1701 can set a printing method, a bookbinding method, and a chapter break operation. 1701 can be called from the UI menu of FIG. Reference numeral 1702 denotes a print method setting field. As the printing method, single-sided printing or double-sided printing can be selected. Reference numeral 1703 denotes a chapter division setting field. By setting 1703, it is possible to specify how imposition is performed when a chapter break comes. The present invention is characterized in that the items 1703 include “set chapter start to right page” and “set chapter start to left page”.

  FIG. 18 is a table that holds print formats applicable to the present embodiment.

  FIG. 18 shows a data area for managing the print format in the bookbinding application 104. The bookbinding application performs imposition, book file creation, print instruction, and the like according to the information in the print format table. The management and holding method of the print style table is the same as that in Patent Document 1 and is not included in the features of the present invention, and will not be described. Reference numeral 1801 denotes a printing style table. Reference numeral 1801 denotes a table having setting information designated by the UI unit of the bookbinding application 104 such as 1701 or internal setting information. This table has a large number of items because it has data relating to the print format, but only the parts necessary for the present invention will be described here. Reference numeral 1802 denotes a data area for the printing method. This value is determined by the UI of 1702. “Double-sided” is now set. Reference numeral 1803 denotes a chapter delimiter data area. This value is determined by the UI of 1703. Now, “Not specified” is set. In addition, there are some items such as 1804.

  FIG. 19 is a processing flow when the case binding method for case binding applicable to this embodiment is designated.

  FIG. 19 shows a flowchart of automatic blank page generation processing in accordance with “chapter break” as a result of setting “both sides” in 1702 and “set chapter start to left page” in 1703 in the UI of FIG. ing. This flowchart is called when determining the number of blank sheets at the end of a chapter when determining the layout of each chapter. First, in response to a print instruction, a blank sheet is inserted in accordance with chapter breaks in S1901. Details of this processing will be described with reference to FIG. Next, imposition processing is performed in S1902. In S1902, the electronic document data that has been impositioned is completed. In step S1903, the bookbinding application 104 performs printing on the printing apparatus. The print data is electronic original data created in S1902.

  FIG. 20 is a processing flow for inserting a blank page according to the chapter break setting applicable to the present embodiment.

  FIG. 20 is called in S1901. The processing flow of FIG. 20 automatically adds a blank page in a chapter so that the imposition of the book file becomes “change the start of the chapter to the left page”. The blank page to be added is a blank page managed internally unlike the blank page added by the user. This is called an internal blank page. The internal blank page cannot be deleted by the user on the UI. Further, when imposition is changed, the internal blank page is calculated and reconstructed each time, so that the user does not have to be aware of it. Now, assuming that “Make chapter start left page” is selected in the UI 1703 of FIG. 17, the flow of FIG. 20 will be described. First, in step S2001, the chapter break setting is confirmed. Here, in cases other than “change chapter start to left page”, the processing of FIG. 20 is skipped and processing according to conventional chapter setting is performed. Next, in S2002, the first chapter is regarded as not being processed. The first chapter is a cover as shown by 301 in FIG. “Make chapter start left page” does not apply to front and back covers. An example of adaptation will be described in the second embodiment. S2003 is a start determination of loop processing. If there are multiple chapters, it will loop the number of chapters. In step S2004, it is determined whether the first page (start) of the chapter is imposed on the surface of the paper. If it is the front side, the process proceeds to S2005, and if it is the back side, the process proceeds to S2006. If it is the front side in S2004, N-up blanks are added to the beginning of the chapter in S2005. As a result of the N-up shift, blank pages will come to the front, and the page at the beginning of the chapter will come to the back of the paper. That is, when it is spread, it will come to the left. In step S2006, the imposition position of the last page of the chapter is calculated from the number of chapter pages and N-up information. In step S2007, it is determined whether there is an area that can be further imposed on the sheet on which the last page of the chapter is imposed. If there is an impositionable area remaining, the process proceeds to S2008, and if not, the process proceeds to S2009. In S2008, when there is an impositionable area remaining, a blank sheet is inserted until the sheet is full. This ensures that the beginning of the next chapter always starts with the next sheet. In step S2009, the end of the loop process is determined. The process belongs to S2003 until it is performed for all chapters. This completes the internal blank sheet insertion process in the case of “set chapter start to left page”. In S1902, if imposition is performed, bookbinding can be created such that the start of the chapter is the left page.

  FIG. 21 shows a book file when a blank page is inserted according to the chapter break setting applicable to this embodiment.

  FIG. 21 is a book file when the processing flow of FIG. 20 is adapted to the book file of FIG. Internal blank papers 2101, 1022, and 2103 are inserted. When this book file is printed by case binding, you can see that the first page of the chapter is on the left side.

  FIG. 22 is a processing flow for inserting a blank page according to the chapter break setting applicable to the present embodiment.

  FIG. 22 is basically the same processing as FIG. FIG. 20 is a processing flow when “chapter start is set to the left page”, whereas FIG. 22 is a processing flow when “chapter start is set to the right page”. Since S2002, S2003, S2004, S2007, S2008, and S2009 in FIG. 22 are the same as those in FIG. 20, description thereof will be omitted. In step S2201, the chapter break setting is confirmed. Here, in the case other than “change the chapter start to the right page”, the process is exited as in FIG. If it is the back side in S2004, N-up blanks are added to the beginning of the chapter in S2205. As a result of the N-up shift, blank pages will come to the front, and the page at the beginning of the chapter will come to the back of the paper. In step S2206, the imposition position of the last page of the chapter is calculated from the number of chapter pages and N-up information.

(Effect of Example 1)
According to the first embodiment, by selecting “Make chapter start on right page” or “Make chapter start on left page” in the UI, the first page of the chapter always starts from the left or right side. And automatically insert a blank page to create a book file so that the imposition does not collapse. This eliminates the need for the user to insert a blank page, improves work efficiency and system productivity, and prevents human error so that high-quality documents can be created. .

  In the first embodiment, the cover is treated as an exception in the processing of FIG. In case binding, you can also specify the binding direction of the cover page, and the setting of “Start chapter at the right page” or “Start chapter start at the left page” can be set including the cover page. Improvement can be expected.

  In the second embodiment, processing including a cover will be described.

  This embodiment is shown in FIGS. 1, 2, 3, 4, 6, 7, 7, 8, 9, 10, 11, 13, 14, 15, 15, 16, 17, Since FIG. 18 and FIG. 19 are the same as those in the first embodiment, a description thereof will be omitted.

  FIG. 23 is a processing flow in consideration of a cover page into which a blank page is inserted in accordance with the chapter break setting applicable to this embodiment. FIG. 23 is basically the same processing as FIG. FIG. 20 is a processing flow having a subroutine when there is a cover exception, whereas FIG. Since S2001, S2003, S2004, S2005, S2006, S2007, S2008, and S2009 in FIG. 23 are the same as those in FIG. 20, description thereof will be omitted. In step S2302, the front cover imposition process is performed. This will be described with reference to FIG.

  FIG. 12 is a cover exception processing flow for inserting a blank page according to the chapter break setting applicable to this embodiment.

  In FIG. 12, the cover is impositioned. FIG. 12 is an explanatory diagram based on the premise that “Make chapter start left page” is designated. First, in S2401, the binding direction of the cover is determined. The binding direction of the cover sheet can be acquired from the print style table 1801 in FIG. If the binding direction is left open, the process proceeds to S2402, and if the binding direction is right open, the process proceeds to S2405. In S2402, it is determined whether or not the cover is an exception. Since it is premised that “the chapter start is set to the left page”, if the cover is not an exception, the process proceeds to S2403 where the cover is also imposed from the left of the sheet. However, when creating a left-open cover, the cover cannot be bound unless it is impositioned on the right side of the sheet. Therefore, this exception is not allowed and an error is notified to the user in S2403. The error handling may be a dialog or a warning that rounds the settings, or anything. Whether or not to return processing after an error depends on the creation of the bookbinding application. In the case where the cover exception is made in S2402, the cover is imposed from the right side of the sheet. This exception is allowed because the front cover is always impositioned from the right. In S2404, imposition is performed as set. S2405 is a cover exception determination process at the time of right opening. When opening right, the cover is impositioned from the left. If the cover is an exception, the cover will be imposed from the right, so bookbinding cannot be performed. Therefore, this exception is not allowed, and an error is notified to the user in S2406 as in S2403. If no cover exception is made in S2402, the cover is imposed from the left side of the paper. This exception is allowed because the front cover is always impositioned from the left. However, when the printing direction on the paper is determined by the printing device, it is necessary to replace the front cover and the back cover in step S2407 so that the order is reversed.

(Effect of Example 2)
According to the second embodiment, in addition to the first embodiment, a blank page is automatically inserted so that the imposition is not automatically broken, including a cover page, and a book file is created. This eliminates the need for the user to insert a blank page, improves work efficiency and system productivity, and prevents human error so that high-quality documents can be created. .

It is a software block diagram of the system applicable to a present Example. It is a block diagram which shows the structure of the personal computer applicable to a present Example. It is a format diagram of a book file applicable to the present embodiment. It is a list of book attributes applicable to the present embodiment. It is a list of chapter attributes applicable to the present embodiment. It is a list of page attributes applicable to the present embodiment. This is a processing flow in which a bookbinding application applicable to the present embodiment opens a book file. It is an electronic manuscript import processing flow of a bookbinding application applicable to the present embodiment. It is a processing flow in which an electronic manuscript file is generated by an electronic manuscript writer of a bookbinding application applicable to the present embodiment. It is an example of UI screen which displays the book file designated from the existing book file applicable to a present Example. It is an example of a UI screen when a new book file applicable to the present embodiment is created. It is a cover exception processing flow for inserting a blank page according to the chapter break setting applicable to this embodiment. It is a bookbinding preview screen that is a problem applicable to the present embodiment. This is a preview of case binding that is a problem applicable to the present embodiment. This is a blank paper insertion pattern of a case binding preview, which is a problem applicable to the present embodiment. This is a paper switching pattern for a case binding preview, which is a problem applicable to the present embodiment. This is a UI for designating a case binding method for case binding of a bookbinding application applicable to this embodiment. It is a table holding a print format applicable to the present embodiment. It is a processing flow when the case binding method of case binding applicable to the present embodiment is designated. It is the processing flow which inserts a blank page according to the setting of the chapter breaks applicable to a present Example. This is a book file when a blank page is inserted in accordance with the chapter break setting applicable to the present embodiment. It is the processing flow which inserts a blank page according to the setting of the chapter breaks applicable to a present Example. This is a processing flow that takes into account a cover into which a blank page is inserted in accordance with the chapter break setting applicable to this embodiment.

Claims (3)

In a document processing system that can set and change the print format when printing a document,
There is a specification means that has a logical division between chapters, can combine different print styles for each chapter, and can specify the print style of the entire document, and how to impose the first page of the next chapter An insertion means for inserting a blank manuscript page so that it can be a first page of a spread, and a means for rearranging the manuscript page according to the inserted layout Document processing system.   When specifying chapter breaks, insert means to insert blank manuscript pages and manuscript pages are inserted so that the first manuscript page impositioned at the beginning of each chapter is always in the same direction. The document processing system according to claim 1, further comprising means for rearranging according to a layout.   3. The document processing system according to claim 1, further comprising means for determining whether or not the function is valid for the front cover or the back cover when performing layout for each separation.

Images