JPS63131265A - Document forming device - Google Patents

Abstract

PURPOSE:To improve the operability of forming a document by mutually changing over editing operation without terminating the functions of respective editing parts such as forming and editing data in an area, editing the area in a layout screen, and changing over display pages. CONSTITUTION:An input part 1, a display part 2, a storage part 3 and a printing part 4 are connected to a control part 5. The control part 5 controls respective parts, and it consists of an input control part 51, a window control part 52, a system control part 53, a printing control part 54, a display control part 55, an editing part 56, a system control part 57, and a file editing part 58. The document is formed and edited in the editing part 56 consisting of two parts of a document editing part 561 and an area editing part 562.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention creates a document by mixing different types of data such as text, graphs, figures, etc.

The present invention relates to a document creation device that can be edited.

[Conventional technology]

In recent years, document creation devices such as word processors handle not only text (character) data, but also graphics, graphs, and tables.

There are more and more types as shown in the image. In addition, as a method for creating/editing a document in which multiple types of data are mixed, as described in Japanese Patent Application Laid-open No. 18036/1983, specifying the area where the data to be edited is stored on the page layout of the created document After that.

A method is used in which detailed information for that area is displayed and edited in areas different from the page layout described above.

[Problem that the invention seeks to solve]

The above-mentioned conventional technology allows users to edit another area while editing a certain area, or refer to the layout of a page other than the page on which that area exists while editing a certain area. This point has not been taken into account, and for this reason,
Perform the above operations (if you only need one, either finish editing the currently created area, or print the currently created document and then edit it in another area while referring to it). There was a problem in that document creation efficiency was poor because it was necessary to go through the steps of restarting editing.

An object of the present invention is to switch to other editing operations without completing the creation and editing of various data, editing of areas on layout display, switching of display parts, etc., when creating a document containing a mixture of multiple data. The object of the present invention is to provide a document creation device that can perform the following tasks.

[Means for solving problems]

The above purpose is to provide an input section for inputting description elements to be described in one document for each area, a storage section for storing input description elements, and a display section for displaying various description elements stored in the storage means. In the document creation device, the document editing section displays the page layout of the created document on the display section and edits the area according to the display, and the type of description element data that creates and edits the description element data in each area. Created by multiple area editing sections according to the document and the document editing section.

activating means for activating a corresponding area editing section according to the type of loading element data of the area instructed to be updated; and an area editing section activated by the document editing section and the activating means;
Both of these can be achieved by providing editing section switching means that switches the editing section without terminating its function.

[Effect]

The editing section switching means operates to temporarily interrupt the processing by the editing section that is currently editing, and to restart the processing by another editing section that has already been interrupted. As a result, when moving on to the operation of another editing section, there is no need to terminate the editing section currently in process, thereby improving document creation efficiency.

〔Example〕

Hereinafter, an example in which the present invention is implemented in a Japanese word processor will be explained with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a Japanese word processor to which the present invention is applied, in which 1 is an input section using a keyboard for inputting characters, a pointing device such as a mouse for indicating operation targets, function names, etc., 2 is a display unit such as a CRT display that displays characters, figures, etc.
Reference numeral 3 denotes a storage unit such as a semiconductor memory or a magnetic storage device, which stores the contents of created documents, window management information, etc. to be described later. 4 is a printing section such as a wire dot printer, and 5 is a control section such as a microprocessor for controlling each of the above-mentioned sections, including an input control section 51, a window management section 52. System control unit 53. Print control section 542 Display control section 552 Editorial section 56. System management department 57. It is composed of a file editing section 58. In this embodiment, document creation and editing are performed by one editing section 56, which further includes a document editing section 561. The area editing section 562 is composed of two parts.

FIG. 2 shows a screen displayed on the display unit 2. Picture 1iT2
1 is the menu area 22. It consists of an Ml collection area 23° and an icon area 24. Each editorial department.

Data is displayed in each rectangular frame 25 (hereinafter referred to as a window) in the editing area 23, and document data is individually edited within the window.The menu area 22 displays the functional classification name of each editing section. 26 (hereinafter referred to as pull-down menu name) is displayed, and when the operator points to pull-down menu name 26 with the mouse,
A window is set (hereinafter referred to as opening a window), and a detailed list of function items 28 is displayed inside (hereinafter referred to as a pull-down menu). For example, as shown in FIG. 2, in the menu area 22.

Pull-down menu names 26 such as edit and print are displayed, and when the operator instructs editing using the mouse, a pull-down menu 28 opens and function items such as new creation and update are displayed. In this state, when the operator specifies a function item with the mouse, the specified function will be executed.

The window 25 includes a caption area 251 . . . that displays a window name, for example. Data area 252 for displaying data. Operators can close, move, or
Control area 253 for instructing operations such as resizing
It consists of The icon area 24 contains pictograms (hereinafter referred to as icons) representing each program such as the editorial department.
27 is displayed, and when an icon is selected by the operator, the corresponding program is started.

As shown in FIG. 3, the mouse 31, for example,
An execution button 23112 for selecting a function etc. and a cancel button 312 for canceling the selected operation target are provided. The mouse cursor 3o moves within the screen 21 following the movement of the mouse 31 by the operator, and is used to indicate an operation target within the screen 21.

Each part constituting the second control section 5 will be explained below.

The system management unit 57 starts programs corresponding to the icons notified from the input control unit 51, such as the file editing unit 582 and the document editing unit 561. The correspondence between icons and programs is shown in the icon management table 571.
The icon management table 57 shown in FIG.
1 stores the program number corresponding to the icon number.

The program number is an identification number assigned to each program, and each program is managed by a program control table 572 shown in FIG. The program control table 572 has program control blocks 573 (hereinafter abbreviated as PCB) arranged in order of program number.

The PCB 573 contains program start address information 5731
．． Stack address information 5732. Priority information 5733.
Parent program number 5734. Data type information 5735,
Other programs and attribute information 5736 are stored.

The parent program number 5734 indicates from which program the program is started.

Data type information 5735 indicates what kind of data the program handles, such as text and graphics, and stores a data number. In addition, the data name corresponding to the data number is stored in the data name definition table (hereinafter abbreviated as DNDT) 574, as shown in FIG.
is stored in

The file editing section 58 displays a list of documents stored in the storage section 3 in a window, and edits the specified document. Here, document editing is a general term for updating, deleting, printing, etc. of a document.

The document editing section 561 displays in a window the layout of the corresponding part of the document that the file editing section 58 has instructed to create or update, and edits the area one page higher. Here, editing an area refers to instructions for creating and updating element data within the area,
Further delete and move.

