JP4549379B2 - Document processing apparatus, document processing method, and program - Google Patents

Description

  The present invention relates to a document processing apparatus and a document processing method having an automatic layout function for completing a document by arranging fields of records registered in a database at predetermined positions, for example.

  In recent years, CRM (Customer Relationship Management) and One-to-One (1) due to factors such as the shortening of product life due to the increase in product variety and the orientation of consumer customization services due to the widespread use of the Internet. 1) The need for marketing is drawing attention. These methods aim to increase customer satisfaction and to cultivate and retain customers.

  Customer relationship management is a mechanism that enhances customer satisfaction and improves the profitability of a company by responding to individual needs based on a customer database. One-to-one marketing is a type of database marketing that creates a database of personal attribute information such as customer's age, gender, hobbies, preferences, purchase history, etc., analyzes the content, and makes proposals that meet customer needs. This is a marketing method to be performed, and a typical application example is variable print. Recently, with the advancement of DTP (desktop publishing) technology and the spread of digital printing devices, a variable print system that customizes and outputs documents for each customer has been developed and optimally laid out different amounts of content for each customer. It is now required to create a document.

  Conventionally, in a variable print system, a layout frame (also referred to as a container) is created on a document, and records and fields that satisfy certain conditions of a database are associated as contents of each container. In this way, variable printing has been realized by associating the database with the layout.

  However, since the sizes of the text and image containers are fixed, when the data in the database is inserted into the container, if the amount of data exceeds the container size, text overlap and image clipping occur. Further, if the data amount is smaller than the container size, a gap is left.

  As a technique for solving these problems, a technique for reducing the size of an adjacent area when the size of a certain character area increases is disclosed in Patent Document 1, and characters are input to the character area. According to the document, the size of the character region is expanded and the size of the region adjacent to the character region is reduced.

  As described above, some conventional automatic layout techniques can dynamically change the size of a layout frame (container) in accordance with the amount of input text.

  Patent Document 2 also describes a technique for arranging a plurality of product information (product records) in a layout area in a page.

In this technology, a master part (equivalent to the sub template in this case) with a preset layout (for example, placement of product name, image, price, etc.) is prepared, and which master part is used for each product information To do. Then, data (product name, image, price, etc.) included in the product information is arranged in a predetermined area in the set master part and sequentially arranged in a layout area designated in the page. In the present application, the function of arranging information of one record according to the sub template and sequentially arranging a plurality of sub templates in the flow area is called a multi-record function, and the operation is expressed as flowing the sub template into the flow area. .
JP-A-7-129658 JP 2000-48216 (paragraphs 0025 to 0055, FIGS. 2 and 11)

  However, the technique described in Patent Document 1 describes that the character area is enlarged in accordance with the input of the text. However, when the size of the character area increases, the adjacent areas are kept apart. As the amount of input text increases, the adjacent area continues to be reduced.

  Furthermore, Patent Document 1 does not consider a variable print system that creates a customized document for each customer by associating the above-described database with each region and flowing content data.

  Moreover, in the technique described in Patent Document 2, it is necessary to set in advance which master part should be used for each record. For example, when the number of records is enormous, it is set according to an increase in the number of records. Therefore, the number of operations for doing so increases, and the operability for the user is lowered.

  Further, it is assumed that some users want to use the same master part for records having similar data attributes. For example, when creating a document using records 1 to 10, it is assumed that the same price data is set in record 2 and record 5. In this case, the user may want to create a document using the same master part for records 2 and 5 having the same data attribute in the record.

  In such a case, in the technique described in Patent Document 2, it is necessary to preset which master part should be used for each record. Therefore, the master part used in record 2 is remembered, and the master part is stored in record 5. When setting, the master part must be selected based on the user's memory. However, the number of records for creating a pamphlet or catalog is normally expected to be enormous, and more types of master parts are used. At this time, it is difficult to say that the method of selecting the master part only by the user's memory is optimal.

  In Patent Document 2, depending on the number of records to be arranged in the layout area, there are cases where the record cannot be stored in the designated layout area. In the case where only one page of layout area has been set, Patent Document 2 moves to the next layout candidate position and arranges it, but the process in the case where it cannot move to the next layout candidate position is described. As a result, there arises a problem that data cannot be laid out.

  In addition, as a general process when it is not possible to lay out all the records in this way, a method of reducing the data to be laid out can be considered, but by changing the size of the data to be laid out, the user's desired The layout size may not be obtained.

  In this way, assuming that the user creates a catalog or pamphlet that the customer seems to like, the conventional technology alone provides a good operability for the user, and documents according to various customer preferences. It becomes difficult to create.

  In addition, with conventional multi-record printing (a function for printing a document by arranging a plurality of records in one document), a document is only printed when a specific item of the record is changed (for example, a customer name is changed). Dividing (for example, dividing a document for each customer) could only be done in one simple hierarchy. This makes it difficult to insert a document break (also called a break) at a desired position, for example, when the user wants to change the page for each product, making it difficult to create an orderly document or a document with a desired break. Met.

  The present invention has been made in view of the above problems, and in order to achieve a variety of output results according to customer preferences while maintaining user operability, conditional expressions are set in regions on the template. It is another object of the present invention to provide a document processing apparatus and method having an automatic layout function for laying out record data extracted based on the conditional expression into a plurality of types of sub-templates and arranging them in a predetermined area.

  In addition, in order to obtain an output result desired by the user without reducing the size of data to be arranged, an automatic layout function for generating a page having the area when the extracted record cannot be arranged in the area is provided. An object of the present invention is to provide a document processing apparatus and method.

  Another object of the present invention is to provide a document processing apparatus and method having a multi-record automatic layout function that can increase the degree of freedom of document delimiter insertion and thereby realize an orderly layout or a layout reflecting the user's will. To do.

Alternatively, a document processing apparatus that executes layout processing using first and second pages having areas for arranging content data,
Obtaining means for obtaining the content data;
When the content data acquired by the acquisition unit overflows from the areas of the first and second pages and the area included in the first page is larger than the area included in the second page, the first and second The content data is arranged in a two-page area and a new page area generated based on the first page, and the content data acquired by the acquisition unit overflows from the first and second page areas, When the area included in the second page is larger than the area included in the first page, the first and second page areas and a new page area generated based on the second page Arrangement means for arranging content data.

  According to the present invention, when an extracted record cannot be arranged in an area, a template having the area is generated. Therefore, a layout document desired by the user can be obtained without reducing the size of data to be arranged. It becomes possible to create.

  Alternatively, according to the present invention, the content data included in one of the plurality of records is input to the partial area included in the subtemplate, and the process for determining the layout in the subtemplate is executed. If a plurality of sub-templates cannot be arranged in the region, a template having a region for which extraction conditions are set is newly generated.

[First Embodiment]
<Outline of Embodiment>
An embodiment suitable for applying the example of the present invention will be described. First, an outline of the invention will be described. In the present embodiment, a so-called variable print that creates a document in which a database record or the like is arranged in accordance with a container (a partial area into which data is flowed: also called a field area) defined in a document template (also called a template). The present invention relates to computer software for realizing a function called as “computer”. A computer loaded with this software executable functions as an automatic layout system (or document processing apparatus). In this embodiment, in particular, not only data is arranged according to a template, but also a part of a document is created according to the template, and the part of the document is inserted into an area (referred to as a flow area) separately defined in the template. Software with a function to complete a document (multi-record function) is disclosed. The number of documents that can be inserted is not necessarily one for one flow area. Furthermore, when a plurality of flow areas are defined in the template, a technique for distributing a part of a created document for each flow area according to a certain condition is also disclosed. A template arranged in the flow area is particularly called a sub template. A template including a flow area is particularly called a master template.

  Here, the automatic layout system of this embodiment has two characteristic functions. The first function is to automatically generate a multi-page document by arranging the record on a new page when the record does not fit on one page, for example, when the number of records is very large. The second is a function for arranging individual records using a format (sub-template) corresponding to the records to increase the degree of freedom of document layout. Next, the configuration of the computer system and the application configuration in the present embodiment to which the present invention is applicable will be described.

<System configuration diagram>
FIG. 1A illustrates a system 100 for printing a variable data document. The method described herein is implemented by executing a predetermined program on the general-purpose computer module 101 described in detail in FIG. 1B. The process described in FIG. 1A is executed by the computer module 101 and executed by the whole or a part of software such as the layout editing application program 121 that can be executed on the system 100. In particular, the layout editing and printing steps are performed by software instructions executed by the computer 101 which is the document processing apparatus of the present invention. The software is stored in a computer readable medium including a storage device as described below, for example. The software is loaded into the computer from the computer readable medium and executed by the computer 101. A computer readable medium having a computer program recorded on such software or medium is a computer program product. By using the computer program product on a computer, the computer functions as an apparatus that can perform document layout editing and variable data printing.

  The computer module 101 is connected to an input device such as a keyboard 132 and a pointing device such as a mouse 133, and an output device including a display device 144 and a local printer 145 depending on the situation. The input / output interface 138 can connect the computer module 101 from the network connection 107 to connect to other computer devices in the system 100. A typical network connection 107 is a local area network (LAN) or a wide area network (WAN).

  The computer module 101 generally includes at least one processor unit 135, for example, a memory unit 136 composed of a semiconductor random access memory (RAM) or a read only memory (ROM), and an INPUT / OUTPUT (I / O) Interface, I / O interface 143 for keyboard 132 and mouse 133 is included.

  The storage device 139 generally includes a hard disk drive 140 and a flexible disk drive 141. Although not shown in FIG. 1B, a magnetic tape drive may also be used. The CD-ROM drive 142 is provided as a nonvolatile data source. The computer module 101 communicates via the interconnect bus 134 in accordance with an operating system such as GNU / LINUX® or Microsoft Windows®, or by a method according to the conventional operating mode of the computer system. Each component (reference numeral 135 to reference numeral 143) included in the computer module 101 to be performed is used.

  The layout editing application program 121 of FIG. 1A normally resides in the hard disk drive 140 of FIG. 1B, and is executed, read and controlled by the processor 135. In some cases, the application program 121 is encoded on a CD-ROM or flexible disk, and is read through the corresponding flexible disk drive 142 or CD-ROM drive 141 and provided to the user. Alternatively, the application program 121 may be read from the network connection 107 by the user. In addition, software includes magnetic tape or ROM or integrated circuits, magneto-optical disks or wireless or infrared communication between computer module 101 and other devices, computer readable cards such as PCMCIA cards, and recorded information on email communications and WEB sites. May be loaded into the computer module 101 from other suitably sized computer readable media, including the Internet and Intranets. The above examples are merely examples of related computer readable media. Other computer readable media may also be used.

  The layout editing application 121 instructs to perform variable data printing (VDP) and includes two software components. Among these, the first component is a layout engine 105, which is a software component for calculating the positions of rectangles and lines constituting the container according to the restrictions and sizes given by the rectangular container. The layout engine 105 can calculate the position and the like not only for the container but also for other objects. The layout engine 105 operates as an application for determining the size and position of each partial area (for example, a container), and outputs drawing information to a printer driver (not shown) so that the printer driver performs image drawing processing of a variable data document. Generate print data.

  The second component, the user interface 103, provides a mechanism for allowing a user to create a document template and associate it with a data source within the document template. The document template is data that becomes a template in which a fixed sentence or the above-described container is arranged on a document, for example. A document is completed by flowing data such as text and images taken from a database into a predetermined area of the document template, for example, a container.

  The user interface 103 and the layout engine 105 communicate via a communication channel 123. The data source for document generation is a general database 119 that resides on a database server 117 that is typically configured by another computer running a database application. Host computer 101 communicates with database server 117 via network connection 107. The variable data printing application 121 generates a document template stored in the file server 115 configured by the host computer 101 or generally another computer. The variable data printing application 121 generates a document composed of a document template merged with data. These documents are stored in the local file system of the host computer 101, stored in the file server 115, or printed directly on the printer 113. The print server 109 is a computer that provides a network function to a printer that is not directly connected to the network. The print server 109 and the printer 113 are connected via a general communication channel 111.

  The template data 131 is also called a document template, and is template data of a document in which an area called a container in which a record read from a database or the like is embedded, fixed data, or the like is defined. This configuration will be described later with reference to FIGS.

    FIG. 34 is a diagram for explaining the outline of variable data printing according to this embodiment. A user interface module 103 (hereinafter referred to as user interface 103) of the layout editing application 121 arranges a plurality of containers 345 to 347 on a page in accordance with an operation instruction from the user, and places constraints on positions and sizes in each container. By assigning, a document template 344 is generated.

  The user interface 103 associates the document template 344 with the data source 340 (database 119 in FIG. 1), and further associates each container with each data field in the data source 340. Information associated with each container and each data field in the data source 340 is described in a document template, and the document template is stored in the HDD 140 or the memory unit 136.

  The data source 340 is a file in which item data (variable data) is described in record units, and is stored in the HDD 140. In response to a print instruction or preview instruction from the user, the layout engine 105 reads the associated variable data from the data source 340 into each of the containers 345 to 347 of the document template and flows it in record units (for example, the data record 1). The data fields A to C are poured into the containers 345 to 347), and the size and the like of each container are adjusted (layout adjustment) according to the size of the data to be poured. The layout adjustment method will be described later.

  In the case of a preview instruction, a document image whose layout has been adjusted is generated and output to be displayed as a preview on the screen of the video display 144. In the case of a print instruction, a document image generated using the layout engine 105 or the printer driver is output as print data to the print server 109. By sequentially processing the data records 1, 2, 3,..., Variable data printing is realized.

  The data source (340) for document generation may be, for example, a general database 119 on a database server 117 configured by another computer running a database application. In this case, the host computer 101 can communicate with the database server 117 via the network 107 and acquire a data source. The document template (344) for variable data printing generated by the layout editing application 121 is stored in the file server 115 constituted by the host computer 101 or another computer. As described above with reference to FIG. 1C, the layout engine 105 of the layout editing application 121 generates a variable data document constituted by a document template merged with data. These documents are stored in the local file system of the host computer 101, stored in the file server 115, or transmitted to the printer 113 and printed. The print server 109 is a computer for providing a network function to a printer that is not directly connected to the network. The print server 109 and the printer 113 are connected via a general communication channel 111.

  FIG. 2 shows a configuration for causing the layout engine 225 to be executed independently by the engine server 227 from the configuration of FIG. 1A. The engine server 227 is a general computer. The document template stored in the file server 115 can be combined with data stored in the database 119 to generate a document by the layout engine 225 when printing or for other purposes. Such an operation is requested via the user interface 103 or only certain records are required to be printed.

