JPH04113450A - Sentence editing device - Google Patents

Abstract

PURPOSE:To facilitate such complicated editing tasks as the shifts of charts, graphics and images, and the tabulation, etc., by defining a simple primitive, i.e., an area primitive. CONSTITUTION:An input means 1 is provided together with an editing execution part 2, a display means 3, a memory control part 4, a primitive storage part 5, a line control table 6, a page control table 7, a paragraph control table 8, a chapter control table 9, and a sentence control table 10. An area primitive is applied and used for security of a rectangular area. Meanwhile a text primitive, a graphic primitive, and an image primitive show the characters, the graphics, and the images respectively. The area primitive is provided with a pointer pointing a line control block where the line control is applied to the secured rectangular area. Thus the same control is secured as the line control carried out in the pages. As a result, the changes of charts and the tabulation are facilitated together with the shifts of the graphics and the images.

Description

[Detailed Description of the Invention] (Industrial Application Field) The present invention provides a method for inputting character strings such as sentences, ruled lines, and figures.
The present invention relates to a text editing device that formats text into a display format.

(Prior Art) In recent years, text editing devices such as Japanese DTP and Japanese word processors have been widely used as devices for formatting texts, tables, and figures. Such text editing devices generally have a ruled line editing function.

(Problem to be Solved by the Invention) However, the above-mentioned ruled line editing function treats ruled lines on the same level as characters, and does not process ruled lines and characters within a table as data attached to the table. In some cases, the ruled lines may shift when you delete or add characters within them, and in many cases, tables with ruled lines (including the characters within the ruled frame) cannot be moved to a desired position, and even if they are However, there was a problem in that it required complicated procedures.

The present invention solves the above-mentioned problems and provides a text editing device that allows easy tabulation, change of table layout, and movement of figures and images.

(Means for Solving the Problems) In order to solve the above problems, the present invention introduces region primitives, text primitives represent characters, graphic primitives represent shapes, image primitives represent images, and the region The primitive is a primitive whose purpose is to secure a rectangular area. This area primitive is provided with a pointer to a line management block for performing line management of the secured rectangular area, and management similar to line management within a page is performed.

(Function) With the above configuration, each primitive attached to a region primitive is processed as one piece of data, so if you move the region primitive to a certain position, the original table, figure, or image can be moved to the destination. Can be completely reconstructed. In addition, since the ruled line primitive is defined as a type of vector data that has directions only in the vertical and horizontal directions, there is no effect when inserting or deleting character strings in the table, so editing of characters in the table can be done easily. I can do it.

(Example) An example of the present invention will be described with reference to FIGS. 1 to 20.

FIG. 1 is a functional block diagram of a text editing device according to the present invention. The text editing device includes an input means 1 having means for inputting and editing instructions for characters, figures, and images, and an editing execution unit 2 that performs predetermined editing on the characters, figures, images, and editing instructions inputted from the input means 1. , a display means 3 for making the result of text editing by the editing execution section 2 visible to the user of the device, and a memory management section 4 for managing the use and release of memory required by the editing execution section 2; The editing execution unit 2 transforms input characters, figures, images, and editing control data into a predetermined data format, and the primitive storage unit 5 stores the transformed data; the characters stored in the primitive storage unit 5; A row management table 6 that collects row management blocks that manage graphics, images, and control data for each row, and a page management table 7 that collects page management blocks that manage the row management blocks of the row management table 6 for each page. , a node management table 8 that collects node management blocks that manage the page management blocks of the page management table 7 for each node.
, a chapter management table 9 that collects chapter management blocks that manage the chapter management blocks of the chapter management table 8 for each chapter, and a document management table 10 that manages the chapter management blocks of the chapter management table 9.

FIG. 2 is a circuit block diagram of a text editing device according to the present invention, which includes a keyboard 11, a cathode ray tube display (hereinafter referred to as CRT) 12, a central processing unit (hereinafter referred to as CPU) 13, and a random access memory (hereinafter R
AM) 14 and read-only memory (hereinafter R)
(referred to as OM).