It is a general term for things such as copying.

The area editing unit 562 displays in a window the contents of the area for which new creation or updating has been instructed by the one-document editing unit 561, and performs creation and editing of data within the area. The area editing section 562 includes various editing sections depending on the type of data. That is, text data editing section, graph data editing section 2
This includes the graphic data editing department.

Among the above editing sections, the one that can be executed after the start of document creation is always the editing section in the topmost window on the screen. Also, make the window the top level. That is, to switch the editing section, move the mouse cursor 30 onto the currently displayed window and press the execution button 311. This specified change in the stacking order of windows is performed by the window management unit 52.

In addition to changing the stacking order of windows, the window management unit 52 opens and refreezes windows on the screen in accordance with requests from each &1 East. The windows opened on the screen are managed by the window management table 521 shown in FIG. 7. The window management table 521 has window management blocks 522 (hereinafter abbreviated as WCB) arranged in order of window number. The following information is stored in the WCn522.

・Window setting position and size information 5221 Screen 21
If the origin is the upper left of the window, the upper left X coordinate of the window, the same y
Store the coordinates, the lower right X coordinate, and the lower right y coordinate.

- Window stacking order information 5222 If multiple windows are open on the screen,
Information indicating the order in which they overlap is stored.

- Window name information 5223 Stores the window name to be displayed in the caption area 251 of the window 25.

・Task number 5224 The number of the task that set the window is stored.

Each editorial department is generated as one task.

The task number is determined by the editorial department when it is generated as a task.
- Provided by the system control unit 53 described below.

- Window display image storage location information 5225 One window display buffer is prepared for each window, and the display image data of the window is stored there. The location of the corresponding window display buffer is stored in the window display image storage location 1i5225.

This information is used to recover the display image of the portion hidden beneath the window when changing the stacking order of the windows.

Stores the storage address of menu data to be displayed in 728.

- In-use flag information 5227 Stores information indicating whether the CB 522 is in use.

The window management unit 52 changes the stacking order of windows, opens and closes them, etc. based on the above information. When changing the stacking order, the window management unit 52 instructs the system control unit 53 to interrupt the editing section that was currently being edited and to restart the editing section of the specified window using the task number 5224 mentioned above. Control unit 5
Request 3. It also requests the input control unit 51 to display the menu corresponding to the window that has become the topmost window by operating the window, according to the menu data storage location 5226.

The system control unit 53 interrupts the corresponding task based on the request from the window management unit 52.

Controls restart, etc. In addition, the system control unit 53 generates a task for the corresponding editorial department based on a request from each editorial department, starts a task corresponding to the corresponding editorial department based on a startup request from each editorial department, and , performs termination processing of the task corresponding to the corresponding editorial department based on the termination request from the editorial department.

Furthermore, in order to enable information exchange between tasks, the system control unit 53 transmits messages to the corresponding editorial department based on requests from each editorial department, and sends messages sent from the corresponding editorial department. Each task that performs the process of receiving is managed by a table called a task control table 531 shown in FIG. The task control table 531 has task control blocks 532 (hereinafter abbreviated as TCB) arranged in order of task number, and one TCB 532 is allocated to one task. TCB53
For example, all information necessary for starting and restarting a task is stored in 2, as shown below.

・Link field 5321 Used when connecting TCB532 to the list.

・Task priority information 5322 Stores priority information when executing tasks.

=Program number 5323 Stores the number of the program that generated the task.

-Task status information 5324 Stores information indicating what status the task is currently in.

- Suspension flag information 5325 Information indicating that a suspension request has been made to the task is stored.

-Task start and restart address information 5326 Stores the start address of the task or the address at the time of interruption.

・Stack status information 5327 Stores the stack position at the time the task was suspended.

-CPU status information 5328 Saves all register contents at the time the task was interrupted.

Here, the status of the task is as shown below, for example.

-NONEXISTENT state Indicates a state in which the program does not exist as a task. At this time, the task number corresponding to the TCB becomes unused.

- Dormant state Indicates a state in which a program exists as a task, but execution is prohibited.

- When a CPU is assigned to a READY state task, the part that assigns a task to the CPU, which indicates a state in which a program can be executed, is called a task dispatcher.

・RUNNING state Indicates the state in which the task program is being executed.

・Waiting (tlAITING) state Indicates a state in which execution of a task is suspended until a certain event occurs. For example, there is a wait for message reception, in which the user waits until the message is sent, and a wait for input/output, in which the user waits until the input/output ends.

As shown in FIG. 9, tasks in the READY state are managed, for example, by connecting corresponding TCBs to one list 1 to 1 in priority order (this list is called a READY queue). A pointer to the TCB corresponding to the task in the READY state with the highest priority is stored in the header 533 of the READY queue, and a link field 5321 of the TCB is stored.
stores a pointer to the TCB corresponding to the task with the next highest priority, and the following TCBs are similarly connected by pointers in order of priority, and the link field of the last TCB indicates that it is the last TCB in the list. Information indicating the is stored. The task dispatcher allocates the task corresponding to the highest priority TCB connected to the READY queue to the CPU and causes the task to be executed.

A task in WAITING state is 1, for example, the corresponding TCB
The TCB is connected to a list prepared for each cause and managed according to the cause of each wait, and when the wait is canceled due to the occurrence of a certain event, the TCB is removed from the corresponding list, the READY queue is connected, and the task is dispatched by the task dispatcher. resumes from where it left off.

Messages are managed by a message control table 534, as shown in FIG. The message control table 534 includes a message control block 535 (hereinafter MC).
(abbreviated as B), and one MCB 535 is allocated to one message. M.C.B.
535 includes, for example, status information 5351.535 indicating whether the MCB 535 is being used. Sending side task number 5352° Receiving side task number 5353. Message size information 5354. A message buffer 5355 that temporarily holds transmitted messages is stored. Also, depending on the parameters at the time of the message reception request, when there is a message reception request, if the message has not yet been sent from the other task, the TCB 532 corresponding to the task that requested reception is removed from the READY queue and shown in FIG. VAIT is connected to the message reception queue 536 shown in FIG.
It is possible to put the task in the ING state, or it is possible to simply pass the message to the task that the message has not been sent without putting the task in the IuAITING state.