<Application configuration diagram>
(Main window)
As shown in FIG. 3, the user interface 101 includes a user interface formed by an application window 301 displayed on the video display 144 during operation. The window 301 is characterized by a menu bar 302, a tool bar 303, a work area 306 that can be moved by the position / motion of the mouse 133, an optional palette 311, and a cursor / pointer device 313.

  Menu bar 302 is a well-known technique and has a number of menu items 304 that extend below the hierarchy of menu options.

  The toolbar 303 has a widget 305 such as a number of tool buttons that can be hidden or displayed depending on the particular mode of the application. An optional ruler 308 is used to indicate the position of a pointer, page, line, margin guide, layout frame (ie container) or object within the work area. The palette 311 is used to access additional functions such as a library that reads and displays variable data. The palette 311 has a window control 312 for moving, resizing, and closing.

The toolbar area 303 has at least the following “button” that can be selected by the user.
(1) Selection tool button 403: Used to select, move, resize, resize, and lock / unlock a container edge. Containers allow multiple selection by dragging a selection box around multiple containers or holding down the CTRL key while selecting multiple containers.
(2) Image container tool button 404: used to create a container having a static (fixed) or variable image.
(3) Text container tool button 405: used to create a container having static (fixed) or variable text.
(4) Link tool button 406: used to create a link for associating containers, and used to control the link distance.
These buttons are implemented as tooltips of icons that change according to the operation status, as is well known in the art.

  The application window 301 shown in FIG. 3 of the layout editing application 121 can determine a basic layout by laying out containers and links in a page. The basic layout is a basic layout for variable data printing. If each container in the basic layout is a fixed container, the layout of the print results of all records is the same. In addition, when each container in the basic layout is a variable container described later, the size and position of each container varies within the constraints described later depending on the amount and size of data read in units of records. Therefore, the document template created by the layout editing application 121 determines the basic layout to the last, and when a variable container is included, the layout of the final printed matter is adjusted by the read data. .

(Document template)
A work area 306 is used to display and edit the design of the document template. This allows the user to design an overview of the prepared printed document and to understand how the merged document changes based on the amount or size of variable data.

  If an external data source (such as a database record) is linked to the template, variable text and images are displayed in the container so that you can preview the current document.

  Objects that provide visual clues to depict the document structure and variable data containers are always displayed when the cursor is moved over the container or when a container is selected.

  The work area 306 is characterized by a scroll bar 307, an optional ruler 308, and a document template 309. The document template 309 can indicate that there are a plurality of pages.

  The page size of a given document template is specified by the user using well-known techniques. For example, by selecting “Page Setup” from “File” in the menu, a dialog for setting the page size is displayed, and the page size specified by the user is reflected there. The actual number of pages in each document may vary depending on the variable data. If the basic layout does not have a constraint to fit each container on a page of a predetermined paper size, an additional page is automatically created. The border within each page is an optional page margin 310 that indicates the maximum width of a printable object on the page.

  FIG. 3 also shows an example of objects that can be displayed on the document template 309 of one page. They have a plurality of containers 407, 408, unfixed sides 410, links 412 and sliders 413. The function of each object will be described later.

(container)
A container is a space in which fixed or variable text and images are drawn and drawn in a document template, and is laid out while interacting with other containers and objects. The container can be moved, resized and recreated using the pointer 313 by manipulating the pointing device 133 and shown in the user interface of FIG.

More precisely, a container has a collection of settings, a visual representation, and interaction and editing operations. The container definition is explained below.
(1) Fixed or variable content is poured into the container. Variable content is obtained from a data source (eg a database record) and is dynamic in the sense that different documents vary the container size according to different data. Variable content is not included because it is not suitable for printing, as it is animated or otherwise changes over time. Fixed content is displayed in the same way for all documents generated using a single template. However, when the variable content and the link are set, the position of the container including the fixed content may be different in each document due to a change in the position or size of the container including the variable content.

  (2) The container has a decoration function such as a text setting such as a background color, a border, and a font style applied to the content. Such a setting is called a container attribute. The container attribute can be set for each container, but it is also possible to set the same container attribute as a certain container.

  (3) The container is merged with data from the data source when the document is generated. Variable content is obtained as specific data from a data source and is displayed or printed. The content contained in the container can be output, for example, printed, displayed on the screen 144, or both.

  (4) The container has a user interface. For example, it has an interactive GUI for container editing and display settings. User interface elements are usually displayed on screen 144. The user interface 103 displays some of the container decoration functions such as background color and font. It also has a function for editing and displaying container settings. Examples of user interface feature objectives include borders, corner icons for interactively changing and displaying the size and position of containers, or showing container behavior when the container is merged with data from a data source There are overcoated numbers, lines, icons, and text. However, those elements are not printed on the document.

(Container constraints)
Containers have constraints (ie, can be defined) to control how the content displayed or printed in each document fits in the container. These constraints are the primary means by which a user can control a large number of documents with a single document template, as well as linking fixed and variable content with a container. An example of the restriction is “the content height of this container is a maximum value of 4 inches”. Another example of the constraint is “the left edge of the container contents must be displayed in the same horizontal position in each document”. The contents described here are various methods for displaying and editing such constraints using a GUI.

  Content placeholders that specify the placement of fixed content so that the image has a defined location on the page are well known in digital printing technology. In the following description, a container has a position and a size, which can be edited and displayed in a manner known in the art. Here, a description will be given focusing on display / editing in variable data printing.

  The user can specify the size and position of the content of the document by specifying the position, size, constraints, and the like of the container. Since multiple documents are generated from a single document template, the user interface must be used to specify and display the container's specifiable settings and constraints. The container is also used as the user interface.

<Template creation mode (container display / edit)>
The procedure for creating a variable-printed document includes a template creation process for creating a template (template creation mode) and a document creation process for creating a document by inserting content into the created template (especially when previewing a document). This can be divided into two phases. First, the template creation mode will be described.

(How to create a new container)
Containers are described in two types: text containers and image containers. A text container has text and an embedded image. An image container has (stores) only images. The variable means that it can be different for each record as described above.

  A new text container and an image container are created on the document template 309 by dragging a rectangular area with the text container tool 404 and the image container tool 405 that are selected by clicking with the mouse 133 from the widget 305.

  Alternatively, the container may be simply created by clicking on the document template 309 after activating the appropriate tools 404, 405 as well. In this case, a default size container is inserted or a dialog box is provided to enter the dimensions of the new container. Or other ideas may be considered. In this way, the position and size of the rectangle designated by the user on the user interface are directly stored in the hard disk or the like as a document template file when the document template is stored as the position and size of the container on the template.

(Container display method)
The sides of the container define a virtual boundary line when the associated content is displayed in the document. When using a container as a user interface, for example, the left side of the container is treated as the leftmost side where the associated content can be displayed in any document. Similarly, the height of a container may be understood as a limitation on the height at which the associated content can be displayed in the generated document. In this patent proposal, it is assumed that the side or size of the container is changed through the user interface 103.

(User interface definition)
Next, some user interface and layout relationship definitions used to limit the layout of content will be described. The layout example shown in the attached drawings is also displayed according to this definition.

(1) If the left and right sides of the container are solid lines, the width of the container is fixed. If the container width is fixed, the width assigned to the associated content is the same for all documents. However, the height of the container can change.
(2) If the upper and lower sides of the container are solid lines, the height of the container is fixed. If the container height is fixed, the height assigned to the associated content is the same for all documents.
(3) If the distance constraint is fixed, the specified distance is the same for all documents.
(4) If the solid line side of the container is associated with another container using a link described later, the container on the solid line side may be pushed by another container associated with the link and change its position. Links to the upper and lower sides cause a change in position in the vertical direction, and links to the left and right sides cause a change in position in the horizontal direction. The opposite of “fixed” is “variable” meaning that the edge, position, or document constraints may change from document to document. An example of a rule regarding the relationship between the user interface and the layout for realizing the variable is as follows, for example.
(5) If the left and right sides of the container are dotted lines, the width of the container is variable. If the container width is variable, the width assigned to the associated content will vary from document to document.
(6) If the upper and lower sides of the container are dotted lines, the height of the container is variable. If the height of the container is variable, the height assigned to the associated content varies from document to document.
(7) If the distance constraint is variable, the specified distance may change from document to document. By setting the distance restriction, it is possible to perform a layout for adjusting the container distance within the limit of the maximum length / minimum length.
(8) If a dotted line side of a container and another container are associated with each other using a link described later, the container may push (or be pushed) another container associated with the link and change its position. Links to the upper and lower sides cause a change in position in the vertical direction, and links to the left and right sides cause a change in position in the horizontal direction.

  FIG. 4 shows the state of the sides of the container based on the above rule. In general, the state of the side of a container is an element that is displayed as an aid for designing a document template, and thus is not drawn on a printed matter. The set values of the minimum value and maximum value of the width and height set as the constraints of the container are displayed in a secondary dialog window 311 (see FIG. 3).

  Note that the above-described display on the user interface and the constraints of the container itself or between the containers are described from the viewpoint of the user using the user interface, and from the viewpoint of the program executed to realize the user interface. Is the opposite of causality. In other words, the above rules are as follows:

(1) If the data indicates that the container width is fixed, the left and right sides of the container are displayed with solid lines.
(2) If the height of the container is fixed in the data, the upper and lower sides of the container are displayed with solid lines.
(3) If the distance specified by a fixed value is the same for all documents.
(4) When the container width or height is set in the data to be fixed, and the distance (container constraint) with the other container is set for the fixed side, the position of the container is It is determined according to the size of other containers.
(5) If the container width is set to be variable, the left and right sides of the container are displayed with dotted lines.
(6) If the height of the container is set to be variable, the upper and lower sides of the container are displayed with dotted lines.
(7) If the restriction on the distance between the containers is set to be variable, a layout for adjusting the distance between the containers within the limit of the maximum length and the minimum length of the distance can be performed.
(8) When the container width or height is set in the data to be variable, and the distance (container constraint) from the other container is set for the fixed side, the width or height of the container In response, the position of the other container is determined.

  In FIG. 5A, the width of the container 501 is variable. In this case, the side 503 is represented by a solid line, and the variable side 504 is represented by a dotted line. The scale icon 505 is an optional indicator that indicates that the side 504 adjacent to it is variable. In FIG. 5B, the width and height of the container 501 are variable. In FIG. 5C, the container 501 is also variable in both width and height. A handle 502 is also displayed on the user interface in order to perform edge operations.

<Example of document template data>
FIG. 23 shows an example of document template data (referred to as template data) 131. In FIG. 23, template data 131 is stored in the memory 136 or the hard disk 140. The template data includes the following elements.

  (1) Overall size 2302: Indicates the page size of the entire template. The size is indicated by, for example, vertical and horizontal lengths or a standard paper size.

  (2) Container information 2303: For each container arranged in the template, identification information for identifying the container, the reference position (position information) of the container, the length of each side (size information), the container It shows the attributes (attribute information) of the sides and points to be configured, content information associated with the container, and the like. The position information and the size information are defined at the time of creating the template by designation through the user interface of FIG. The position information is a reference position of the container set by the user when creating the container. If the container has a variable position, the size is changed according to the size of the content (image size, text amount) to be poured into the container, and the position is dynamically changed according to the size of each container. If the container has a fixed position, it has fixed position information. For example, by having information that can specify the position of the diagonal point of the container, the position and size can be specified. Of course, all points may have positions on the template, one point may have position information on the template, and the other points may have relative position information. That is, it can be defined by one point of the container and the size of the container. Further, a fixed point may be defined by a position on the template, and a variable point may be defined by a relative position.

  The attribute information indicates attributes such as sides, sides, axes, or intersections of the containers described with reference to FIGS. 3 and 5. For example, an upper side, a lower side, a left side, a right side, a horizontal axis, a vertical axis, each corner point, a center point, a width, and a height are determined for one container. Whether each element is variable or fixed is defined by attribute information. When the document template is created by the user interface of FIG. 4, the operator selects a desired one from the menu “fix” or “variable” displayed in the palette 311 with the sides, points, and axes of the container selected. By selecting an item, either “fixed” or “variable” attribute is written in the container information 2303 corresponding to the selected point or side. For example, all the default values immediately after container creation are set to “variable”. In this example, “fixed” for one side or axis means that the position in the direction orthogonal to the longitudinal direction is fixed, not the length or the longitudinal position of the side or axis. ing. If the attributes of other points or sides are automatically determined by setting the attributes of points or sides, the attributes are also written. For example, when a corner point is designated as “fixed”, the sides between the corner points are also “fixed”. The reverse is also true. Further, for example, when the position of the center point is designated as “fixed”, “fixed” is written in the attribute of the center point, and the attribute of the horizontal axis and the vertical axis is also written as “fixed”. In this case, if the width and height remain variable, the width and height attributes remain “variable”.

  The information related to the associated content (content related information) includes, for example, information indicating the type of whether it is a text container or an image container, an identifier of a data source inserted into the container, such as a database name, a record It includes association information such as a conditional expression for extracting a part or all of a name, a field name, etc., and contents. Further, in the case of a text container, information related to fonts, for example, character modification information such as font type and size, color, italic, bold, underline, etc. are also included in the content related information. The container information 2303 is held as many as the number of containers provided in the document template.

  (3) Link information 2304: A link is an object associated between containers and is one of container constraints. In particular, the link information is information indicating that the distance between two containers connected by a link is constant (fixed link) or variable range (variable link). As link information, for example, for each of the horizontal direction and the vertical direction, identifiers of two containers, information indicating that a link is set between opposing sides of the containers, and containers in the direction along the link Including the distance between. Link information is held for each defined link. As a form of link information, the position of each container side may be held in each of the horizontal direction and the vertical direction, and information indicating that a link is set between the sides may be held.

  (4) Fixed information 2305: Information for defining a fixed part other than the variable part is included. For example, a sentence, an image, or the like common to all documents (all records) generated by applying the template can be defined. For a sentence or an image, the position information may be defined without including the data itself. Of course, it also includes information for defining the position on the template.

  FIG. 24 shows an example of template data 131 ′ used for the multi-record function. Of course, this data is also stored in a memory or the like. In FIG. 24, a flow area called a flow area is defined in a document template and can be flowed as another template. A number of sub-templates corresponding to multi-records are poured into one flow area. In FIG. 24, the template data 131 ′ includes flow area information 2401. Flow area information is held in the template data by the number of flow areas included in the template. The flow area information 2401 includes the following elements.

  (5) Flow area attribute information 2402 indicating the overall position, size, flow type, etc .: The position and size are as described in FIG. The flow type is a code that defines a pattern in which a sub template is poured into the flow area. Since the number of sub-templates to be flowed into the flow area is determined by the multi-record key column and is variable, information defining the layout of the sub-templates within the flow area is the flow type based on the number of sub-templates to be flowed into the flow area.

  (6) Sub-template information 2403: In the sub-template information 2403, content arranged in the sub-template and content laid out in accordance with the sub-template (this will be referred to as laid-out content in this specification). Arrangement information indicating the association with the flow area into which is inserted is included. The sub template information 2403 is information for identifying a template to be inserted into the flow area, for example. The information includes, for example, the name of a template data file (template file). Further, an arrangement condition for arranging the laid-out contents and a flow type for designating in which order the laid-out contents are inserted may be included. As the arrangement condition, a search condition (search expression) of a database to be laid out by the sub template is held. In addition, as a flow type, an identifier indicating the designated flow type is held by specifying from among options prepared in advance, such as Z type, N type, and V type. Alternatively, an arrangement information field may be provided in the record of the database, and the laid-out content may be inserted into the flow area corresponding to the arrangement condition value that matches the value.

  Furthermore, condition information 2403a for specifying a sub-template inserted into the flow area is included as information characteristic of the present embodiment. For example, the condition information 2403a for associating different subtemplates according to the value of a specific field in the database record associated with the subtemplate can be included as the subtemplate information. Thereby, the sub template corresponding to the value of the field is used for the record.

  (7) Multi-record information 2404: The database name associated with the flow area and an identifier such as a field name in each record are included. Records having the same value for the specified field name are fetched (read) from the specified database and laid out in one flow area. There may be a case where the target record is considerably larger than the size of the flow area. In such a case, the flow area is expanded to cover a plurality of pages, and the records are laid out.