To explain the operation of the text editing device configured as above, the input means 1 shown in FIG. 1 is performed by the keyboard 11 shown in FIG. , the page management puller, the section management table 8, the chapter management table 9, and the document management table 10 are written to the RAM 14, and the editing execution section 2 and the memory management section 4 are
4 and executes the program stored in the ROM 15, and the display means 3 displays the data on the CRT display 12.

FIG. 3 shows the structure of text primitives stored in the primitive storage section 5. As shown in FIG.

The text primitive has a next primitive link 16, which is a pointer to the next primitive connected to the same line;
The primitive type is text.

Type 17 indicating that it is a figure 2 image, ruled line, or area;
Character advance amount 18 that represents the distance to the next primitive, character modification information 1 that represents the character screen type, emphasis, character size, and rotation
9 and a kanji/kana code section 20 representing a kanji or kana number.

FIG. 4 shows the configuration of ruled line primitives stored in the primitive storage section 5. As shown in FIG.

The ruled line primitive has the same next primitive link 16 and type 17 as above, a relative X coordinate 21 indicating the distance from the left edge of the area frame, a relative Y coordinate 22 indicating the vertical distance from the top edge of the area frame, and a relative Y coordinate 22 indicating the vertical distance from the top edge of the area frame. and a vertical direction 23 and a ruled line length 24 from the relative X and Y coordinate values. Note that the ruled line length 24 is calculated by assuming that the current relative X, Y coordinates (viewpoint coordinates of the ruled line) are (X-+y).
When is 1, the end point coordinates of the ruled line are (
X. -+1y. ), if direction 23 is down (X6 +
y6++).

FIG. 5 shows an area primitive for securing a rectangular area, which is also stored in the primitive storage unit 5. The area primitive is the same next primitive link 1 above.
6 and type 17, horizontal length X max 25 and vertical length Y max 26 of a rectangular area whose upper left corner is the current point, and a link 27 to a row management block that manages rows in this rectangular area. . Note that the ruled line primitive shown in FIG. 4 above, the image primitive shown in FIG. 6 below, and the graphic primitive shown in FIG. 7 below are primitives managed by a row management block connected to an area primitive.

FIG. 6 shows the configuration of image primitives stored in the primitive storage section 5. The image primitive has the same next primitive link 16 and type 17 as above, the width of the image area Xmax28, and the vertical width of the image area Y
max29, image processing, e.g. designing,
It consists of an image command 30 that instructs emphasis, etc., and a pointer 31 that links to the image data, which is a pointer to the entity of the image data.

FIG. 7 shows the configuration of graphic primitives stored in the primitive storage section 5. The graphic primitive has the same next primitive link 16 and type 1 as above.
7, figure command 32 and figure command 3 which instruct drawing figure, for example, movement of current position, circle, ellipse, line, etc.
For example, in the case of a circle, it is composed of graphic parameters 33 such as the radius and angle, and in the case of an ellipse, the major axis, minor axis, and angle.

FIG. 8 shows the configuration of the row management ring block stored in the row management table 6.

The next block ring 34 is a pointer to the next row management block, and the previous block link 35 is a pointer to the previous row management block.These two pointers are used to scroll,
Backscrolling can be done easily. The primitive head 36 is a pointer to the first primitive connected to the same line, and the primitive tail 37 is a pointer to the last primitive connected to the same line.These two pointers allow easy management of primitives in the same line. Line pitch 38 is the vertical distance from the next line, that is, the next line management block, and by summing this value from the first line of the page, you can find the vertical coordinate in the page. .

The line head relative X coordinate 39 represents the coordinate in the line direction from the left margin of the page. That is, the starting coordinate in the row direction and the row end relative X coordinate 40 of the first primitive are the coordinates in the row direction of the last primitive connected to that row. The line information 41 includes information regarding lines such as Bungyo, Ruby, Kinsoku, etc.
The heading line information 42 is used to identify whether the line is a large heading, medium heading, or small heading.

The main heading line link 43 is a pointer to the line management block of the next subheading line, and is intended to facilitate paragraph search within the page.

FIG. 9 shows the configuration of a page management block stored in the page management table 7.