Here, the overall processing flow of the system control unit 53 will be shown using FIG. When a processing request is issued from a task to the system control unit 53, the execution environment at the time when the task issued the request is first saved in the TCB 532 (step 1001). Next, identify the requested functionality (step 100
2) and perform the processing corresponding to each function (steps 1003~
1008). After completing the processing corresponding to each function,
It is determined whether the task is to be switched, for example, based on the state of the READY queue (step 1011), and if the task has been switched, the task dispatcher is activated (step 1013). If the switch is not made, the execution environment saved in step 1001 is restored from the TCB 532 in step 1012.
), restarts the requesting task. Furthermore, when an input/output end interrupt occurs from an input/output device, the execution environment at the time of the interrupt occurrence is saved to the TCB 532 (step 1
009), then.

After completing input/output processing such as passing the input character code to the input requesting task and releasing the input task from waiting (step 1010).

Activate the task dispatcher (step 1o13). The task dispatcher determines whether the TCB is connected to the READY queue (step 1191), as shown in FIG. 12j.

If it is not connected, it loops infinitely until an interrupt occurs (Step 1197), and if it is connected, it goes to READY.
The TCB with the highest priority is acquired from the pointer stored in the header 533 of the queue, and it is determined from the suspension flag information 5325 of the TCB whether there is a request to suspend the task (step 1192). If there is an interruption request, update the pointer and remove the TCB from the READY queue (step 1193), repeat the process from step 1191, put the TCB in the ACTIVE state (step 1194), and set the execution environment from the TCB. After recovery (step 1195), the corresponding task is restarted (step 1196).

The functions required of the system control unit 53 are as follows:
For example, task creation/deletion processing (step 1003),
Task startup/termination processing (step (1004)), task forced termination processing (step 1005), task suspension/resumption processing (step 1006), message transmission/reception processing between tasks (step 1007), input/output requests Input/output request processing 10 with processing (step 1008)
08 accepts input/output requests from tasks to the keyboard, display device, etc., puts the requested task in VAITING state until the input/output is completed, or sets the V
For example, a task in an AITING state is transitioned to a REDY state. Other processes are shown in FIGS. 12a to 12i, and detailed rules will be described later.

The input control unit 51 passes character codes input from the keyboard and coordinate values input from the mouse to the task,
According to the area on the screen 21 designated by the mouse, notification of the designated icon to the system management unit 57, notification of the designated menu task, and window management unit 5 are performed.
2 to request switching of the specified window.

As shown in FIG. 13, first, in step 1301, input data from the input unit 1 is analyzed to determine whether or not the input is from a mouse. If the input is not from the mouse, the input is from the keyboard, and the character code corresponding to the pressed key is acquired (step 1311), and the acquired character code is passed to the input request task (step 1312). For example, if the operator presses the character key for "A" on the keyboard, the character code for "A" is passed to the task that requested the input. If it is determined in step 13o1 that the input is from the mouse, the coordinates are determined to find out where on the screen the operator has indicated (step 1302), and the mouse cursor 30 is displayed at the mouse movement position (step 1303). As a result of step 1302, if the operator's instruction is inside a window that is not at the top level, it is determined that it is a window switching instruction.Step 13
04), requests the window management unit 52 to switch the window (step 1316).

If the operator's instruction is in the icon area 24 (step 1305), it is determined which icon was instructed and after obtaining the icon number (step 1313), the obtained icon number is notified to the system management unit 57 (step 1314). ). Further, the system management unit 57 determines the program corresponding to the notified icon from the icon management table 571, generates the program as a task, and instructs the system control unit 53 to generate and activate the task. request. In addition, in the case of instructions for the operation target within the top-level window (Step 1
306), after converting the indicated coordinate values from coordinates on the screen to relative coordinate values within the window (step 1317).
), and passes the coordinate value to the task that requested the input (step 1318).

If the operator's instruction is the menu area 22 (step 1307), a request is made to the window management unit 52 to open a pull-down menu (step 1315).
. Further, if the operator's instruction is the pull-down menu area 28 (step 1308), it is determined which function item was instructed, and the instructed function item number and pull-down menu number are passed to the task that requested input ( Step 131.9). If the operator's instruction is the control area 253 or caption area 251 within the window (step 1309), a code for closing, scrolling, etc. is passed to the task that requested the input (step 13).
10). If other areas are specified, do nothing. Further, in the above, when passing the code to the input requesting task, the system control unit 53 causes the task that requested the input to transition from the VAITING state to the READY state.

The menu is displayed in the menu management table 523 shown in FIG.
．． It is managed by a pull-down menu management table 525. The menu management table 523 includes 5231 pull-down menus, followed by 5 menu management blocks.
24 are stored in pull-down menu number order by the number of pull-down menus. The menu management block 524 includes
Pull-down menu name 5241. The maximum number of characters for a function item is 5242, and the number of function items is 5243. A pointer 5244 to the pull-down menu management table 525 is stored. In addition, the pull-down menu management table 525 includes
Function item name 5251. Valid/invalid flags 5252 indicating whether a functional item is valid or not are stored in the order of functional item number for the number of functional items.

Based on the above information, the input control unit 51 displays the pull-down name of the topmost window in the menu area 22 when a window is opened or switched when there is a request from the window management. Further, if a pull-down name is specified by the mouse, the function item name is acquired from the corresponding pull-down menu management table 525, and if the function item is valid, it is displayed normally, and if it is invalid, it is displayed in half-brightness in the pull-down menu area 28. to be displayed.

The print control section 54 is for controlling the printing section 4 based on a document printing request from the editing section 56 . Also,
The display control section 55 includes an editing section 56 and a window management section 5.
Due to display request from 2.

This is for writing display data of only the portion that can be developed in the topmost window based on the stacking order information of the window management block 522 into the memory for displaying on the display section 2 in units of dots.

Document creation and editing in the Japanese word processor of this embodiment is performed as follows.

First, in the initial state, the operator starts creating a new document or editing an already created document by pointing the corresponding icon using the mouse.

In response to this instruction from the operator, the input control unit 51 determines which icon is instructed from the screen instruction coordinates,
The icon number is notified to the system management section 57. on the other hand,
The system management unit 57 is in an initial state as shown in the flowchart of FIG.

After the icon is displayed (step 1701), a message is requested to be received (step 1702), and if the message is received, the sender of the message is determined (step 1703), and the message is sent from the input control section 51. If so, then the program number corresponding to the designated icon is obtained based on the icon management table 571 (step 1704), and the corresponding editing section is generated as a task.