<Link setting method>
FIG. 6 shows a UI example of a link setting method. First, in order to set a link, containers (at least two) for setting a link are created. An example in which two containers are created and links are set is shown. Next, the link tool described above is selected. FIG. 6 shows an operation of creating a container and setting a link from a state in which the link tool is selected. 6A to 6C will be described in order.

  6601 and 0602 in FIG. 6A are the same as 407 and 408 in FIG. 3 described above, and mean fixed sides. Reference numeral 0603 denotes a mouse pointer. First, click to select one of the containers to set the link. Next, as shown in FIG. 6B, the mouse pointer is moved to the other container and clicked. Reference numeral 0604 in FIG. 6B denotes a line connecting the clicked position in FIG. 6A and the moved mouse pointer, and is a UI indicating to the user where the link is set. After the second click in FIG. 6B, a link UI indicated by 0605 is displayed at the set location, and the container is in the state shown in FIG. Reference numeral 0606 denotes a side indicated by a dotted line, and indicates a variable side as described above. In such a design, the left container 0601 can have a variable size in the right direction. The right container 0602 can have a variable size in the left direction. By connecting with a link between them, the left and right containers operate so as to variably adjust their sizes while maintaining the distance between them.

  This process is described below from the viewpoint of the data processing in FIG. For example, container information 3303 is defined by creating a container. Then, the layout editing application 121 stores, as link information, that a link has been set between the two selected containers. Then, the attributes of the opposing sides of the two containers to which the link is set are changed as necessary. For example, if at least one of the opposing sides is variable, there is no need to change the attribute of the side. However, if both are fixed, the significance of setting a link is lost, so at least one is made variable. In the example of FIG. 6, both are changed variably. Of course, when the edge attribute is changed, the layout editing application 121 rewrites the attribute information of the changed attribute in the edge whose attribute included in the container information 3303 is changed.

  In the above description, the expression “opposite” is used. However, in addition to the case where the lines seem to face each other, the lines themselves do not face each other (that is, the projections in the longitudinal direction of the two lines overlap). If not, the link can be set between the extension lines if the extension lines are in a facing relationship. In this specification, including the case where the extension lines face each other as described above, the sides associated with the links are expressed as “opposing”. That is, for example, a link can be set between small containers arranged along the diagonal of the template.

  As described above, if one of the opposing sides of the containers associated by the link is variable and the other is fixed, the variable side may move depending on the content size. Then, according to the movement amount of the variable side, the container on the fixed side side moves in parallel (when there is no anchor). The distance between containers defined in the link (distance in the direction along the link) is maintained. If both sides are variable, the size of the quantity container is variable according to the size of the content, but the distance between the containers is maintained in this case as well.

<Preview mode (layout calculation)>
FIG. 7A shows a flow of layout calculation in the preview mode. The layout calculation is a process of recalculating the container size and the container arrangement according to the data size of the content when actual data is inserted into the container of the document template. In FIG. 7A, since the case where the preview mode is designated is taken as an example, the document generated by inserting the content into the template is displayed on the display 144. However, when the print mode is designated, the document is printed out instead of the preview display. Each process of the flowchart in the present application is executed by the processor 135 in the information processing apparatus (host computer).

  In FIG. 7, the layout editing application 121 first recognizes that the preview mode has been selected (step 0701). In the operation mode by the automatic layout system of the present embodiment, containers are created and associated with each other, a layout setting mode for creating a document template defining the layout, and a record is inserted into the created layout (template) Then, a preview mode for previewing the layout result after the record is actually inserted is included.

  In this preview mode, the actual record is inserted and the layout is calculated. The preview mode is a layout calculation on the display. Even when printing is actually performed, the layout is calculated by inserting a record, and the calculation method is the same as that in the preview mode.

  When the preview mode is set, the layout editing application 121 recognizes that the record to be previewed has been selected (step 0702). The record may be selected by selecting a record designated by the operator, or by sequentially selecting records from a designated database. When the record is selected, the layout editing application 121 performs calculation for laying out the record according to the template (step 0703), and if the flow area is included in the template, the flow area includes data according to the sub-template. Arrange (step S0704). The layout editing application 121 lays out the record according to the calculation result of steps 0703 and S0704, displays it (step 0705), and determines whether or not to preview other records (step 0706). This determination may be based on an instruction from the operator, or it may be determined whether the preview for a predesignated range has been completed. If the layout editing application 121 determines in step 0706 that there is no need to preview another record, it ends the preview mode (step 0707).

  On the other hand, when previewing another record, the layout editing application 121 selects another record, performs layout calculation again, lays out the record, and previews the record (step 0708). At the time of printing instead of the preview mode, the layout is calculated in order for all the records to be printed. Therefore, steps 0701 and 0707 do not exist. In step 0706, it is determined whether printing has been completed for all records to be printed.

(Layout calculation procedure)
FIG. 7B is a flowchart showing details of layout calculation in step 0703 of FIG. 7A. FIG. 8 is a diagram showing a UI display example at that time. Note that the flowchart described in this embodiment is not limited to FIG. 7B, and is executed by the computer of FIG. 1A, FIG. 1B, or FIG.

  First, the layout editing application 121 obtains a set of containers for calculating a layout (step 0710). The layout calculation is performed as a set of containers associated by links. For example, referring to FIG. 32, four containers are laid out on the page, and an association is set for each container. In this case, container A and container B, and container C and container D are associated by a link. Therefore, container A and container B are set 1, and container C and container D are set 2. That is, with reference to the link information 2304 of the template data shown in FIG. 23, the container group associated by the link can be determined as one container set.

  Next, from the set of containers obtained in step 0710, the layout editing application 121 selects one set of containers for calculating the layout (step 0711). For example, the order of appearance in the link information of the template data may be followed. Then, the layout editing application 121 calculates a layout for the selected set of containers. Here, the layout is optimized so that the size of the container to be laid out is as small as possible with the actual content size (step 0712).

  Layout optimization is such that the size of the content inserted into each associated container is as large as possible in the associated containers so that the size can be changed dynamically. To be done. When the container size is fixed, the content is scaled and stored in the container, or a part of the content is stored in the container. Even when three or more containers are included in the container set, the container size corresponding to the size of each content (that is, the length of each variable side) is calculated, and the distance defined by the link information from the midpoint is calculated. The position is determined as the position of the side. For a container whose linked side is a fixed side, its position is moved according to the movement of the side of the associated container.

  As described above, a set of containers linked by a link is determined, and the size of a variable size container is determined, and the position of a variable position container is determined.

  The layout optimization calculation is performed as described above, and if the calculation result violates the rule, the layout editing application 121 calculates again so as not to violate the rule (step 0713). Here, the rules are restrictions set by the user at the time of template creation, such as the size and position of the container, the length of the link, and the like. The restriction is defined by attribute information such as sides and points included in the container information in the template data and link information. In particular, items having a “fixed” value in the attribute information and link information are restrictions on the layout. Therefore, after the layout calculation in step 0712 is completed, items such as sides, point positions, and sizes of the calculated containers having the attribute “fixed” are compared with the container information in the template data, and the values are different. If there is any item, it is judged as a constraint violation. Also, regarding links, if the link length (distance between containers) included in the link information is different from the distance between containers in which the link after the layout calculation in step 0712 is set, it is a constraint violation. Determined.

  Once the layout is calculated so that it does not violate the rules, the layout of the container set is completed. Then, the layout editing application 121 performs steps 0711 to 0713 for a set of all containers on the page, and calculates the layout of the entire page (step 0714).

  When the flow area information is included in the template data, it is necessary to perform layout of the sub-template in the flow area in the layout calculation in step 704. This process will be described with reference to FIG. 10, FIG. 14, FIG. These figures are processing in the template creation mode instead of the preview mode, but the preview display is also performed in the template creation mode, and the preview display processing is the same.

  FIGS. 8A to 8C are UI examples at the time of layout calculation. FIG. 8A shows a state in which a certain record is inserted and a layout is determined. Reference numerals 0801 and 0802 denote fixed sides, 0803 denotes a variable side, 0804 and 0805 denote arrows indicating change directions of the variable side, and 0806 denotes a link. In this state, the record is changed and contents of different sizes are inserted. FIG. 8B shows the new content size superimposed on the state of FIG. 0807 represents the size of the content inserted into each container. Then, layout calculation is performed. FIG. 8C shows the result of layout calculation. The size of each container after the calculation is calculated so that there is a difference equivalent to the size of the content that is actually inserted, and is calculated so as not to violate the rules described above. As shown in FIG. 8C, the inserted content size 0807 shown in FIG. 8B and the calculated content size 0808 are equivalent to each other.

  However, if the container size is simply changed with the same difference, there is no problem in the case of the layout calculation only in the horizontal direction as shown in FIG. 8, but the layout calculation considering the vertical direction and the horizontal direction as shown in FIG. 33 is performed. If it must be done, it may not be possible. In the case of FIG. 33 that handles a two-dimensional layout in the horizontal direction and the vertical direction, adjustment is first made in the horizontal direction and then in the vertical direction using the layout calculation method of FIG. That is, the layout adjustment is performed between the containers 3301 and 3302 so as to be within the set value D in the above-described procedure, and then the layout adjustment is performed between the containers 3302 and 3303 so as to be within the setting G. However, with the adjustment method in which adjustment is performed in the horizontal direction and then in the vertical direction, a layout result deviating from the basic layout desired by the user is assumed.

  Therefore, for each container, the difference between the square of the width of the basic pattern and the width after layout adjustment, and the difference between the height of the basic pattern and the height after layout adjustment, so as not to deviate from the basic pattern (aspect ratio) as much as possible. The sum with the square is calculated and calculated for all containers. The layout editing application 121 may perform layout adjustment by calculating the width and height of each container so that the total sum of the squares of the containers is minimized.

  By performing layout adjustment using this least square method, the final layout which is balanced as a whole can be determined without greatly deviating from the basic layout initially set by the user. Since a variable link described later is set between the containers, the link size is changed as described later according to the size of the content data to be inserted. By providing such a layout adjustment unit, the layout editing application described in the present application can adjust the arrangement positions of a plurality of partial display areas (containers) according to the allocated data size.

<Multi-record (multi-data) function>
An outline of multi-record will be described. In a normal document template, one record corresponds to one document, but in the multi-record corresponding to the sub template, records until a break (separation) in which a reference item is changed are poured. Therefore, a plurality of records are included in one document. Therefore, it is desirable that the variable data database corresponding to the normal document template and the variable data multi-record database corresponding to the sub-template are different from each other.

  FIG. 9 is a diagram showing an example of an outline of a multi-record and its layout method. Reference numeral 0901 denotes a document, 0902 denotes a page, 0903 denotes a sub template, and 0904 denotes a database. Looking at the database indicated by 0904, data Nos. 1 to 7 are displayed. In the variable print of one record and one document, there are seven records. In this case, seven documents are created. However, in the variable print that supports multiple records of multiple records and one document, the following processing is performed. First, the user arbitrarily specifies a column for specifying a multi-record. The designation is made, for example, when creating a template. Information for specifying the designated field is stored as a part of the multi-record information 2404 in FIG. In this example, it is assumed that the field name: Name is specified. Then, a record having the same value in the designated field is determined to be a record laid out in one document, and this is also designated as a separately designated sub template (stored in the sub template information in FIG. 24). Used and laid out in one flow area. In the example of FIG. 9, the records of No. 1 to No. 4 have the field Name value “Tom”, so they are poured into one flow area and laid out on one document. The records of Nos. 5 to 7 are laid out on a different document using the same template as “Tom” because the value of the field Name is “Nancy”. That is, once the document “Tom” is completed, a document “Nancy” is created. In this way, a new document is created in accordance with the change of the data in the designated column.

  Specifically, for example, according to the setting in the template data, a page break is made after adding a footer or the like (not shown) to the “Tom” document. This completes the document “Tom”. Next, using the same template data as before, a “Nancy” document header or the like is added to a new page (not shown). Then, using the sub-template that is also set as the sub-template information in the flow area defined in the template, the record having the value of the NAME field “Tom” is laid out and poured into the flow area. This is a normal multi-record.

  However, in the present embodiment, the same template data is used for Nancy and Tom, but the same sub-template is not necessarily used for each record. This is because a sub-template corresponding to a separately specified condition can be used.