The next block link 44 is a pointer to the immediately following page management block, and the previous block link 45 is a pointer to the immediately previous page management block. These two pointers can easily control page scrolling and page backscrolling.

The line head 46 is a pointer to the line management block of the first line connected to the same page, and the line tail 47 is a pointer to the line management block of the last line connected to the same page. Easily manage row management blocks.

The page number 48 indicates the total number of pages from the first page in the direction. The page layout 49 is a pointer to the actual page layout managed by the page layout link in the document management table 10, which indicates the number of columns, vertical layout, or horizontal layout of the page layout. . The subheading format 50 is a pointer to the subheading format managed by the subheading format link in the document management table that determines the subheading format (area, character type, etc.) within the page. The subheading row link 51 is a pointer to the row management block of the subheading row within the page.

FIG. 10 shows the structure of the knot management block stored in the knot management table 8.

The next block link 52 is a pointer to the next node management block, and the previous block link 53 is a pointer to the previous node management block.These two pointers facilitate linear scrolling and backscrolling. The page head 54 is a pointer to the page management block of the first page connected in the same direction, and the page tail 55 is
This is a pointer to the page management block of the last page connected in the same direction. With these two pointers, page management blocks in the same direction can be easily managed. The page count 56 indicates the number of pages in the thread direction. Verse number 57
indicates the total number of copies from the first clause of the intention.

The medium heading format 58 is a pointer to the medium heading format data entity managed by the medium heading format link in the document management table 10 that determines the heading format (area, character type, etc.) of the section. The middle heading line link 59 is a pointer to the line management block in which the middle heading is specified.

FIG. 11 shows the structure of the chapter management block stored in the chapter management table 9.

The next block link 60 is a pointer to the next chapter management block, and the previous block link 61 is a pointer to the previous chapter management block. These two pointers allow easy scrolling and backscrolling as desired.

The clause head 62 is a pointer to the clause management block of the first clause connected to the same intention, and the clause tail 63 is a pointer to the clause management block of the last clause connected to the same intention. You can easily manage the intention clause management blocks. Start page link 64 indicates a pointer to the start page management block. The chapter number 65 indicates which chapter the corresponding amount is. The major heading format 66 is a pointer to the major heading format data entity managed by the major heading format link in the document management table that determines the chapter heading format (area, character type, etc.). The major heading row link 67 is a pointer to the row management block in which the major heading is specified.

FIG. 12 shows the structure of the document management table 10.

The chapter head 68 is a pointer to the chapter management block of the first chapter in the document, and the chapter tail 69 is a pointer to the chapter management block of the last chapter in the document. Blocks can be easily managed.

The page layout link 70 is a pointer to a data group that stores page layout data, and manages a plurality of page layout data.