Activate (step 1705). The generation and activation of this task is performed as shown in the processing flows of FIGS. Based on this, the control unit 53 acquires an unused task number from the task control table, creates a corresponding TCB (step 1101), puts the task in the DORMANT state (step 1102), and returns the acquired task number to the request source (step 1102). Step 1103), then the system management section 5
7 makes a task activation request according to the task number, and the system control unit 53 sets the TCB corresponding to the specified task number in the READY state in step 1121.
) to connect to the READY queue. This puts the editing section in an executable state (step 1122).

Further, the above-mentioned notification is performed by sending and receiving messages via the system control unit 53.

For example, as described above, when transmitting a message from the input control section 51 to the system management section 57, first,
The input control unit 51 requests the system control unit 53 to send a message to the system management unit 57 (step 1706).

Accordingly, as shown in FIG. 12h, the system control unit 53 determines from the message control table whether a reception request has been received from the system management unit 57 (step 1171), and if a reception request has been received, responds to the transmitted message. To transfer the message to the message buffer of the MCB, step 1174) removes the task waiting for reception, that is, the TCB of the system management section 57, from the message queue and reads the READ
Connect to Y queue (step 1175). Further, if there is no reception request yet, the system control unit 53
CB is acquired (step 1172), and the message is transferred to the message buffer of the MCB (step 117).
3) On the other hand, when the system management unit 57 requests the system control unit 53 to receive a message, the system control unit 53 checks whether the message for the system management unit 57 is in the MCB, as shown in FIG. If there is a message (step 1181), the message is retrieved from the MCB and transferred to the system management section 57 which is the request source (step 1184). In the above, MCB
If there is no message, it is determined whether the task that issued the macro made the request specifying that there is a wait (step 1182), and if there is no wait, the process returns to the task that there is no message and ends the process. (Step 1185), if there is a wait, after acquiring an unused MCB, remove the TCB of the task from the READY queue in FIG. 9, connect it to the message reception queue 536,
Transfer control to dispatcher (step 1183゜11)
86), therefore, when a message is transferred to the MCB due to a message transmission request, the task waiting to receive it is
Since the task is connected to the EADY queue, the task is restarted and executed again from message reception processing, and the contents of the MCB (message) are received by the task.

As a result, if the instruction from the operator is to create a new document, the document editing section 56 is sent to the document editing section 56, and if the instruction from the operator is to edit an already created document, the file editing section 56 is used to instruct which document to edit next. 58 are activated by the system management unit 57, respectively.

Next, the processing contents of the file editing section 58 will be explained based on the flow shown in FIG. 19. The file editing section 58 first opens a window (step 2001), displays a list of documents stored in the storage section 3 in the window (step 2002), and after displaying the list, the file editing section 58 opens the input control section If the input is received, the content is determined (step 2004). If the input from the operator is an instruction for a document to be operated, the process determines which document was specified. The document name is determined and registered in the operation target document table 581 shown in FIG. 20 (step 2005). Note that the operation target document table 581 includes a designated document number 5811 and a designated document name 5812. If the instruction is to update or print, the system management unit 57 is notified that the instruction to update or print has been given, along with the name of the currently targeted document and the data type number corresponding to the document (step 2006); In the case of an editing instruction such as copying or deleting a document, processing such as copying or deleting the target document is performed (step 2007), and in the case of a scrolling instruction, a scrolling display of the document name list is performed (step 200).
8) In the case of an end instruction, the window is closed (Step 2009), the system management unit 57 is notified that the file editing process has ended (Step 2'010), and the end of the task is requested (Step 2011). In response to this termination request, the system control unit 53 sets the TCB of the requesting task to the DORMANT state (step 1131) and releases the resources used by the task (step 1132), as shown in FIG. 12d. Here, resources refer to memory and CPU.

Now, the above-mentioned window opening/closing process is carried out by the window management section 52, and the contents of the process will be explained based on the flowcharts shown in FIGS. 15 and 16.

First, in the case of opening a window, the window management unit 52
generates WCB 522 based on the information specified by the task (step 1501), and at this time, it is determined whether the window already exists or not (step 1502).
), if it exists, suspend the task using the currently topmost window (step 15).
'03), the display image of the topmost window is saved in the display buffer (step 1504). Then, the window is displayed according to the position and size specified by the task (step 1505), and the number of the generated window management block is returned to the requesting task (step 15).
06).

On the other hand, in the case of closing, first, the image of the specified window is deleted (step L511), the window hidden by the window to be closed is determined from the window management table, and the display image is retrieved from the display buffer mentioned above. Step 1: Restore the display image of the window below the erased window
512).

Make 'dc8522 in the erase window unused (
step 1513).

Note that the task interruption process described above will be described later.

As mentioned above, if the operator requests new creation,
The system management unit 57 generates the document editing unit 561 as a task based on the notification from the input control unit 51 (step 1).
705), start in new creation mode (step 170)
7) In addition, in the case of updating an already created document, the corresponding program number is obtained from the program control table (FIG. 5) based on the data type number notified from the file g collection section 58 (Step 1708), the document editing section 561 Step 1709) to generate a task as a task, and step 1710) to send startup parameters to the editing section 561.
Start the document editing section 561 in update mode (Step 1
711).

Furthermore, when the system management section 57 receives and receives a completion notification from the editing section that it has generated and started, it deletes the task (step 1712).As with the above-mentioned generation request, the system control section 57 deletes the task (step 1712). As shown in FIG. 12b, the system control unit 53 puts the TCB corresponding to the designated task in the N0NEXISTENT state (step 1111), that is, puts the TCB in an unused state.

Incidentally, when the system management section 57 starts up the document #g collection section 561, it sends the above-mentioned mode and the generated task number as startup parameters to the document editing section by a message. Furthermore, in the case of the update mode, the update target document name notified from the file editing section 58 is also transmitted.

Now, FIG. 21 shows the processing of the activated document editing section 561.
This will be explained based on the flowcharts shown in FIGS. 22a to 22Q.

The document editing unit 561 first performs initial processing (step 3001
), the details of which are shown in FIG. 22a, step 3101
), the startup mode, new creation or document update, is determined based on the contents of the parameters (step 3102). and,
In the case of new creation, the document data is initialized (step 3103), and in the case of document update, the data to be updated is called from the storage unit 3 according to the document name specified by the parameter (step 3104).