<Overall flow of template creation mode processing>
10 and 11 show a processing flow of the template creation mode by the layout editing system according to the present invention and a description UI thereof. Each step of the flow of FIG. 10 will be described with reference to the UI diagram of FIG. When the layout editing application 121 is executed and the user inputs an instruction to create a new template, the screen shown in FIG. 11 (except for the rectangles 1104, 1106, and 1105) is displayed. The procedure of FIG. 10 is a procedure of the layout editing application that is executed in accordance with a user instruction from the state.

  First, when the layout editing application 121 recognizes that the icon 1103 in FIG. 11 has been pressed, the layout editing application 121 shifts to the flow area creation mode (S1001). In the page margin area 1102, a rectangle created by dragging the user's mouse. Is drawn as a flow area (S1002). The layout editing application 121 stores the position and size of the drawn rectangle in the memory unit 136 as a part of the template data as the position and size of the flow area 1106 (S1003). Containers 1104 and 1105 are text containers and image containers defined outside the flow area 1106. These containers are not related to the processing of flowing content into the flow area, but can be provided as headers and footers, for example. These containers are also stored in the memory unit 136 with their input position and size as part of the template data. The flow area 1106 makes the user easily recognizable visually by making the rectangular UI such as color and line type different from those containers.

  Next, the layout editing application 121 associates a multi-record field with the created flow area (S1004). This is a process of inputting an identifier such as a database name associated with the flow area and a field name in each record. In operation, for example, a target flow area is specified by clicking a flow area, and the necessary information is input in accordance with a certain operation flow. The information is stored in the memory unit 136 as multi-record information of the template data shown in FIG. This can be input simultaneously with the properties in steps S1006 and S1007.

  Next, the layout editing application 121 determines whether to make various settings for the created flow area (S1005). If the property is set, the layout editing application 121 displays a property dialog by recognizing that the mouse pointer is clicked in the flow area (S1006). The layout editing application recognizes and sets the content set using the displayed property dialog (S1007). The property dialog and setting method will be described in detail later. Various set information is held in the memory unit 136. When the creation and setting of the flow area is completed, the layout editing application 121 confirms whether or not to preview the layout (S1008), and if previewing, transitions to the preview mode and performs layout calculation (S1009). This layout calculation performs the same processing as the flow shown in FIG. 7B.

  Next, the layout editing application 121 performs layout calculation for the set flow area (S1010). This process will be described later in detail with reference to FIG. Finally, the layout result is displayed (S1011). Steps S1009, S1010, and S1011 correspond to steps S0703, S0704, and S0705 in FIG. 7A.

(Flow area property settings)
FIG. 12 shows an example of a setting dialog for performing various settings (property settings) of the flow area. This is a UI example of a dialog displayed in step 1006 in the flowchart of FIG. 10 and reflecting the content in step S1007. Note that sub-templates and conditional expressions in the sentence will be described after the flowchart.

  First, the user selects whether a sub-template or a conditional expression is associated with a flow area by using a radio button 1202. Thereafter, when sub-template association is selected, the user designates a sub-template to be used in the flow area from the list box 1203. Alternatively, when the association of the conditional expression is selected, the user specifies a conditional expression to be used in the flow area from the list box 1204. The sub template and the conditional expression can be separately created by each unique UI means in the document template being edited or in a predetermined place even outside the template. In addition, the conditional expression can be created by a UI shown in FIG. However, as another method, the file is saved in a separate file, and can be selected and specified by specifying the file from this setting dialog. In this embodiment, a plurality of sub-templates and conditional expressions can be created for each flow area in the document template. However, from the viewpoint of selecting from the list box, each is designed to have a unique name for identification. It should be. In addition, from this setting dialog, the flow direction (that is, the direction in which contents are arranged) when the sub template is poured into the flow area is selected from the selection column 1205. The content interval can be set in the setting field 1206 in the vertical direction and in the setting field 1207 in the horizontal direction.

  To confirm the above settings, an OK button 1208 is pressed. When the OK button is pressed, the setting at that time is stored in the memory unit 136 as the flow area information 2401 in FIG. For example, flag information indicating whether the target flow area is associated with a sub template or a conditional expression, a sub template name or a conditional expression name (name of a conditional expression file) according to the flag information, a flow direction, and an interval Is stored as sub-template information 2403 and attribute information 2402. When a cancel button 1209 is pressed, all the specified settings are canceled and are not saved.

(Sub template layout example)
An outline of the sub-template described above will be described. FIG. 13 shows a layout example of a sub template (that is, an example in which data is laid out using a sub template. The same applies hereinafter). The sub-template refers to data stored as a template in a state where an arbitrary number of image containers and text containers are arranged and which data (field) of a record is assigned to the container. This is useful if you use the same layout many times in one document. The containers arranged in the sub-template are the same as the image container and the text container, and a link can be set between the containers. Therefore, the layout size can be optimally changed by applying the layout calculation method described in FIG. 7B to the containers arranged in the sub-template.

  FIG. 13 shows a layout example of the sub-template. Reference numerals 1302 and 1305 denote image containers, 1303 and 1306 denote text containers, and 1307 denotes a link.

  In FIG. 13, since the image and text content sizes poured into the containers arranged in the sub-templates 1301 and 1302 are different, the optimal layout is calculated for each record and the layout is changed. Therefore, even though the same subtemplate is used, the subtemplates 1301 and 1302 have different layouts with different positions and sizes of containers (partial display areas). As a layout method in the sub-template, layout adjustment is performed using the above-described process of FIG.

(Sub template conditional expression)
The sub template conditional expression can selectively assign a plurality of types of sub templates to one flow area. Since the conditional expression is also an expression for extracting content that matches the condition from the database, it is also referred to as an extraction condition in the present application, and a template having a flow area in which the conditional expression (extraction condition) is set is created. It becomes. In addition, any one of the sub template and the conditional expression can be associated with the flow area. If the sub template is associated with the flow area, the acquired record is poured into the associated sub template. Note that a conditional expression may be set when associating the sub-template, and only records that match the conditional expression may be poured into the sub-template associated with the flow area.

  In addition, the conditional expression includes identification information of a sub template applied when the condition is met. FIG. 15 shows an example of a UI for setting a conditional expression. Records that conform to the conditional expression set in the flow area are associated with the sub-template associated with the conditional expression and flowed into the container. Then, the sub template into which the record is poured is arranged in the flow area.

  This input area has at least a text box 1502 for naming a conditional expression and a pair of IF statement 1503 and ELSE statement 1504 which are elements constituting the most basic condition determination. In the input area of the IF statement, a list box 1505 for selecting a field for which a condition is determined, a list box 1506 for setting a logical expression for determination, a text box 1507 for inputting a value used for determination, and condition determination A THEN_USE processing statement 1508 that determines the sub-template for inserting the record that determines the operation when the result is positive, and also determines the sub-template for inserting the record when the condition determination result is invalid ELSE_USE processing statement 1504. The determination logical expression 1506 includes “Equal (equal)”, “NOT_EQUAL (not equal)”, “LESS_THAN (small)”, “LARGER_THAN (large)”, “START_WITH (starts with)”, “END_WITH (ends) ) "And so on.

  Further, in order to set a complicated conditional expression, an AND / OR connection statement combo box 1509 is provided to set a compound condition in the IF statement. When an AND or OR compound condition is selected in this combo box, one condition line is added to the IF statement. In the case of AND, it is determined that the IF statement determination is true only when a plurality of conditions are all positive, and in the case of OR, when any of the conditions is positive. In order to set a more complicated conditional branch, an ELSE_IF statement addition button 1510 is provided. When the button 1510 is pressed, an ELSE_IF statement is newly inserted between the IF statement and the ELSE statement. The contents and operation of the ELSE_IF statement are the same as those in the IF statement. When the IF statement is invalid, the next lower ELSE_IF statement is determined, and when the IF statement is further incorrect, the next lower ELSE_IF statement is determined, followed by the final determination of the ELSE statement. Reference numeral 1511 denotes a delete button for deleting the selected ELSE_IF statement. When the number of ELSE_IF statements increases, a list of conditions can be displayed using the scroll bar 1512. If it is determined to be true by any IF statement or ELSE_IF statement, the USE processing statement is executed. The sub template name is input (selected) to the USE processing statement. In this way, sub-templates that meet the conditions can be automatically selected for each record that has various values through the conditional expression, and various layouts can be realized in one conditional expression. . By associating this conditional expression with a flow area, a plurality of types of sub-templates having various layouts can be arranged in the flow area in one flow area.

  When the user inputs the condition, the user finally presses an OK button 1514. When the OK button 1514 is pressed, information indicating the sub template condition set in the UI is stored in the memory unit 136 as a part of the sub template information 2403. This sub-template conditional expression may be any information that can specify the sub-template when the conditions and conditions are satisfied, such as a text file in which the (selected) text described in the UI of FIG. 15 is stored as it is. . In the example of FIG. 15, “IF field01 EQUAL value01 AND field02 EQUAL vlue02 THEN USE subtemplate01 ELSEE IF field01 EQUAL value03 AND field02 EQUAL vlue04 THEN USE subtemplate02 ELSE USE subtemplate03” is stored as information indicating the subtemplate conditional expression. Even if the data is stored as it is, it is described in a simple grammar and is input from the UI as shown in FIG. 15, so there is no room for grammatical errors. Therefore, a suitable sub-template can be determined by parsing the description of the conditions with a simple program.

  In this way, the conditional expression holds the condition for extracting content data for layout from the database and the sub template used when the condition is met. Therefore, the extracted content data is held in the memory unit 136 as association information indicating which sub-template should be arranged. In addition, since it is possible to set a plurality of conditional expressions as described above, each of the extracted content data has a sub template associated therewith, and therefore, a plurality of types of sub data in which each content data is arranged. The template is laid out in the flow area.

<Flow area layout method>
FIG. 17 shows a flow of layout calculation in the flow area by the layout editing application program 121. The procedure in FIG. 17 is executed in step S1010 in FIG. 10 and step S0704 in FIG. 7A. Here, a description will be given when one flow area is set. For a template in which a plurality of flow areas are set, the steps S1701 to S1715 may be repeated for each flow area.

First, the layout editing application program 121 obtains data for layout from the database associated with the flow area (S1701), and substitutes the number of records to be laid out for n (S1702). Specifically, the number of records to be acquired can be recognized by communicating with a database including records for layout by a user interface which is one of the modules constituting the layout editing application.
If the number of records to be laid out is 0, there is no need to perform layout processing, so the processing ends without performing processing (1703). Next, the layout editing application 121 assigns 1 to a variable k for checking the record in order to check from the first record (S1704). Also, 0 is substituted into a variable Num that substitutes the number of sub-templates to be laid out (S1705). The layout editing application 121 reads the data of the kth record from the database (S1706). Note that the content data of the read record is temporarily held in the memory unit 136.

  Next, the layout editing application 121 refers to the flow area information 2401 regarding the target flow area, and determines whether the sub template is associated or the conditional expression is associated (S1707). When the conditional expression is associated, the layout editing application 121 lays out the kth record according to the sub-template based on the flowchart of FIG. 16A described later (S1708). In the procedure of FIG. 16A, when a sub template is associated with the flow area, the sub template information is read. When the conditional expression is associated, the conditional expression is evaluated in step 1708, and the sub template obtained as a result is obtained. , And the layout for the kth record is performed according to the read sub-template. On the other hand, if it is determined that the conditional expression is not associated with the flow area, the k-th record is laid out according to the sub-template associated with the flow area based on the flowchart of FIG. 14 (S1709). Data laid out in accordance with the sub-template in steps S1708 and S1709 is stored in the memory unit 136 until it is poured into the flow area. What is saved is the relative positional relationship and size of each container after the content is poured, and the contents of the container obtained as a result of the layout calculation. For example, an appropriate coordinate origin is determined on the sub-template, and the container position and size information indicating the position and size of each container in the coordinate system is stored. In addition, for the contents to be stored in the container, the position and information indicating the data arranged at the position are stored in the same coordinate system. These are referred to as laid-out sub template information.

  When the layout of the sub-template is finished, the layout editing application 121 increases the variable Num by 1 (S1710), and increases the variable k by 1 in order to proceed to the next data (S1711). The layout editing application 121 compares the number n of data to be recorded with k (S1712). If k is less than n, the process proceeds to step S1706, and the process is repeated for the k-th data. If k is greater than or equal to n, the layout of the sub-template ends, and the process proceeds to the process of laying out the sub-template laid out in the flow area.

  In order to lay out the sub template in the flow area, the layout editing application 121 acquires the size of the flow area from the flow area information 2401 (S1713), and acquires the size of the sub template to be laid out (S1714). Specifically, a sub template in which content data is to be arranged is specified according to the flowchart of FIG. 16 to be described later, and the execution result of the layout optimization process in the sub template is held in the memory unit 136. Can be obtained. In the present embodiment, the size of the outer frame of the sub template is determined by the size of the container in the sub template. In other words, the size after layout of the sub template changes depending on the contents of the record by the free layout processing in the sub template. Since the layout result by the record poured into the sub template is held in the memory unit 136 as described above, the layout editing application 121 can acquire the size of the sub template to be laid out. Note that, depending on the user, there may be a case where the outer frame size of the sub template is desired to be constant. Therefore, the outer frame size of the sub template may be fixed or variable by a predetermined process. Absent.

  The layout editing application arranges the laid out sub template in which the content data is laid out in the flow area while applying the flow direction and the flow interval set in the flow area information 2401 (S1715). The flow direction is a sub-template arrangement method, and the flow interval indicates an interval between sub-templates. Here, what is arranged in the flow area is the sub-template information that has been laid out saved in steps S1708 and S1709. Specifically, in step S1715, the container position and size defined in the relative coordinate system in the laid out sub-template and the content position and content are converted to the flow area coordinate system. At this time, if there is a layout template that does not fit in the flow area, it is necessary to perform reduction conversion on the size of the sub-template. It should be noted that if it is not desired to perform sub-template reduction conversion, it can be handled by a page repetition function described later.