The main heading format link 71 specifies the main heading format (
The medium heading format link 72 is a pointer to a data group that stores the format of medium headings (area, character type, etc.) and stores multiple large heading format data. The subheading format link 73 is a pointer to a data group that stores the format of the subheading (area, character type, etc.), and manages the plurality of subheading format data, respectively.

The format link 74 is a pointer to data that stores the document format (indentation, tabs, etc.). Document information 75 is used for information regarding documents.

FIG. 13 is an overall schematic diagram for better viewing the relationship between the tables and blocks shown in FIGS. 3 to 12. This shows that documents, chapters, sections, and structures are organized hierarchically. The primitive 76, the line management block 77, the page management block 78, the section management block 79, and the chapter management block 80 are part of the document management table 1.
0, the primitive storage unit 5, line management table 6, page management table 7, clause management table 8, and chapter management table 9 are linked to each other.

Next, the operation of each functional block will be explained using a flowchart.

FIG. 14 shows the primitive storage section 5 and the row management table 6.
, which shows a flowchart for inserting text by referring to or updating the page management table 7. This flowchart will help you better understand the role of each table, so it will be explained below. First, when characters are input by operating the keyboard 11 (step A), the entered character string is
Create the text primitives shown in the figure (Step B
). Next, if the input mode is the insertion mode (step C), insert processing is performed (step D) and line end coordinates are set (step E). Note that the insertion process inserts between the text primitive connected to the inserted row management block in the row management table 6 and the text primitive immediately before it, so the pointer of the next primitive link 16 in FIG. Reupholster.

Next, it is checked whether or not the column length of the inserted line exceeds a predetermined column length as a result of inserting the text (step F), and if it does not exceed the predetermined column length, the insertion operation is terminated (step G). On the other hand, if the length exceeds the page length, a check is made to see if the next line exceeds the page length (step H), and if the length exceeds the page length, the process proceeds to the next page for inserting it into the next page (step 2). Next, the remaining text primitives of the previous line are inserted at the beginning of the line management block of the next line (step J), the process returns to step E, and step F is repeated until the column length is no longer exceeded.

As described above, each table is closely related to each other, and basic editing operations such as insertion and deletion can be easily processed.

Next, the creation of the clause management table 8 will be explained with reference to the flowchart shown in FIG. Note that this flowchart shows the movement of management information in the hierarchy below the page management table 7.

In order to create the section management table 8, first operate the keyboard 11 and specify a middle heading line (step K).
, marks the middle heading in the heading line information 42 of the line management block in FIG. 8 (step L), and if there is no main heading line in the page, the line tail 47 in the immediately preceding page management block is marked as the corresponding middle heading line. By connecting the line head 46 of the page management block to the line management block immediately before the page management block (step M), the middle heading line is bound to this page management block. Next, the page head 54 shown in the management block in FIG. 10 is connected to the page management block for which the middle heading has been created, and the page tail 55 of the immediately previous section management block is connected to the page management block immediately before the page management block for which the middle heading has been created. Connect to block. Furthermore, by connecting the line management block of the middle heading line to the middle heading line link 59 of the clause management block (step N), management of the text in units of clauses is realized.

Next, the creation of the chapter management table 9 will be explained with reference to the flowchart shown in FIG.

First, in order to create the section management table 8 mentioned above, a major heading line is specified (step ○), and the major heading is marked in the heading line information 42 of the line management block in Figure 8 (
Step P), Next, connect the line tail 47 in the page management block immediately before this page management block to the line management block immediately before this main heading line, and connect the line head 46 to the line management block of the main heading line. By connecting to (step Q), this large heading line is bound to this page management block. Next, connect the page head 54 of the section management block in Figure 0 to the page management block where the main heading was created, and connect the page tail 55 in the immediately previous section management block to the page management block immediately before the page where the main heading was created. Connect to block (step R). Finally, connect the section head 62 in the chapter management block in FIG. 11 to the section management block where the major heading was made, and connect the section tail 63 in the immediately previous chapter management block to the section management block immediately before the section where the major heading was made. Connect to. Further, the page management block specifying the major heading is connected to the start page link 64, and the line management block of the thick heading line is connected to the major heading line link 67 (step S).

This makes it possible to manage texts by chapter.

In this way, chapter management table 9, section management table 8,
Chapters and sections of a document can be managed hierarchically using the page management table 7 and the line management table 6. While referring to or changing the above four management tables 9, 8, 7 and 6, input data such as characters, figures, 2 images, etc. is edited and displayed.

Next, the region primitive according to the present invention will be explained with reference to FIGS. 17 to 20.

FIG. 17 is an example of a structural representation including area primitives.

In the figure, a text primitive 81 in the first row is derived from a plurality of text blocks 82 indicating characters, and a text primitive 81 in the next row is derived from an area primitive 83 indicating a table area and a text block 82, and further from the above-mentioned area. The primitives 83 each include a ruled line primitive 85 made up of a plurality of ruled line data 84 and a text primitive 81 to be inserted into a table.

In order for the structural representation in FIG. 17 to become a graphical representation as shown in FIG. 18, the character feed amount 18 of the text primitive 81 in FIG. 3, the line pitch 38 of the line management block in FIG.
The ruled line length 24 and ruled line coordinates 21 and 22 of the ruled line primitive 84 in FIG. 4, and the area primitive 83 in FIG.
The area coordinate tank and vertical lengths 25 and 26 are set. Here, to move the table between the characters "A" and "I" as shown in Figure 19, use a-b, c as shown in Figure 17.
-d, d-e chain is cut, a- shown in Fig. 20
The movement of each primitive is completed by simply connecting d, d-b, and ce. The coordinate value can be obtained by adding the horizontal length 25 of the region primitive to the character feed amount 18 of the text primitive "A".

Figure 19 shows the structural representation after movement.

As you can see from the above explanation, the ruled line data connected below the area primitive 83 and the coordinate values of the text primitives are based on the area primitive, so there is no need to perform any operations even if you move the table. The graphical representation of region primitives is kept intact. Moreover, since character editing within the ruled line frame is completely independent from the main text, the coordinate values of the characters can be easily determined. The same can be said of graphic primitives and image primitives below area primitives.

(Effects of the Invention) As explained above, according to the present invention, by defining a simple primitive called an area primitive, complex editing such as moving tables, figures, images, and table formatting can be easily realized. A document editing device that greatly improves the processing efficiency of text formatting can be obtained.

[Brief explanation of the drawing]

1 and 2 are functional block diagrams and circuit block diagrams of a text editing device according to the present invention, and FIGS. 3, 4, 5, 6, and 7 are respectively stored in a primitive storage unit. Figure 8 is a diagram showing the configuration of text primitives, ruled line primitives, area primitives, image primitives, and figure primitives; Figure 8 is a diagram showing the configuration of the line management block stored in the line management table; Figure 9 is the page management block stored in the page management table. Block configuration diagram, 10th
Figure 11 is a configuration diagram of the section management block stored in the section management table, Figure 11 is a configuration diagram of the chapter management block stored in the chapter management table, Figure 12 is a configuration diagram of the document management table,
Figure 13 is an overall schematic diagram of Figures 3 to 12, Figure 14,
Figures 15 and 16 are flowcharts for inserting text, setting medium headings, and setting main headings, respectively.
Figures 7 and 18 are examples of structural representations that include area primitives and their graphical representations, Figure 19 is a graphical representation after the table in Figure 18 has been moved, and Figure 20 includes the area primitives in Figure 19. This is an example of structural expression. 1... Input means, 2... Edit execution unit, 3...
Display means, 4... Memory management unit, 5... Primitive storage unit, 6... Row management table, 7.
...Page management table, 8...Section management table,
9...Chapter management table, 10...Text management table, 11...Keyboard, 12...Cathode ray tube display (CRT), 13...Central processing unit (
CPU) 14...Random access memory (RAM)
), 15. Read-only memory (iqoM), 1
6...Next primitive link, 17...Type, 1
8...Character feed amount, 19...Character modification information, 20
...Kanji/kana code part, 21...Relative X coordinate,
22...Relative Y coordinate, 23...Direction, 24...
・Ruled line length, 25...Horizontal length (Xmax), 26
...Vertical length (Ymax), 27...Link to row management block, 28...X max, 29...
Y max, 3o...image command, 31...
Link to image data, 32...Graphic command, 33
...Figure parameter, 34...Next block link, 35...Previous block link, 36. Primitive head, 37... Primitive tail, 38
...Line pitch, 39...Relative X coordinate of the beginning of the line,
40... Line end relative X coordinate, 41... Line information, 4
2... Heading line information, 43... Seishin heading line link, 44... Next block link, 45... Previous block link, 46... Line head, 47... Line tail, management block, 81... - Text primitive, 82... Text block, 83... Area primitive, 84... Ruled line data, 85... Ruled line primitive. Patent applicant Matsushita Electric Industrial Co., Ltd.

Claims (1)

[Claims] In order to edit text, there is a primitive storage unit that stores data converted from characters, figures, images, and editing control data into a predetermined data format as primitives, a row management table that manages each primitive row by row, and a row management table. A page management table that manages tables, a section management table that manages each page management table, a chapter management table that manages each section management table, a document management table that manages each chapter management table, and the primitive storage section described above. , an editing execution unit that creates and refers to the above-mentioned tables and formats text, and a display means that displays the result of text formatting by the above-mentioned editing execution unit. A text editing device characterized by binding image data, figure data, ruled line data, and character data to primitives.