Note that the structure of one document data will be described later. and,
From the program control table (FIG. 5), a support area editing department management table (hereinafter abbreviated as SFMT) is created which shows a list of areas Hz parts in which new areas can be created and updated in the document. As shown in FIG. 27, the SFMT holds the program number 5683 of the area editing section that can be supported and the type number of data that can be created by this area editing section in pairs, and further has the area editing section 5681 mentioned above. . At the same time, in order to inform the operator of what kind of data areas can currently be created, the name of the data for the area editing section ' is set in the pull-down menu data (step 3105). Then, when editing the area described later, clear the specified area of the operation target area table (Fig. 28) indicating which area is the operation target to 0 (Step 3106), and then enable/disable the pull-down menu data. The state is initialized (step 3107). Note that the operation target area table is the 28th
As shown in the figure, the number of designated areas currently designated as targets for operation is 5684. Specified area type 568
5 and retains the specified area number 5686 (
The type of area will be described later. Switching between enabling and disabling this pull-down menu data will be described later.

Subsequently, the sentence sm collection unit 561 opens the window (step 3108), and displays the layout of the first page of the edited document in the window as shown in FIG. 31(a) (step 3109).

When opening the window, the size of the window should correspond to the size of the display paper above.

Also, part of the window title includes the document editing section. 1. Add the task number of section 561.

Now, the above SFMT and menu data creation (second
The process of step 3105) in FIG. 2a will be explained in more detail.

As shown in Figure 27, SFMT is useful for the document editing department.
This is a table showing a list of program numbers 5682 and data type numbers 5683 of the area editing section that can be activated, and whether or not corresponding programs exist in creating new areas, updating areas, and displaying layouts, which will be described later.
Used as a parameter when creating a task.

The method for creating it is as shown in FIG.
111, 3112), and sequentially from the first block of the program control table (FIG. 5), it is determined whether the parent program number matches the program number of the document editing section itself (3114).

If it matches, sentence i! The program number P is regarded as PCB573 for the area editing section that can be started by the F editing section.
And the data type number Dp set in the PCB 573 is registered in the SFMT (step 3115).

In addition, the name of the data corresponding to the data type number (for example, "Graphic", "Grab", etc.) is obtained from the DNDT (Figure 6), and the name is applied to the menu data held by the document editing department itself (Figure 23). ) is registered as the name of the pull-down menu data for creating a new area.Step 3116) Increment the registration number E (Step 3117). Repeat the above process for the number of program management blocks. E is set in the area editing section 5681 (step 3119).

This makes it possible to display, as a pull-down menu, only the names of area editing units that are currently actually incorporated into the system.

Here, the structure of the document data will be explained using FIG. 24.

The document data is stored in the chapter 1 management table 5610. as shown in FIG. Page management table 5620. true format table 5
630. It is composed of an area management table 5640 and intra-area data 5660, and each table is composed of a plurality of blocks. Each table will be explained below.

・Car management table 5610 Manages how many chapters the entire document consists of,
Page pointer 5611 indicating the first rI4/last page for each chapter
, 5612. In addition, the chapter 1 management table has printing information 56 for displaying and printing headers, footers, etc. for each chapter.
Hold 13.

・Page management table 5620 Area pointers 5623 and 5624 that indicate the first/last areas of the areas set within the page, and a trade pointer 5625 that indicates which format data is used on each page
and has. In addition, each block has a backward pointer 562
1 and the forward pointer 5622 to link the pages in ascending order,
The first and last pages are pointed to from the above-mentioned car management table. The pages in this document data are structured as shown in Fig. 25 (reference numeral 56).
71 indicates the page). Among these, the page size.

For information on margins, see the true format table below, and
Basic area 5672. The internal areas 5673 are each managed in an area management table.

・True format table 5630 The paper type (A
3. A4, etc.), paper orientation (portrait, landscape).

Manage top, bottom, left, right margins, etc.

- Area management table 5640 The area management table stores data stored within one document (within a page), such as text data and graphic data.

It manages where and in what size various types of data such as graph data are stored within a page.

Therefore, in the area management table, the area setting position within the page is the area upper left X coordinate 5643. Rotation y coordinate 5644, lower right X coordinate 5645. Data type information 5647, which has the same y-coordinate 5646 and also indicates the type of data within the area. Area attribute information 5648 indicating the attributes of the area itself. Area data 5
It has a data pointer 5650 pointing to 660.

Note that the attribute information of the area itself includes whether it is transparent or opaque (if it is opaque, the area below covered by the area becomes invisible), the line type of the area frame, etc.

In addition, in one table, in order to manage the order in which the four sentences are arranged in areas within the same page, the backward pointer 5641 and the forward pointer 5642 are used to link each other. Links in this area link from areas of low priority to areas of high priority, that is, from the lowest area to the highest area within the page. Further, among these, the first n/last areas are each pointed to from the above-mentioned page management table. Further, in the area management table, status information 56 indicating whether the area is being edited or not, and whether an area editing section corresponding to the area data type does not currently exist in the system.
It has 49.

Further, the areas existing within one page can be roughly divided into the following two areas.

(i) Internal area 5673 This area exists on the basic area, and the position and size are determined by the operator's operation. Furthermore, one of various data such as text, graphics, graphs, and images can be stored in the area. Also, edits to this area include creating and updating new areas.

All area editing such as moving, copying, and deleting is possible.

(ii) Basic area 5672 Refers to the part of the page excluding the top, bottom, left and right margins, and when a page is generated by the operator's operation, one main area is also generated.
Always the first area within the page (!A is also the area below)
becomes. In addition, only the text data that becomes the body of the document is stored in this area, and editing for this area is the same as editing for the above areas, allowing new area creation and updating, and movement and copying of one area. Editing operations such as , deletion, etc. are performed by editing operations for pages such as moving, copying, and deleting one page.

- Area data 5660 Data stored within an area, including text and shapes.

Graphs, image data, etc. are stored.

Now, in FIG. 21, initial processing (step 3001
) The next document 1w collection section 561 requests input from the input control section 51 (step 3002).

Then, the input result from the operator is determined (step 3003), and if it is an instruction for the area to be operated,
It is determined from the document data which area is specified based on the specified position within page number 1 and the setting position of the area, and the area number is registered in the operation target area table (step 300
4). The determination method at this time will be explained in more detail using the flow shown in FIG. 22c.