(Sub template layout (no conditional expression))
Sub-template in step S1709 The flow of this layout process is as shown in FIG. In FIG. 14, the layout editing application first acquires data for layout from the database (S1401). The size of the content data to be laid out in each container in the sub template is acquired (S1402). Specifically, as described above, the user interface, which is one of the modules constituting the layout editing application 121, performs the association process with the database, so that the data in the database can be referred to. The size and the like can be acquired by interpretation. Note that steps S1401 and S1402 may be performed simultaneously. In the process of S1402, the layout editing application 121 can acquire the size of the content data by analyzing the data information acquired in S1401. Note that the size of the acquired content data is held in the memory unit 136.

  The layout editing application performs layout calculation for each container based on the data size acquired in S1402 (S1403), and optimizes the layout (S1404). The optimization method is executed using the processing of FIG. 7A as described above.

  The layout editing application 121 determines the layout optimized in S1404 (S1405), flows data to be laid out (S1406), and displays it (S1407). Note that the layout determined in S1405 is temporarily held in the memory unit. If the display in S1407 is performed collectively when the document is completed, step S1407 is not necessary.

(Sub template layout (with conditional expression))
FIGS. 16A and 16B show sub-templates for performing condition determination from a database record and inserting a record when a conditional expression is set in the flow area in step S1708 of FIG. It is a flowchart of the process to select.

  In FIG. 16A, the layout editing application 121 first acquires data for layout from the database (S1601).

  Next, the layout editing application 121 determines a sub template for laying out data (S1602). If the content data of the currently targeted record does not match the conditions set in the flow area, the next record is targeted without laying out the targeted record. That is, a record having content data that matches the conditional expression is handled as a layout target record. The details will be described with reference to FIG.

  Next, the layout editing application 121 passes the size of data to be laid out to each container (S1603). Specifically, the layout editing application can recognize the size of data to be laid out by analyzing the data acquired in S1601, and the processing of S1603 is realized by associating the size of the data with each container.

  The layout editing application 121 calculates the layout in each container based on the data size passed in S1603 (S1604), and optimizes the layout (S1605). As described above, the optimization method is adjusted according to the size of the content data.

  The layout editing application 121 determines an optimized layout (S1606), flows data to be laid out (S1607), and lays out and displays it in the flow area (S1608). Note that step S1608 is unnecessary if the display is performed collectively when the document is completed.

  FIG. 16B is a flowchart describing details of the process S1602 for determining the sub-template in FIG.

  The layout editing application 121 reads the sub template conditional expression file based on the flow area information 2401 of the flow area of interest, extracts the first IF sentence of the conditional expression (S1611), and determines the IF sentence from the record received in step S1601. The value of the current field is extracted (S1612). Note that the field value of each record acquired from the database may be acquired by communicating with the database, and the layout editing application stores the value of the field of each record in the memory unit 136 so that the memory editing unit 136 The field value may be extracted with reference to FIG.

The layout editing application 121 determines whether or not the value of each field extracted in S1612 matches the condition extracted in S1611 (S1613). That is, since the conditional expression is held in the memory unit 136, the layout editing application 121 can evaluate with a specific field value by referring to the memory unit, and the determination process described in S1613 can be performed.
When the layout editing application 121 determines that the conditional expression set in the flow area matches the value of the field extracted as the determination target, that is, when the evaluation result is true, the USE processing corresponding to the condition is performed. The selected sub template name is stored in the memory unit 136 (sub template information 2403) (S1614). By this process, a sub-template for arranging content data included in a record that is currently targeted and determined to match the conditional expression is associated and held. This associated information is also held in the memory unit as one of the above-described association information.

  If the layout editing application 121 determines that there is no match in S1613, it determines whether there is another IF statement (S1615). If there is, the process proceeds to S1611 in order to continue the IF statement determination. Finally, for a record that does not match any IF statement, the USE processing of the ELSE statement is selected, and the corresponding subtemplate name is stored (S1616).

  Note that in the process of FIG. 16B, due to the presence of S1616, records that do not meet the conditions are also poured into the sub-template. However, if the sub template to be used in the ELSE statement is not specified, records that do not meet the conditions may not be flown into the sub template. In other words, by not designating a sub template to be used in the case of ELSE, it is possible to narrow records to be flowed into the sub template to those that match the conditional expression set in the flow area.

  As a result of the above processing, when a conditional expression that uses a plurality of types of sub-templates is set, a plurality of types of laid-out sub-templates are arranged in the flow area. Furthermore, depending on the conditional expression, it is possible to switch whether all the acquired records are poured into the sub template or only the records that match the conditional expression are poured into the sub template.

  FIG. 18A shows an example in which sub-templates are laid out in the flow area. In FIG. 18A, 1801 is a page margin, 1802 and 1803 are fixed containers, 1804 is a flow area, and 1805 is a sub-template. Reference numeral 1806 denotes a horizontal flow interval, and 1807 denotes a vertical flow interval. Four sub-templates are laid out in the flow area, and each is arranged with an appropriate flow interval set in the flow area setting dialog starting from the upper left of the flow area.

  Each sub template used in the flow area is obtained as a result of a conditional expression, and the detailed layout design in the sub template is different in the size of the content data included in the flowed records, so the layout results also vary. is there.

  FIG. 18B shows a state in which a flow in the flow area is performed by various sub-templates obtained based on such a conditional expression. Reference numeral 1804 denotes a flow area, in which a detailed layout of the sub-template represented by 1805 is described. Thus, the size of the flow area is fixed no matter how many sub-templates are laid out. If there is a layout size of the sub template that extends beyond the size of the flow area, the portion that protrudes from the flow area is clipped and not displayed. Finally, the layout result is displayed and the process ends (S1716).

  If it is determined that the sub template protrudes from the flow area, it is possible to reduce the sub template so that the sub template fits in the flow area. Accordingly, when it is determined that the sub-template protrudes from the flow area, a dialog for designating whether to perform clipping processing or reduction processing may be displayed. FIG. 18B shows a state in which four types of laid out sub-templates are arranged according to the conditional expression.

  According to the above procedure, a desired sub-template can be designated for the arrangement of the record according to the value of the desired field of the record arranged in the flow area. For this reason, the degree of freedom of layout of objects in the document is increased, and a higher quality document can be created.

  In addition, depending on the conditional expression set for the flow area, it is possible to set whether to record all records or only records that conform to the conditional expression, and it is possible to easily create a layout desired by the user. It becomes possible.

  A specific example is shown in FIG. In the template 2502a in which the flow area shown in FIG. 25A is defined, a conditional expression 2501 is associated with the flow area and stored as sub-template information 2403. According to the conditional expression 2501, if the field data A is 1, the sub template 2503 is included in the record. If the field data A is 2, the sub template 2504 is included in the record. In this case, the sub template 2504 is used. The layout target database includes records 2506 and 2507.

  Here, as shown in FIG. 25B, the record 2506 is first fetched. In this case, the conditional expression “field data A = 1” is first evaluated for this record according to the procedure of FIGS. 17 and 16, and “field data A = 2” is evaluated next because it is not true. Eventually, this condition is not true either, so the record 2506 is laid out using the sub template 2505 by the USE statement in that case. This is a layout example 2502b. However, in the procedure of FIG. 17, since the sub template is poured into the flow area after all the records are laid out, the preview display as shown in FIG. 25B is not performed.

  Next, a record 2507 is fetched. In this case, since the conditional expression “field data A = 1” is true, the record 2507 is laid out using the sub template 2503 by the USE statement in that case.

  As described above, since the determination processing of the records 2506 and 2507 is completed and the sub-template to be inserted is determined, each content data actually included in the record is laid out by adjusting the layout in each associated container in the sub-template. 2502c is obtained. In this way, different sub-templates can be used for each record based on the conditional expression set by the user.

[Second Embodiment]
Conventionally, the flow area is limited to a range of one page, and the purpose is to realize a layout result corresponding to a document with a limited page space, such as a postcard, by performing a process of placing a sub-template within a range of one page. It was. Therefore, it is not considered to lay out the sub template over a large number of pages. However, the need to create a customized document for each customer, there is a situation where the number of pages is not limited, and a document with a flexible number of pages is created according to the range of customer interest To do.

  In the second embodiment of the present invention, when the sub template is laid out in the flow area, when the sub template overflows out of the area, a new page having the flow area is automatically generated, and the sub template overflowed there An automatic layout system including a method for continuously laying out the images will be described. Such a function is called a repeated page function.

  The advantage of this method is that if one flow area is defined, all records in the database associated with the flow area can be laid out according to the definition of the flow area, and can be collected as one document. In addition, description is abbreviate | omitted about the part (drawing and its description) which is common in 1st Embodiment.

<Repeated page in multiple pages>
FIG. 19 shows an example of a setting dialog UI that is called when a flow area is inserted in a template creation mode for a document having a plurality of pages. The flow area ON / OFF is selected from the radio button 1902. When the flow area is ON, a page number in which the flow area is arranged is set in the text box 1903. Here, the input is limited by the UI so that the start page is 1 or more and the end page is less than or equal to the maximum page of the document.

  Further, in a text box 1904, a repeated page range in which repeated instances are generated from the arranged flow areas and the sub-template flows is set. The repeated page will be described later. Here, the input is limited by the UI so that the start page of the repeated page is equal to or more than the start page of the flow area, and the end page is equal to or less than the end page of the flow area. Further, at least one page is always limited to be a repeated page. This is because the header and footer that are not suitable for repetition may be included in the beginning and end of the document.

  That is, the page from the start page of the flow area to the page before the start page in the repeated page setting is a page that is not repeated. Further, the page after the end page in the setting of the repeat page to the end page of the flow area is not repeated.

  When OK is pressed in the setting dialog, a flow area is inserted into each page in accordance with the set page range, and these pieces of information are stored in the memory unit 136 as template information covering a plurality of pages collectively.

  In order to make a group, for example, group identification information can be included in the template information so that it can be handled as a group. The flow area repetition flag indicating the set radio button 1902 and various page settings are stored in the memory unit 136 as part of the flow area information 2401 for each page. However, except for the position of the flow area, other attribute information, sub template information, and multi-record information are the same for each page. Thus, for information other than the position of the flow area, for the templates belonging to the same group, for example, the information set for the first page is referred to.

<Flow area position control>
A flow area arranged over a plurality of pages can occupy each position and size in each page. FIG. 20 shows an example UI for adjusting the position and size of the flow area in each page. As described above, 2001 is a margin area, and the 2004 flow area itself is displayed in an easy-to-understand manner in a different expression from a normal container depending on the line type and color. However, as shown in FIG. The size can be changed by a size change handle 2003 which is well known and generally used in graphic drawing software. In the flow area, it is appropriate to limit the possible area within the margin area. When the flow area size is changed, the changed size is stored in the memory unit 136 as flow area information.

<Repeated page>
FIG. 21 is a conceptual diagram illustrating a state in which a flow area is arranged over a plurality of pages in one document and a state in which a layout-completed page is generated when actual data is inserted into the flow area.

  In FIG. 21A, reference numeral 2102 denotes a repeated page. Although 2101 and 2103 are not repeated pages, they are pages where a flow area exists. Reference numeral 2104 denotes a flow area. That is, the template of FIG. 21A is configured according to the example shown in FIG. Reference numerals 2105 and 2106 denote ordinary containers. These normal containers are not related to the flow area. A normal container stores contents associated therewith and is not a target of multi-record processing.

  The flow area 2104 extends over a plurality of pages, but is handled by the layout processing application as one continuous area. That is, except for the position and size of the flow area, other flow area information is commonly referred to. That is, when the flow area is designated to be repeated, the user needs to define a template of a plurality of pages according to the designated page. At this time, all attributes other than the position of the flow area are common.

  With this configuration, when actual data is inserted, all records in the database are arranged using the entire flow area extending over three pages 2101 to 2103 in this figure.

  FIG. 21B shows a state in which actual data is inserted into the flow area set as shown in FIG. 2107 represents one type of sub-template. However, for the sake of simplicity, the details of the sub-templates and containers that are actually flowed are omitted. FIG. 21B shows that the second page 2102 in FIG. 21A designated as a repeated page is automatically generated and repeated according to the number of records. That is, 21 records are supposed to flow in the flow area in FIG. 21, but only the flow area of page 2101 to page 2103 shown in FIG. Since all the records cannot be stored, 2102 designated as a repeated page is automatically generated until all the records are arranged in the flow area.

  In this embodiment, the case where the repeated page is designated in advance has been described. However, the repeated page may be automatically designated. In that case, as an example, a page having the largest area of the flow area may be considered as a repeated page. This is because it is possible to prevent unnecessary pages from being repeatedly generated by designating the page where the most sub-templates are arranged (that is, the page having the largest flow area) as the repeated page. Because.

  When a flow area exists across a plurality of pages as described above, it is effective in improving the expressiveness of the document if it is possible to set which page is repeatedly set according to the nature of the page. In the example of FIG. 21, for example, the flow area of the first page may include a customer name in a normal container part and a greeting to the customer. After that, the multi-record record data is displayed in the flow area, and after processing a large number of record data on the repeated page, the sales person's name is entered in the flow area on the third page, and a closing greeting can be posted. Conceivable. In this way, it is possible to give diversity to the contents of a plurality of pages, while taking the form of a document in which many similar record data are arranged.

<Flow of layout processing>
FIG. 22 is a flowchart when the laid-out content is poured into the flow area according to the second embodiment of the present invention. The process of FIG. 22 is executed as step S1715 of FIG. 17 in the first embodiment. This flowchart describes a method of arranging a sub template in a flow area composed of a plurality of pages.

  First, the layout editing application 121 acquires the number of sub-templates to be arranged in the flow area and substitutes it for n (S2001). This number is the value k or n determined in step S1712 of FIG. If n is 0 (S2002), there is no need to lay out in the flow area, so the process is terminated (S2003). Details of the processing up to this point have been described above, and will be omitted.

  Next, the layout editing application 121 initializes a variable k to 1 (S2204). Information on whether there is a page with a flow area that is not a repeated page is obtained at the beginning of the document, and if there is, template information corresponding to a non-repeated page at the beginning of the document is read from the template data. The layout editing application 121 substitutes s for the start page that is not the repeated page, and e for the end page, that is, the page immediately before the repeated page (S2205). This information is read from the flow area information stored in the memory unit 136 by user input through the UI of FIG.

  Next, the layout editing application 121 sequentially flows sub-templates that fit within the page of interest (pages s to e) in order from the top in pages s to e in accordance with the flow area information of the read template. In step S2206, when the flow ends, the number of sub-templates contained in the pages s to e is obtained and set as t (S2207). At this time, the layout editing application 121 substitutes t for k (S2208), and compares k and n (S2209). Note that the value of k is temporarily stored in the memory unit 136. If k is less than n, all sub-templates are not arranged in the flow area, and the process advances to step S2210. If k has reached n, all the sub-templates have been flowed, and the process ends.

  The layout editing application 121 first temporarily stores the current number of laid-out pages p in the memory unit 136 (S2210). Next, the layout editing application 121 reads template information corresponding to a portion that is not repeated at the end of the document from the template data. The page number (the last page from the page immediately after specified in the repeated page range) in the flow area that is not a repeated page is acquired from the tail of the document, and the start page is substituted for s and the end page is substituted for e (S2211). These pieces of information are also read from the flow area information stored in the memory unit 136 by user input through the UI of FIG.

  The layout editing application 121 sequentially flows the sub-templates that can be accommodated in order from the top in accordance with the flow area information of the read template on the pages s to e (S2212), and when the flow processing ends, the pages s to e. The number of sub-templates that fall within is acquired as t (S2213). Next, the layout editing application 121 compares k + t with n (S2214). Since the value of k is temporarily stored in the memory unit 136 as described above, the layout editing application 121 can recognize the value of k. If k + t is less than n, the process advances to step S2215. If k + t has reached n, it means that all the sub-templates have been flowed without using repeated pages, and the process is terminated.

  If the processing of the flowchart shown in FIG. 22 does not end even after the processing up to S2214 is completed, a record to be laid out even if a page that is not the first repeated page and a page that is not the last repeated page are combined (layout-sub template) Is not fit.

  Therefore, the layout editing application 121 discards the instance (layout data) of the laid out page after p that has flowed in step S2212 (S2215). In other words, the processing of S2215 is performed to flow the laid-out instance after p that has flowed in S2212 to the repeated page (from the page immediately after being specified in the repeated page range to the last page).

  The layout editing application 121 reads template information corresponding to the repeated page portion from the memory unit 136. Then, the page number of the repetitive flow area in the document is acquired, and the start page is s and the end page is e (S2216). These pieces of information are also obtained from the flow area information 2401 held in the memory unit 136.

  The layout editing application 121 flows as many sub-templates (layout instances) as can fit in the flow area of the repeated pages s to e (S2217). The layout editing application 121 acquires the number of sub-templates that have fallen on the repeated pages s to e and substitutes it for t (S2218), adds t to k, and substitutes it for k again (S2219). Here, k and n are compared (S2220). If the layout editing application determines No in S2220, that is, if it is determined that all the sub-templates acquired in S2202 can be poured, the process of the flowchart in FIG. 22 ends.

  However, if it is determined Yes in S2220, the process proceeds to S2210 again. After entering the processing of S2210, the processing from S2211 to S2213 is performed, and when it is determined to be Yes again in S2214, all the sub-templates (layout instances) acquired in S2201 are not the first repeated page and the first page. Even if a flow area in a page that is not a repeated page or a tail repeated page is used, it cannot be stored. Therefore, the process proceeds to S2215 again, and a page including the repeated flow area is generated. By repeating the above processing until it is determined No in S2220, the repeated pages are automatically generated until it is determined that all the sub-templates can be loaded. This generation may be generated by copying a predetermined page.

  Here, the above processing will be specifically described with reference to FIG. First, from the sub template (layout instance) acquired in S2201, as many sub templates as fit in the flow area of the page 2101 are poured. The steps so far are S2201 to S2208.

  Subsequently, when it is determined that all the acquired sub-teplates are not poured (S2209), the remaining sub-templates are poured into the flow area of the page 2103. The steps so far are S2210 to S2213.

  If it is determined that even if the flow areas of pages 2101 and 2103 are used, it is not possible to flow in all sub templates acquired in S2101 (S2214), the sub templates flowed into page 2103 are deleted, and the sub templates are deleted. It is poured into the flow area of page 2102 which is a repeated page. The processing so far is from S2215 to S2219. Through the above processing, the sub templates acquired in S2101 are sequentially poured into the flow areas of pages 2101 and 2102.

  Here, it is determined whether or not all the sub-templates acquired in S2101 have been accommodated (S2220). If it is determined that they have not been accommodated, the sub-templates that have not been accommodated are reflowed into the flow area of the page 2103. If it is determined that all the sub-templates are not flown through the processing up to this point (S2214-Yes), the process proceeds again to S2215, and a page 2102 that is a repeated page is generated, and the flow area of the generated page 2102 is displayed. The sub template will be poured. By repeating the above processing, as shown in FIG. 21B, only the repetitive page 2102 is repeatedly replicated (generated) until all the sub-templates are accommodated.

  Note that when a plurality of pages are designated as repeated pages, a blank page may occur depending on the number of sub-templates to be acquired. For example, when three page groups are designated as a repeated page, a repeated page group is generated because the acquired sub-template cannot be stored. At this time, three page groups are generated. Will be generated. However, depending on the number of sub-templates acquired, it is assumed that the second page of the newly generated repeated page group fits in, and the third page designated as the repeated page is blank. In this case, blank pages are automatically deleted according to user settings.

  As described above, in this embodiment, when the template does not fit in the flow area, a new page is automatically generated, and the sub-template that does not fit in the one-page flow area is continuously flowed. The purpose is to create a document with no page restrictions. Since the new page to be generated is a repeated page designated in advance by the user, it is possible not only to configure a page reflecting the user's intention, but also to automatically set the repeated page as described above. By doing so, it becomes possible to improve the operability of the user.

  Further, when all the laid out sub-templates can be arranged by using the page and the repeat page immediately before the repeat page (in the case of S2220-Yes), the flowchart of FIG. If there is content data to be output on the footer page, the process ends after adding the footer page.

  Further, in the present embodiment, the description is made by paying attention to the fact that one continuous flow area can be defined over a plurality of pages, and in particular, it refers to arranging a plurality of flow areas in one document. Absent. However, it goes without saying that a plurality of flow areas can be arranged over a plurality of pages.

  According to the present invention, different sub templates are selected according to the contents (values) of record data extracted from the database, and records are inserted into the selected sub templates. Then, by repeating the insertion process for each record, a partial layout in which various sub-templates and records are combined can be obtained. By making the layout-completed sub-template flow in order in the flow area, it is possible to realize a flow layout that repeats complicated layout switching, which cannot be realized by conventional pouring.

  In addition, if a sub template overflows from one flow area as a result of flowing a large number of records, a document having a high number of pages is automatically created by automatically generating additional pages including a layout area (flow area). Can be created. This is a very effective effect when creating a document such as a catalog in which partial layouts that are similar to a certain extent but have a different detailed layout structure and whose number of items is not predetermined are listed. It becomes.

[Third Embodiment]
In this embodiment, the first embodiment and the second embodiment are further developed, not only simply expanding the flow area to a plurality of pages, but also between sub-templates, between the flow area and the container, A layout editing application program that can be divided will be described. Therefore, with the second embodiment as an underlay, the description of the parts common to the second embodiment and the parts common to the first embodiment will be omitted, and different parts will be described. <Sub-template conditional expression>
The conditional expression is a mechanism for assigning a plurality of sub-templates to one flow area. Either a sub template or a conditional expression can be associated with the flow area. FIG. 26 is a diagram illustrating a UI example for setting a conditional expression. This is the same as in the first embodiment. However, in the present embodiment, it is possible to input the conditional expression stored as the sub-template information including the delimiter information under the same conditions as the sub-template.

  FIG. 26 shows an example of a UI for setting one conditional expression for receiving and processing one record from the database. This input area has at least a text box 2602 for naming the conditional expression and a pair of an IF statement 2603 and an ELSE statement 2604 that are elements constituting the most basic condition determination.

  In the input area of the IF statement, a list box 2605 for selecting a field that is a condition determination target, a list box 2606 for setting a logical expression for determination, a text box 2607 for inputting a value used for determination, and condition determination A THEN_USE processing statement 2608 for determining a sub-template for inserting the record, which determines an operation when it is positive. Further, a WITH processing statement 2609 for selecting a Break process (document delimiter process) attached when the sub template is changed, and ELSE_USE for determining a sub template for inserting the record when the condition determination result is invalid. It consists of a processing statement 2604.

  Various conditions such as EQUAL (equal), NOT EQUAL (not equal), LESS_THAN (small), LARGER_THAN (large), START_WITH (starting with), END_WITH (ending with) are prepared in the logical expression 2606 for determination. Further, when a field value is designated as the determination value 2607 determined by the logical expression 2606, for example, the field value input to 2605 and the field value input to 2607 are determined. When the record category is changed as in multi-record, multi-record printing for generating a new document becomes possible.

  Furthermore, “change” can be set as a logical expression for determination. The logical expression “change” for determination is effective when a Break process, which will be described later, is set every time the data value of a certain field value is changed. An effective point by setting the determination expression “change” will be specifically described with an example.

  For example, it is assumed that a layout process with a revised document is executed using a huge amount of record information. At this time, as an example of a conditional expression set by the user, setting processes such as “IF field01 EQUAL value01 with DocumentBreak”, “IF field01 EQUAL value02 WITH DocumentBreak”, and “IF field01 EQUAL value03 WITH DocumentBreak” are assumed to be “field01” It must be repeated for the number of data. That is, as the number of assumed data increases, the conditional expressions increase and become complicated. By using “change” described above, only one conditional expression is required. In other words, by setting “IF field01 change value with DocumentBreak”, the document break is executed each time the data of field value 1 is changed, so there is no need to set conditional expressions for the number of data expected. The operability can be improved.

  Further, in the WITH processing statement, DocBreak (revised document) which interrupts the record layout processing so far, prints a footer page, and then prints a new record from a new header page. Also, Page Break (page break) is started after interrupting the previous record flow, generating a new page, and starting a new record flow. Furthermore, four types of Break processing are prepared: Line Break (new line) for starting a new record flow from the next flow area, and None Break (continuation) for continuing the flow without performing the Break processing.

  Further, in order to set a complicated conditional expression, an AND / OR connection statement combo box 2610 is provided to set a compound condition in the IF statement. When an AND or OR compound condition is selected in this combo box, one condition line is added to the IF statement. In the case of AND, it is determined that the IF statement determination is true only when a plurality of conditions are all positive, and in the case of OR, when any of the conditions is positive.

  In order to set a more complicated conditional branch, an ELSE_IF statement addition button 2611 is provided. When 2611 is pressed, an ELSE_IF statement is newly inserted between the IF statement and the ELSE statement. The contents and operation of the ELSE_IF statement are the same as those in the IF statement. When the IF statement is invalid, the next lower ELSE_IF statement is determined, and when the IF statement is further incorrect, the next lower ELSE_IF statement is determined, followed by the final determination of the ELSE statement. Reference numeral 2612 denotes a delete button for deleting the selected ELSE_IF statement. When the number of ELSE_IF statements increases, a list of conditions can be displayed using the scroll bar 2613.

  If any IF statement or ELSE_IF statement determines true, the related USE processing statement and WITH processing statement are executed. In this way, through the conditional expression, a sub template that matches the condition can be automatically selected for each record having various values, and a Break process attached to the selected sub template is used in combination. Thus, various layouts can be realized with one conditional expression.

  By associating this conditional expression with the flow area, it is possible to flow a plurality of types of sub-templates having various layouts within the area in one flow area.

  When the user inputs conditions from the UI shown in FIG. 26, the user finally presses an OK button 2615. When the OK button 2615 is pressed, information indicating a sub template condition set in the UI (sub template conditional expression) is stored in the memory unit 136 as a part of the sub template information 2403. This sub-template conditional expression may be any information that can specify the sub-template when the conditions and conditions are satisfied, such as a text file in which (selected) text described in the UI of FIG. 26 is stored as it is. . In the example of FIG. 26, “IF field01 EQUAL value01 AND field02 EQUAL vlue02 THEN USE subtemplate01 WITH PageBreak ELSEE IF field01 EQUAL value03 AND field02 EQUAL vlue04 THEN USE subtemplate02 WITH PageBreak ELSE USE subtemplate03 WITH PageBreak” is saved as information indicating the subtemplate conditional expression. To do. Even if the data is stored as it is, it is described in a simple grammar and is input from the UI as shown in FIG. 26, so there is no room for grammatical errors. Therefore, a suitable sub-template can be determined by parsing the description of the conditions with a simple program.