First, it is determined whether or not the indicated position is within the basic area 5672 (step 3201). If it is outside the basic area, there is no area corresponding to the indicated position, so an instruction error is determined. If it is within the basic area, below is the internal area 567 within the page.
Steps 3202 to 3205) determine whether the indicated position is within the internal area in order from the highest area hIi (the last area in the page), and if the result of the determination is that it is within the internal area, the operator's instruction is is regarded as an operation instruction for the internal area, and an internal area instruction flag is set (step 3206). If the area designation flag is O), the operator assumes that the basic area has been designated and processes. Now,
If the indicated position is within the internal area 5673, then it is determined whether the area has already been designated as a target, that is, whether the number ° of the area has already been registered in the operation target area table (step 3207). )
, if the target has already been specified, the next area (the area indicated by the forward pointer 5642 of the area management block of the area currently being determined on the document data) is checked. Also, if it has not been specified yet, it is assumed that the area has been specified and the number of the area is registered in the operation target area table, but at this time, if the basic area has already been specified as the target ( Step 32
08), the number of specified areas in the operation target area table is 568.
4 is cleared to 0 (after the target designation for the basic area is canceled) (step 3209), the internal area number and area type are registered in the operation target area table, and the number of designated areas 5681 is incremented by 1 (step 3210). ), In addition, in the above, when the basic area is registered as an operation target, the designation ′ is forcibly canceled when the basic area and internal area can be specified at the same time, as described later. This is because there will be no area editing corresponding to this. In addition, in the above process, if no internal area is registered, it is determined whether the internal area designation flag is O (step 3212), and if it is 0, there is no internal area at the specified position, and the operator must It is assumed that the area is specified as the target. Next, the number of the basic area is registered in the table, but at this time, it is checked whether this basic area has already been specified as a target (step 3213), and if it has not been specified, then the internal area is specified as the target. If it has been specified, the operation target area table is cleared once (step 3215).
), the basic area number and area type are registered in the operation target area table, and the number of specified areas is set to 1 (step 3216).

Now, if the instruction from the operator is an instruction to release the tank chamber of the area that is being specified as a target, it is determined from the document data which area was specified based on the page number, the specified position within the page, and the set position of the area. , the region number is deleted from the operation target region table (step 3005 in FIG. 21). The determination method at this time will be explained in more detail using the flowchart in FIG. 22d.

First, it is determined whether the designated position is within the basic area (step 3251), and if it is outside the basic area, the operation target area table is unconditionally cleared.

That is, the designation of all areas registered in the table is canceled (step 3258). On the other hand, if it is within the basic area, then steps 3252 and 3253) determine whether the indicated position is within the area in order from the highest area on the page (the last area on the page), and as a result of the determination,
If the area is within the area, it is determined whether the area is registered in the operation target area table (step 3254);
'W If the area number is registered in the table, the area number is deleted from the table (step 3257).On the other hand, if the indicated position is not within the area in step 3253, the area is not registered in the table in step 3254. If so, the process goes through steps 3255 and 3256, and the same determination is made for subsequent areas.

Now, as one or more region designation/cancellation operations are performed, the region editing operations that can be executed will change sequentially, but at this time, the process of switching the enable/disable state of the pull-down menu related to region operations (
Step 3014) in FIG. 21 will be explained using FIG. 22e.

Editing operations on regions can be classified into three types depending on the number of regions designated as operation targets, as shown in FIG. That is, first, the number of areas being specified as a target is determined (step 3301).

If the number of regions is 0, only the pull-down menu for creating a new region is enabled, and all other region editing is disabled (
Step 3302). Also, if the number of areas specified as target is 1, only the pull-down menu for creating a new area will be disabled for the time being.

Enable all other area editing (step 3303
), if the number of areas specified as a target is 2 or more, only move, copy, and delete are enabled, and all other area editing is disabled (step 3304), and if the number of areas specified as a target is 1 Further, it is determined whether the specified area is a basic area (step 3305), and if it is a basic area, attribute changes and size changes are also disabled (step 3306).
Next, it is determined whether the status of the specified area is other than O (step 3307), and if the status is other than 0 (the area is currently being edited, or the area editing unit that can update the area is (if not present in the system)
The update is also invalidated (step 3308). In addition, if the number of specified targets is 1 or more, it is determined whether or not an area with a status of 1 (the area currently being edited) exists among the specified areas (step 3309), and if so, deletion is also disabled. (Step 3310).

Next, the case where the instruction from the operator is an instruction to create a new area (step 3006 in FIG. 21) will be explained based on the flow shown in FIG. 22f.

In this case, the operator instructs new creation by specifying the data name displayed in the pull-down menu, but the text? W eastern part 561 is input control section 51
Step 3401
, it is determined which data has been instructed to create new data (step 3402). At this time, if the instructed data is data to be created as an internal area, then the area setting of the area and the attribute setting of the area are determined. Perform (step 34
03). Then, an area management block is generated based on one or more pieces of information (step 3404), and the area editing section is activated (step 3405) (the activation process will be described later).

Now, if the instruction from the operator is an instruction to update an already created area (step 3007 in FIG. 21), step 22g
As shown in the figure, the number of the area registered in the operation target area table 5686 is obtained (step 3411), and the SFM is executed based on the data type of the area management block from that number.
Step 3412) to obtain the program number from T.
The corresponding area editing section 562 is activated as a task (step 3413).

In the activation of the area editing section 562 in the above, the second
As shown in Figure 2h, first, the document editing unit 561 requests the system control unit 53 to generate a task based on the obtained program number (step 3451), and the task number and the number of the corresponding area are returned as a result. is registered in the active editing task management table (hereinafter abbreviated as ETMT) (step 3452), and the ETMT registers the task number 5688. as shown in FIG. It holds the area number 5689 as a pair, and also has the number of activated tasks 5687 indicating how many area editing units are currently activated. Then, the status of the area management block is changed from 0 to 1 to indicate that the corresponding area is being edited (step 3453). After the above processing, the one-document editing section 561 requests the system control section 53 to start a task (step 3454).

Furthermore, the activation parameters are sent as a message to the area editing unit that activates them (step 3455).

At this time, as startup parameters, the startup mode indicating whether to create a new area or update the area, the task number of the document editing section 561, the task number of the eastern part of the area W to be activated, and, in the case of new creation, the size of the area are transmitted.

If other editing operations are instructed, such as moving or deleting an area, inserting or adding a page, etc., perform the corresponding processing (steps 3008 to 3011 in Figure 21) and wait for the next instruction from the operator. (Step 3002).

Now, if the instruction from the operator is the instruction 1 to change the displayed page, for example, the previous page, 2nd page, etc. (21st
In step 3012) in the figure, the layout of each corresponding page is redisplayed in the window. This layout display process will be explained in more detail using No. 221@.