<Layout processing>
FIG. 27A is a flowchart for performing condition determination in a template in which conditional expressions (extraction conditions and break processing) are set for the flow area, and executing layout processing according to the conditional expressions. FIG. 27A is a process in which steps S703 and S0704 in FIG. 7A of the first embodiment and steps S1009 and S1010 in FIG. 10 are combined.

  Here, the template will be described as an example including a header page, a repeated page including a flow area, and a footer page. In FIG. 27A, the layout editing application 121 first acquires data to be laid out from the database (S2701), and determines whether or not the record is finished (S2702). Since the layout editing application 121 performs processing while temporarily holding which record is currently targeted, the determination in S2702 is possible. If the layout editing application 121 determines the end of the record in S2702, the process proceeds to S2713 to execute the footer page layout process, and the process of the flowchart in FIG. If the number of records to be laid out acquired in S2701 is 0, the layout process cannot be executed. Therefore, the process of this flowchart is terminated without executing the footer page layout process in S2713.

  Next, the layout editing application 121 determines whether it is the first record (S2703). If it is the first record, the layout editing application 121 executes header page layout processing (S2704). Specifically, it refers to creating a header page using predetermined content data among the acquired records. At that time, the header page layout processing is realized in the same manner as the sub-template layout optimization processing described in the flowcharts of FIGS. 7A and 14 of the first embodiment. This means that the layout of the sub-template is defined in the same way as a normal template, and the layout optimization process is performed when the contents of the database are poured.

  Next, the layout editing application 121 determines whether or not the content data of the acquired record can be arranged from the content data of the acquired record and the conditional expression set in the flow area, and the record to be arranged If it is determined that the content data is, the sub-template and the Break process are specified based on the conditional expression (S2705). Specifically, the layout editing application 121 reads the sub-template conditional expression stored in the memory unit 136 as flow area information, and satisfies the condition by recognizing the conditional data and the content data included in the acquired record. The contents of the sub template name and Break (separation) processing can be specified.

  Next, the layout editing application 121 determines, based on the specified information, whether a Break process is defined and whether a Break process occurs (S2706). First, whether or not the Break processing is defined can be determined because the layout editing application 121 specifies the Break processing in S2705, and therefore whether or not the Break processing is set.

  Whether or not the Break processing occurs is determined by temporarily holding the content data of the previous record that is currently targeted and comparing it with the content data of the current target record. . Specifically, if the value of the field value (data item) designated for executing the Break process has been changed, it is determined that a Break has occurred.

  As a result of the determination in step S2706, when any one of “no break setting” or “no break occurrence” is determined, the content data of the currently targeted record is arranged in the sub template, and as described above The layout is adjusted in the template and placed in the flow area. (S2714). That is, the laid out sub-templates are arranged in the flow area with an interval specified in the flow area information.

  If the Break setting has been made in S2706 and it is determined that the Break process will occur, the layout editing application 121 determines whether DocBreak (revised document) is specified (S2707). In the determination process of S2707, it is possible to determine which Break process is set by specifying the Break process in S2705. In other words, the break processing is specified by the layout editing application 121 reading the flow area information.

  If it is determined in S2707 that DocBreak (revised document) has been specified, the layout editing application 121 interrupts the flow of records into the flow area and completes a new footer page to complete the output result so far. And layout processing (S2708). At that time, it is necessary to clear the Break setting in advance so that the same processing is not repeated. However, if the Break setting included in the sub-template conditional expression of the flow area information is cleared, the setting itself is changed. For example, Break indicating that the break processing of the revised document related to the record of interest has been completed. A completed flag is provided and set. Setting this Breaked flag eliminates the need to repeat the processing of S2705 and S2706 again.

  Therefore, the layout editing application 121 also determines in step S2706 that this Breaked flag is not set, and even if a break is set, it determines “No” if the Breaked flag is set. Then, the layout editing application 121 advances the processing to S2714, and arranges the current target record in the sub template and lays it out in the flow area of the target page. This break completion flag is reset when the layout of the record of interest is completed.

  Note that the footer page layout process in S2708 is realized in the same manner as the sub-template layout optimization process described with reference to the flowcharts of FIGS. 7A and 14 of the first embodiment, similarly to the header page layout process.

  Thereafter, the layout editing application 121 returns to the header page layout process (S2704) again, and repeats from the process of creating a new document. When the process returns to S2704 after the footer page layout process is completed in S2708, the Break setting is cleared in advance (that is, the Breaked flag is set), so the same process is not repeated again, and the Break definition It is determined that it has not been performed (S2706). Therefore, the normal layout is executed, and the content stored in the record is arranged on the page (S2711). As a result, a revised document is generated in the middle of record processing, and multi-record printing is realized.

  Since the revised document is set, the document can be revised when the content data to be arranged is arranged, so that a new document is generated every time the data attribute is changed.

  Next, as a result of the determination in S2707, when it is determined that the document break is not set, the layout editing application 121 determines whether Page Break (page break) is set (S2709). Since the determination process of S2709 is the same as that of S2707, detailed description thereof is omitted.

  As a result of the determination, if Page Break (page break) is set, the layout editing application 121 interrupts the flow so far and creates a new page (S2710). After creating a new page including a flow area for a page break, the layout editing application 121 obtains the size of the content data of the currently targeted record for the flow area of the new page, and executes a normal layout Then, the content stored in the record is arranged on the page (S2714). As a result, the flow of the sub template that has been laid out is resumed as a new flow in the flow area.

  As a result, a new page is generated each time the data attribute is changed. For example, the same product group can be configured as one page as a customized catalog when proposing multiple products to a user. It becomes. For Page Break, the Breaked flag is also used in the same manner as for Doc Break. The Breaked flag can have Break attribute information such as whether it is Doc Break or Page Break.

  If it is determined in S2709 that the Page Break setting is not set, the layout editing application 121 determines whether Line Break (line feed) is set (S2711). Note that the determination process in S2711 is the same as the determination process in S2707, and thus detailed description thereof is omitted.

  If LineBreak is set as a result of the determination, the layout editing application 121 moves the layout start point from the current flow area to the left end of the flow area corresponding to the next line (S2712). Specifically, the layout engine, which is one of the modules constituting the layout editing application, can recognize the arrangement position of the content data. Therefore, the layout engine recognizes the position of the sub template where the previous record was laid out, temporarily stores it in the memory unit, changes the sub template from there, and moves the layout start point to the left end. Thus, the processing of S2712 is realized.

  Thereafter, a normal layout is executed, and the content stored in the record is arranged in the flow area on the page (S2714). When the process of S2714 is completed, the layout editing application 121 performs the process of advancing the target record, returns to S2701, and enters the process of acquiring the next record.

  As a result, a line break occurs in the middle of the flow area. The new line in this case indicates that the record is moved by the height of the record laid out in the sub template. Note that the line break flag is also used in the same manner as Doc Break.

  Since the line feed is set, when content data having different data attributes are arranged, the line can be changed, so that sub-templates having the same data attribute can be laid out on the same line.

  From the above Break processing, a document composed of a header page, a flow area, and a footer page can be freely changed by various Break processing defined in the conditional expression, and the Break processing set in the flow area is set. Therefore, if the document is a revised document, the content data is arranged by dividing the document by creating a new document, and if it is a page break, the content data is arranged by separating the document by creating a new page, and an output result can be obtained. This makes it possible to obtain various output results during multi-record printing.

  FIG. 27B is a flowchart describing details of the process S2705 for determining the sub-template in FIG. 27A. The layout editing application 121 extracts the first IF statement of the conditional expression (S2721), and extracts the value of the field that is the determination target of the IF statement from the record received in S2701 (S2722). Since the conditional expression is stored in the memory unit as the flow area information as described above, the processing of S2721 and S2722 becomes possible when the layout editing application 121 refers to the memory unit.

  Subsequently, the layout editing application 121 determines whether or not the field value of the currently targeted record matches the conditional expression extracted in S2721 (S2723). Specifically, the content data of the record currently targeted by the layout editing application is temporarily stored in the memory unit 136, and the processing of S2723 is realized by comparing with the conditional expression stored as the flow area information. The

  If the layout editing application determines that the conditional expression extracted in S2121 matches the field value to be determined, the layout editing application selects the USE processing of the conditional statement and determines a sub-template (S2725). When the sub template to be used is determined, the layout editing application stores the current target record in association with the sub template to be used in the memory unit 136.

  If it is determined in S2723 that they do not match, the layout editing application 121 determines whether there is another conditional expression (S2724). Note that the determination processing in S2724 is the same as the processing in S2723. If there is another conditional expression in S2724, the layout editing application similarly performs the determination in S2723 using the other conditional expression.

  If the layout editing application 121 determines that the content data of the currently targeted record does not match any conditional expression, the layout editing application 121 selects the USE processing of the ELSE statement and determines a sub template (S2726). Since the ELSE sentence may not be set by the user, the processing in S2726 is omitted if there is no ELSE sentence conditional expression.

  Finally, the layout editing application 121 acquires the Break process defined by the WITH statement and stores it in the memory unit 136 (S2727).

<Sub template>
Next, the layout process flow of the sub-template layout process in step S2714 in FIG. 27A will be described with reference to FIG.
First, the layout editing application 121 acquires the size of data to be laid out in each container (S2801). Then, based on the data size acquired in S2801, the layout editing application 121 performs layout calculation in each container (S2802), and optimizes the layout (S2803). The layout calculation process and the layout optimization method are as described in the first embodiment.

  The layout editing application 121 determines a layout optimized by the above processing (S2804), and flows data to be laid out (S2805). This process is also as described in the first embodiment.

  Next, in order to lay out the sub template in the flow area, the layout editing application 121 acquires the size of the flow area (S2806), and acquires the size of the sub template to be laid out (S2807). As described above, since the size of the flow area and the size of the sub template are held in the memory unit 136, the size can be acquired. In the present embodiment, the size of the outer frame of the sub template is a fixed size that does not depend on the record to be flowed, even if it is a variable size determined by the contents of the record flowed into the container in the sub template as described above. It doesn't matter.

  The layout editing application 121 arranges the sub template in the flow area while applying the set flow direction and flow interval (S2808). Finally, the layout result is displayed and the process ends (S2809). Since the last display process is performed by a program that calls FIG.

  Steps S2801 to S2805 are the same as steps S1402 to S1406 in FIG. 14, and steps S2806 to S2809 are the same as steps S1713 to S1716 in FIG.

(Break example of flow area)
The processing of FIG. 27 will be specifically described with reference to FIGS. 29 and 35. FIG. 29 shows an example in which a plurality of documents are generated by DocBreak (modified document) processing.

  In FIG. 29, reference numeral 2901 denotes a flow area set for pouring a sub-template, and a conditional expression for using any of the sub-template 2902), the sub-template 2903, and the sub-template 2904 is set in the flow area. The conditional expression is set to execute THEN USE “sub-template 2902” WITH “DocBreak” if the destination field (data A) of the record is “1”. Furthermore, if the destination field (data A) of the record is “2”, it is set to execute THEN USE “subtemplate 2903” WITH “DocBreak”. If the destination field of the record is “3”, it is set to execute THEN USE “subtemplate 2904” WITH “DocBreak”.

  In other words, the revised document is executed in accordance with the change of the item of data A.

  Here, the flow of processing will be specifically described with reference to FIGS. 27A and 29. The layout editing application 121 acquires “record 1” in the data 2900. Here, since record 1 is the first record, “1” of data A included in record 1 is laid out in the container of the header page according to the association information. The processing so far corresponds to S2701 to S2704 in FIG.

  The layout editing application 121 recognizes that “data A = 1” of the record 1 and refers to the conditional expression of the memory unit 136 and if “the record destination field (data A) is“ 1 ”, THEN USE “Sub-template 1” WITH “DocBreak” ”is recognized. As described above, regarding the record 1, it is specified that the sub template 1 is used, and it is recognized that the revised document is set.

  However, since the Break process that occurs when the predetermined field value is changed in comparison with the previous record does not occur in the record 1, the process proceeds to S2714 in which the content data of the record 1 is flowed into the sub-template. This process corresponds to S2706 in FIG. 27A. Note that the content data of the record 1 is temporarily held in the memory unit 136 as described above.

  Subsequently, the layout editing application 121 returns to S2701 after S2714 and proceeds with the next record 2 as a target record. Since record 2 is not the end of the record and is not the first record, the process advances to step S2705. Here, the layout editing application uses the contents data “data A = 2” of record 2 and the conditional expression “THEN USE“ subtemplate 2 ”WITH“ DocBreak ”” if the record destination field (data A) is “2”. The sub-template used in the record 2 is identified as the sub-template 2, and it is recognized that the revised document is set.

  Further, the layout editing application 121 compares the content data of the record 1 and the content data of the record 2 that are temporarily held, and “data A = 1” in the record 1, whereas “ It can be recognized that the data A is changed to “2”. As a result, the Break process occurs when the record 2 is poured.

  From the above, the layout editing application advances the process to S2707 in order to recognize “Break process is set” and “Break process occurs” in the process of S2706. Here, since the “revision document” is set in the conditional expression corresponding to the record 2, the layout editing application creates the footer page 2907 for the record 1. The content data used here is content data included in the record 1. Furthermore, the layout editing application 121 sets the above-described Breaked flag.

  Through the processing so far, 2905, 2906, and 2907 constituting the document (a) shown in FIG. 29 are generated. Subsequently, the layout editing application 121 advances the process to S2704 to create a header page 2908 for the record 2. Since the above-described Breaked flag is set, the process of S2705 is omitted, and further, “No” is determined in S2706. Thereby, the content data of the record 2 is arranged in the sub template 2 and is laid out with respect to the flow area of the page 2909 of the document (b) which is a new document.

  Subsequently, when the same processing is performed for the records 3 and 4, “data A = 2” is obtained for the records 3 and 4, and the same processing as the data A of the record 2, so that the Break processing does not occur. Therefore, the layout editing application 121 proceeds to S2714, and the content data of the records 3 and 4 are laid out in the flow area of the document (b). Normally, the content data of the record 4 should also be laid out in the flow area of the page 2909 of the document (b), but since there is a lot of content data to be flown in, it could not be put in one flow area. A new page 2910 is generated by the repeated page function.

  In this way, the document can be changed in accordance with the change of the sub template.

  Next, a specific example of PageBreak (page break) will be described with reference to FIGS. 27 and 35. FIG. For example, a case where a record included in the data 3500 is poured is assumed.

  Reference numeral 3501 denotes a flow area set for pouring a sub template, and a conditional expression for using any one of the sub template 3502, the sub template 3503, and the sub template 3504 is set in the flow area. In the first conditional expression, when data A changes, WITH “DocBreak” is set. That is, the revised document is executed in accordance with the change of the data A. The second conditional expression is set to execute THEN USE “sub template 3502” WITH “Page Break” if the data B is “X”. Further, if the data B is “Y”, it is set to execute THEN USE “sub-template 3503” WITH “Page Break”. If the data B is “Z”, it is set to execute THEN USE “sub-template 3504” WITH “Page Break”. That is, a page break is executed in response to a change in the data value of data B.

  Here, the flow of processing will be specifically described with reference to FIGS. 27A and 35. The layout editing application 121 acquires “record 1” in the data 3500. Here, since record 1 is the first record, “1” of data A included in record 1 is laid out in the container of the header page according to the association information.

  The layout editing application 121 recognizes that “data A = 1” and “data B = X” of the record 1, and refers to the conditional expression of the memory unit 136 if “data B is“ X ”. , THEN USE “sub template 3502” WITH “Page Break” ”is recognized. As described above, regarding the record 1, it is specified that the sub template 3502 is used, and it is recognized that a page break is set. However, since the Break process does not occur in the record 1, the process proceeds to S2714 in which the content data of the record 1 is flowed into the sub template 3502. Note that the content data of the record 1 is temporarily held in the memory unit 136 as described above.

  Subsequently, the layout editing application 121 returns to S2701 after S2714 and proceeds with the next record 2 as a target record. Since record 2 is not the end of the record and is not the first record, the process advances to step S2705. Here, the layout editing application 121 recognizes the record “Data B = Y” and the conditional expression “If the data B is“ Y ”, the THEN USE“ sub template 3503 ”WITH“ Page Break ”” 2 is identified as 3503, and it is recognized that a page break is set.

  Furthermore, when the layout editing application 121 compares the content data of the record 1 and the content data of the record 2 that are temporarily held, the record 1 is “data A = 1”, whereas the record 2 is “ Since the data A = 1 ”, the revised document is not generated. However, since “Data B = X” of Record 1 is “Data B = Y” of Record 2, Break processing (page break processing) occurs. That is, the layout editing application 121 recognizes that “Break setting is present” and “Break processing has occurred” in S2706, and thus proceeds to S2707 and specifies the Break processing to be executed for the record 2.

  As described above, since the conditional expression applied to the record 2 is “THEN USE“ sub template 3503 ”WITH“ Page Break ”if data B is“ Y ”, it can be specified that a page break is executed. Therefore, the layout editing application 121 determines “Yes” in S <b> 2709 and generates a new page 3507.

  The layout editing application arranges the content data of the record 2 in the sub-template 3503 and lays it out in the flow area of the page 3507 newly generated in S2710.

  Further, since records 3 and 4 are “data A = 1” and “data B = Y”, the document break and page break are not executed. Therefore, the layout editing application 121 lays out the content data of the records 3 and 4 in the flow area of the page 3507. Normally, the content data of the record 4 should be laid out in the flow area of the page 3507, but since there is a lot of content data that cannot be put in one flow area, a new page function can be used to repeat it. A page 3508 is generated.

  Further, the above-described processing is executed for the record 5 as well. Since the content data of the record 5 is “data A = 1” and “data B = Z”, the page break process is executed although the page break process is not executed.

  Therefore, the layout editing application 121 arranges the content data of the record 5 in the sub template 3504 and arranges the content data of the record 5 in the flow area of the page 3509 newly generated by the page break process. It will be.

  Subsequently, the layout editing application 121 proceeds with the process using the record 7 as a target record. Since the content data of the record 7 is “data A = 2”, the data value is different from the data A of the records 1 to 6. Therefore, conditional expression 1 “data A is“ change ”WITH“ DocBreak ”” is applied and the document is identified as a revised document. In other words, the layout editing application advances the processing to S2707 in order to determine that “Break processing is set” and “Break processing occurs” in record 7.

  Further, the layout editing application 121 generates the footer page 3510 and sets the above-described Break completion flag because the set Break processing is a revised document.

  As a result, the layout editing application generates one document composed of pages 3505 to 3510 using records 1 to 6 and starts a new document creation process from record 7. When a line break is set as the Break process, the same process as described above is performed.

  When the flow area is divided by breaks, the divided flow areas are subjected to processing such as layout, assuming that they have the same attribute information.

[Fourth Embodiment]
The fourth embodiment of the present invention shows processing in the case where the conditional expression defined in the template is used as an external conditional expression file that can be overwritten (overwritten). In the template, the conditional expressions are described in an XML-compliant format as shown in FIG. 30, and the template definition itself is also in an XML-compliant tag format. Here, the format of the template itself is irrelevant and will not be described.

  FIG. 30 shows a format of a conditional expression file that is an external conditional expression file. It is the same as the format for saving the setting contents of the conditional expression setting UI in FIG. 26, and the contents displayed on the UI screen are directly applied to the tag format, and the <CONDITIONAL> tag, <IF> tag, <ELSEIF > Tag and <ELSE> tag. The <IF> tag includes a <FIELD> tag describing a determination formula and an <USE> tag describing a determination result. In the <USE> tag, the Break type is described in the WITH identifier. In the <CONDITIONAL> tag, a name for identifying the conditional expression is described. In the <FIELD> tag of the <IF> tag, a set of a field name, a judgment sentence, and a judgment value is defined, and when there are a plurality of judgment sentences, they can be connected by an AND identifier and an OR identifier. The <ELSEIF> tag is described in the same manner as the <IF> tag and is a branch destination of the <IF> tag. Finally, the <ELSE> tag is a branching destination when it does not match any judgment sentence, and only the <USE> tag is described.

  FIG. 31 is a flowchart describing a process for overriding an external conditional expression file. The process of FIG. 31 is performed at the head of FIG. 27A of the third embodiment.

  The layout engine 225, which is one of the modules constituting the layout editing application, reads the template specified by the input parameter into the memory 136 (S3101). Since the file format conforms to XML, the layout engine 225 parses the template file and expands it into an XML object tree (S3102). Next, the layout editing application 121 determines whether there is an external conditional expression file as an input parameter (S3103). This determination can be realized, for example, by giving a specific extension or name to the external conditional expression file. If there is an external conditional expression as a result of the determination, the layout editing application 121 reads the conditional expression file into the memory 136 (S3104). Next, the conditional expression is parsed and expanded into a conditional expression object tree (S3105). Next, the layout editing application 121 rewrites the conditional expression object tree described in the template read in step S3101 with the conditional expression object tree read by external reference (1906). Since it conforms to XML, replacement processing in units of objects can be performed by a known technique. After that, by executing the Break process described in FIG. S27A (S3107), the conditional expression set in the template can be dynamically changed at the time of printing. Therefore, the sub-template change condition according to the variable data to be flown Since this can be changed, more various variable prints can be realized.

  The evaluation of the conditional expression object tree can be realized by executing an operator by a stack machine according to a tree structure, for example. In the above procedure, parsing may be performed after overwriting the conditional expression in the XML format before parsing the conditional expression.

  With this configuration, the conditional expression can be set by editing it with a text editor, for example.

  As described above, according to the layout editing system of each embodiment according to the present invention, different sub templates are selected according to the contents (field values) of record data extracted from the database, and the selected sub templates are selected. Insert a record. Then, by repeating the insertion process for each record, a partial layout in which various sub-templates and records are combined can be obtained. By making the various partial layouts flow in order in the layout area, it is possible to realize a flow layout in which complicated layout switching that cannot be realized by conventional pouring is repeated.

  Further, it is possible to generate a document such as a booklet by regarding the various partial layouts as chapters at the time of bookbinding and performing page control by page break break processing. In addition, when the document break processing is performed with a template that forms a header or footer, a document for each customer can be generated simultaneously with one template and multiple records.

  This is very effective for on-demand printing, such as a customized catalog, in which a document with different product categories appealing to each customer is generated at one time.

  Note that the present invention can be applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, and a printer), and a device (for example, a copying machine and a facsimile device) including a single device. You may apply to. Another object of the present invention is to supply a storage medium (or recording medium) in which a program code of software that realizes the functions of the above-described embodiments is recorded to a system or apparatus, and the computer (or CPU or (MPU) can also be achieved by reading and executing the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the program code itself and the storage medium storing the program code constitute the present invention.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code. A case where part or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing is also included. Furthermore, after the program code read from the storage medium is written into a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer, the function is based on the instruction of the program code. This includes a case where the CPU of the expansion card or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

Computer system configuration diagram according to an embodiment of the present invention Computer system configuration diagram according to an embodiment of the present invention Schematic diagram of a computer module according to an embodiment of the present invention The figure which shows an example of the typical container which has the link between the main window of the typical application including the menu bar, the tool bar, the work area, and the floating palette according to the embodiment of the present invention, and the container The figure which shows an example of 16 patterns of the expression of the container by an example of the interface which concerns on embodiment of this invention The figure which shows an example of the typical container rule which concerns on embodiment of this invention The figure which shows an example of UI which produces the link which concerns on embodiment of this invention The figure which shows an example of the flow of the layout calculation which concerns on embodiment of this invention The figure which shows an example of the flow of the layout calculation which concerns on embodiment of this invention The figure which shows an example of UI corresponding to the flow of FIG. 7 which concerns on embodiment of this invention. Overview of multi-record according to an embodiment of the present invention The figure which shows an example of the whole flow in 1st Embodiment. The figure which shows an example of UI of FIG. 10 in 1st Embodiment. The figure which shows an example of UI of the setting dialog of the flow area in 1st Embodiment The figure which shows an example of the layout of the sub template in 1st Embodiment. The figure which shows an example of the layout flow of the sub template in 1st Embodiment. The figure which shows an example of setting UI of the conditional expression in 1st Embodiment The figure which shows an example of the flow which determines the conditional expression in 1st Embodiment. The figure which shows an example of the flow which determines the conditional expression in 1st Embodiment. The figure which shows an example of the layout calculation flow in the flow area in 1st Embodiment. The figure which shows an example of the layout of the sub template in 1st Embodiment. The figure which shows an example of UI which sets the flow area over several pages The figure which shows an example of UI which changes the position and size of a flow area Conceptual diagram of a flow area with repetition and data inserted into it The figure which shows an example of the flow which lays out a sub template in the flow area which extends over multiple pages A figure which shows an example of composition of template data The figure which shows an example of a structure of the template data of a multi record Schematic explaining operation | movement of the layout editing system of 1st Embodiment. The figure which shows the example of setting UI of the conditional expression in 3rd Embodiment Diagram of layout processing flow in the third embodiment Flow chart of template determination processing in the third embodiment Sub template layout flow diagram in the third embodiment The figure which shows the example of the Break process in 3rd Embodiment The figure which shows the format of the conditional expression which can be referred externally in 4th Embodiment Flow chart for reading external conditional expressions in the fourth embodiment Diagram explaining a set of containers at the time of layout calculation Diagram for explaining layout optimization processing Figure showing an example of variable print The figure which shows the example of the Break process in 3rd Embodiment

Claims (15)

A document processing apparatus that executes layout processing using first and second pages having areas for arranging content data,
Obtaining means for obtaining the content data;
When the content data acquired by the acquisition unit overflows from the areas of the first and second pages and the area included in the first page is larger than the area included in the second page, the first and second The content data is arranged in a two-page area and a new page area generated based on the first page, and the content data acquired by the acquisition unit overflows from the first and second page areas, When the area included in the second page is larger than the area included in the first page, the first and second page areas and a new page area generated based on the second page A document processing apparatus comprising arrangement means for arranging content data. The document processing apparatus according to claim 1 , wherein the new page is repeatedly generated until the content data acquired by the acquisition unit is accommodated. A setting means for setting an extraction condition for extracting content data to be laid out from the database in the area;
The acquisition unit, the document processing apparatus according to claim 1 or 2, characterized in that to obtain the contents data satisfying the extraction condition from the database. The document processing apparatus according to claim 3 , wherein the new page includes an area in which the extraction condition is set. The content data, document processing according to any one of claims 1 to 4, characterized in that a group of small areas obtained by inserting the text data or image data into a plurality of small regions associated apparatus. A document processing method for executing layout processing using first and second pages having areas for arranging content data in a document processing apparatus having an acquisition unit and an arrangement unit,
An obtaining step in which the obtaining means obtains the content data;
When the content data acquired by the acquiring step overflows from the areas of the first and second pages, and the area included in the first page is larger than the area included in the second page, The content data is arranged in a region of the first page and the second page and a region of a new page generated based on the first page, and the content data acquired by the acquisition step is the first and second pages. A new page generated based on the areas of the first and second pages and the second page when the area overflows from the area and the area included in the second page is larger than the area included in the first page. A document processing method comprising: arranging the content data in an area of the document. The document processing method according to claim 6 , wherein the new page is repeatedly generated until the content data acquired in the acquisition step is accommodated. The document processing apparatus further includes setting means,
The setting means further includes a setting step for setting an extraction condition for extracting content data to be laid out from a database in the area;
8. The document processing method according to claim 6 , wherein in the obtaining step, content data satisfying the extraction condition is obtained from the database. The document processing method according to claim 8 , wherein the new page includes an area in which the extraction condition is set. The document processing according to any one of claims 6 to 9 , wherein the content data is a small area group obtained by inserting text data or image data into a plurality of associated small areas. Method. A program for causing a computer to function as a document processing device that executes layout processing using first and second pages having areas for arranging content data,
Obtaining means for obtaining the content data;
When the content data acquired by the acquisition unit overflows from the areas of the first and second pages and the area included in the first page is larger than the area included in the second page, the first and second The content data is arranged in a two-page area and a new page area generated based on the first page, and the content data acquired by the acquisition unit overflows from the first and second page areas, When the area included in the second page is larger than the area included in the first page, the first and second page areas and a new page area generated based on the second page A program for causing a computer to function as arrangement means for arranging content data. 12. The program according to claim 11 , wherein the new page is repeatedly generated until the content data acquired by the acquisition unit is accommodated. Causing the computer to further function as a setting means for setting extraction conditions for extracting content data to be laid out from the database in the area;
The program according to claim 11 or 12 , wherein the acquisition unit acquires content data satisfying the extraction condition from the database. The program according to claim 13 , wherein the new page includes an area where the extraction condition is set. The program according to any one of claims 11 to 14 , wherein the content data is a small area group obtained by inserting text data or image data into a plurality of associated small areas.

Images