In displaying this layout, first the paper frame, header, footer, etc. are displayed based on the document data described above (steps 3501 and 3502), and the following areas set within the page are displayed with the highest priority. The area is sequentially displayed starting from the well-organized area (the first area in the page) (steps 3503 to 3514). In displaying this area, first, an area frame is displayed (step 3504), and then an editing program exists for the data in the area. It is determined from the data type number and SFMT in the corresponding area management block (step 3505), and if there is no such area management block, the status of the area management block is changed to 2 (step 3511),
In order to inform the operator that an editing program for this area does not exist in the system, the area is displayed in full black (step 3512), and if there is an editing program in the above, then whether the attribute for the area 4 is transparent or not is displayed (step 3512). If it is opaque, the area is partially cleared (step 3507), and then the data within the area is displayed (step 3508).

Furthermore, after displaying the area, it is determined whether the area is IJ-concentrated (1 or not) based on the status information for the area (step 3509), and if it is being edited, the operator informs the operator that the area is currently being edited by JI. The entire area is shaded to inform the user (step 3510).
). Thereafter, similar processing is performed for all areas existing within the page to be displayed (steps 3513 and 3514).

In addition, the process (step 3013 in FIG. 21) regarding the activation input by the window switching operation, which will be described later, will be described later. Further, if termination is instructed, document editing is terminated, and the details of this process (step 3015 in FIG. 21) will be described later.

Now, in the above, when a new area is created or updated, the sentence IF editing section 561 changes to the area editing section 562.For example, □1
When a request is made to start the graphic data editing section, the system control section 53, in accordance with this request, newly starts the graphic data editing section as a task. The explanation will be based on.

First, the 1-figure data editing unit receives startup parameters via message (step 4001), determines whether the startup mode is new creation or area update (step 4002), and in the case of new creation, initializes the data ( Step 4003), also.

In the case of updating, the data to be updated is called from the storage unit (step 4004), a window is opened (step 4005), and the graphic data is displayed in the window (step 4006), but at this time, the size of the window is is set to a size corresponding to the size of the area, and the task number of the starting document editing section is added to a part of the title of the window, just like the starting document editing section. As a result, when multiple documents are being edited at the same time, and several areas within each document are being edited, which area corresponds to which document is determined as shown in Figure 32.
It can be easily identified by the task number 254 displayed as part of the title of this window. Also, at this time, the display state of one screen will be as shown in No. 3111(b).

The graphic data editing section performs creation and editing of graphic data in accordance with instructions from the operator within the set window (steps 4007 to 4009).

Note that when the operator instructs the graphic data IIi to finish editing within the area, 1 stores the created graphic data in the storage unit 3 (step 4010), closes the window (step 4011), and sends the area editing completion message to the activation source. to the document editing department 561 (step 4012
), the task is ended (step 4013), and this end message includes an end code indicating the end of editing in the area so that the activated document editing section can determine which area editing has ended; Set the task number of the figure editing department itself.

As described above, creation and editing of the entire document and each area can be performed.Next, the operation method and processing contents for switching the editing section by window operation will be explained using Fig. 31 and Fig. 17. do.

First, as shown in FIG. 31(b) and FIG. 3(c), when switching to document layout editing while editing one graphic area, the document editing section 561 Move the mouse cursor 30 onto the window and press the mouse execution button. Based on this input instruction, the input control unit 51 first determines that the specified position is outside the window of the figure editing unit that was being edited, and inputs this input not to the figure editing unit but to the window management unit 51.
Hand over to 2. The window management section 52 is.

It is determined from the position indicated by the mouse and the window management table that the window of the document editing section 561 has been indicated (step 1521), and the task that is using the window that was the topmost until then, that is, the figure editing section, is temporarily suspended. (Step 1522), and saves the display image of the topmost window to the display buffer (Step 1523). Then, display the newly specified document editing section window at the top (step 1524).
, updating the stacking order of the window management blocks (step 1525), and returning an activation code to the task using the window in order to notify the document editing section, which restarts the process, that the window has been switched. 1526), restarts the task using the J' window, ie, the 1 document #g collection (step 1527).

Note that the above-mentioned interruption and restart of the editing section is processed by the system control section 53. Below, Figure 12e and 1
Interrupted based on the flow in Figure 2f.

The restart process will be explained.

When a task interruption request occurs, the system control unit 53
sets the interrupt flag of the TCB corresponding to the specified task (step 1141), determines whether the task is in the READY state (step 1142), and if the task is in the READY state, removes the corresponding TCB from the READY queue and causes the dispatcher to It is prevented from being allocated (step 1143).

The specified corresponding TCH for a task restart request.
If there is a step to reset the interrupt flag of
Connect to the DY queue (step 1153). If the interrupt flag of the TCB is set, the task dispatcher does not start the corresponding task and removes it from the READY queue.

Furthermore, if the basic area is updated from the state shown in FIG. 31(Q), one screen changes as shown in FIG. 31(d). In this state, each editing section can be switched arbitrarily between text, graphics, and layout using the same operation method as described above. For example, when switching between the area editing sections, that is, from text to graphics, the display state of the screen becomes as shown in FIG. 31(e).

Now, when the window is switched as described above, the activation code is returned as input to the restarted task from the window management section.

For example, in the above example, from the graphic editing section to the document editing section 5
61, the 1-document editing section 561 receives the above activation input after restarting, and performs the following processing accordingly (Fig. 22, k).

That is, first, it is determined from the document data whether or not there is an area being edited in the currently displayed page (step 3601).
If there is, there is a possibility that the contents of that area have been updated by editing, so the display flag is set to 1 (step 3602).

If not, set the display flag to 0 in step 3.
603), the layout is redisplayed after the following message processing. Next, a message reception request is made to the system control unit 53, and if there is a message, the following process is performed as a termination process of the corresponding area editing unit (steps 3604 to 3606).

That is, first, the task number of the area editing unit stored in the message and the area number are obtained from the ETMT (FIG. 29) (step 3651), and the status of the corresponding area management block is reset to 0 (step 3652).
), information about the task is sent to ETMT (Figure 29)
Then, the task itself is deleted (step 3653), and finally the task itself is deleted (step 3654). Now, in the above case, if there is no message, it is determined whether the display flag is set to 1 (step 3607).
, if set, the layout of the page is redisplayed (step 3608).

Finally, the second section regarding the termination process in the document editing section 561.
This will be explained using Figure 2n and Figure 12g.

If the operator instructs you to terminate, the above-mentioned ET
Step 3702) to determine whether there is an active editing task based on the MT (FIG. 29).

If so, use the task number from ETMT (Figure 29).

After acquiring the area number (step 3703) and resetting the status of the area to O (step 3704),
A task forced termination request is made to the system control unit 53 (step 3705). Accordingly, the system control unit 53 first requests the resource used by the #H specified task, as shown in FIG. 12g. Step 116
1) A forced termination processing request is made to the window management (step 1162), and the window management unit 52 performs processing similar to the closing processing shown in FIG. 16, and based on the specified task number, the corresponding TCB is set to READY. If connected to a queue, the READY queue header 53
3 and set the TCH state to DORNANT state (step 1163). After the above forced termination processing, the 1-document editing unit 561 deletes the task (step 3706).
).

The above process is repeated for the editing task that is running (step 3707), and when all the running tasks have been forced to terminate, the document data is registered (step 3708).
, close the window that was open in the document collection section (step 3709), send a message to the system management section 57 to the effect that the processing has been completed (step 3710), and end the task (step 3711).
).

In this manner, when a termination request is made to the one-document editing section 561, the area editing sections 562 that are being edited can be terminated all at once.

〔Effect of the invention〕

As described above, in the document creation device of the present invention, editing of data within an area, editing of an area on a layout screen, switching of display parts, etc. can be performed without terminating the functions of each editing part. Since collection operations can be switched between each other, operability in document creation that includes a mixture of multiple types of data is improved.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the configuration of a Japanese word processor to which the present invention is applied, FIG. 2 is a diagram showing an example of a display screen on the display unit, FIG. 3 is a diagram showing the configuration of mouse buttons, and FIG. 4 is a configuration diagram of the icon management table, Figure 5 is a configuration diagram of the program control table, Figure 6 is a configuration diagram of the data name definition table, Figure 7 is a configuration diagram of the window management table, and Figure 8 is a configuration diagram of the task control table. 9 is a diagram showing the READ queue, FIG. 10 is a diagram showing the configuration of the message control table, FIG. 11 is a diagram showing the message reception queue, and FIG. 12 is a diagram showing the processing of the system control unit. Figure 12a is a diagram showing the task generation process, Figure 12b is a diagram showing the task generation process.
12C is a diagram showing task deletion processing; FIG. 12C is a diagram showing task activation processing; FIG. 12D is a diagram showing task termination processing; FIG. 12E is a diagram showing task suspension processing;
Figure f shows the process of restarting a task, Figure 12g shows the process of forced termination of a task, Figure 12h shows the process of sending a message, Figure 121@ shows the process of receiving a message, and Figure 12j shows the process of message reception. The figure shows the process of the dispatcher,
FIG. 13 is a diagram showing the processing of the input control section, and FIG. 14 is a menu management table. A diagram showing the structure and relationships of a pull-down menu table,
Figure 15 is a diagram showing the window opening process, Figure 16 is a diagram showing the window opening process.
Figure 17 shows the process of closing a window, Figure 17 shows the process of switching windows, Figure 18 shows the process of the system management section, Figure 19 shows the process of the file editing section, and Figure 20 shows the process of the file editing section. Figure 21 is a diagram showing the structure of the operation target document table, Figure 21 is a diagram showing the processing of the document editing unit, Figure 22a is a diagram showing the initial processing of the document editing unit, and Figure 22b is a diagram showing support in the initial processing of the document editing unit. Figure 22c is a diagram showing area management table creation processing, Figure 22c is a diagram showing area designation processing in the document editing department, Figure 22d is a diagram showing designation cancellation processing in the document editing department, and Figure 22a is a diagram showing the pull-down menu of the document editing department. Figure 22f is a diagram showing the process for changing the valid/invalid state, Figure 22f is a diagram showing the new area creation process in the document editing section, Figure 22g is a diagram showing the area updating process in the document editing unit, and Figure 22h is a diagram showing the new area creation process in the document editing department. FIG. 22i is a diagram showing the area editing section activation process in the creation and area update processing; FIG. 22i is a diagram showing the layout display process of the document editing section; FIG. Figure 22Q is a diagram showing the region editing unit termination process in the activation process of the document editing unit; Figure 23 is a diagram showing the editing termination process of the document editing unit;
Figure 24 is a configuration diagram of the menu table of the document editing department, Figure 24 is a configuration diagram of document data, Figure 25 is a diagram showing the page configuration,
Figure 26 is a diagram showing the relationship between the number of areas specified as operation targets and executable area editing operations, Figure 27 is a configuration diagram of the support area editing department management table, and Figure 28 is the configuration of the operation target area table. 29 is a configuration diagram of the startup editing task management table. FIG. 30 is a diagram showing the processing of the graphic data editing section, FIG. This is a displayed window display screen. 1... Input section, 2... Display section, 3... Storage section, 4
...Printing section, 5...Control section, 51...Input control section, 52...Window management section, 53...System control section, 54...Print control section, 55...Display control unit,
56... Editorial department, 561... Document editing department, 562.
...Area Editorial Department, 57...System Management Department, 58...
・File editing department. Agent Patent Attorney Katsuma Ogawa, 1 Kuzu, 4th Ward 5th 8m Noboru 9 Showa 5jZ 55Z 53z ImojQ
Il￥1 11th m U3z 5jZ 1st Z Asahi (7z, Rinosa A,) 關12 b■ Ru1zc prisoner (Kusukushi Enoki! Kotoke 7ri seeking jikai 12. (I son name 12e sword 4 convex 1' l f is a (Kusukushita Shibaya 1#T) 1st zbana IZi country 1I 做Go'#IJ憾5Q $ruel nat5 f\l #rl, m eel 170 th zo figure frequency 2z pe hill 221)ヅKudzu 22c6J
J No. ZZl'j: J 7Zc Prisoner G Portrait 22 wo wo Z2 trfJ $23 Illustration history ne bee flower 4f Nunisu Teful 25th Kasumi 2nd Otm Tea 27th Y! J-V? '@#Elf-Full (5FMT)
'm A shike 101 each whisper day 7'

Claims (1)

[Scope of Claims] 1. An input unit for inputting description elements to be described in the document for each area, for a document in which multiple types of description elements are mixed;
In a document creation device comprising a storage section for storing input written elements, and a display section for displaying various written elements stored in the storage means, a page layout of a created document is displayed on the display section, A document editing section that edits the area according to the display, a plurality of area editing sections that create and edit description element data in each area according to the type of description element data, and a document editing section that performs creation and updating. activating means for activating a corresponding area editing section according to the type of description element data of the designated area; and terminating the functions of both the document editing section and the area editing section activated by the activating means. A document creation device characterized in that it is provided with an editorial department switching means for switching without any trouble. 2. In the document creation device according to claim 1, the editing section switching means is configured to switch the plurality of activated area editing sections to each other without terminating the function of any one of the area editing sections. Characteristic document creation device.