JPH0573544A - Document editing device - Google Patents

Abstract

PURPOSE:To enable the coexistence of a columnar writing and horizontal writing mixed document with simple configuration in the Japanese document editing device. CONSTITUTION:This document editing device is provided with a primitive storage part 5 where character, pattern, image, and editing control data are converted to specific data formats respectively and stored as primitives, a line control table 6 which controls the respective primitives hierarchically by lines of the document, a page control table 7, a paragraph control table 8, a chapter control table 9, a document control table 10, and an editing execution part 2 which generates the primitive storage part 5 and the respective tables, etc., and refers to them to shape the document. An intrinsic information of characters for columnar or horizontal writing is imparted to the line control table 6.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a Japanese text editing device in which vertical writing or horizontal writing can be mixed relatively easily.

[0002]

2. Description of the Related Art Recently, Japanese DTP (Desk Top Publishi)
ng), Japanese WP (Word Processor), and the like, are extremely widely used because they have an excellent function of creating and printing Japanese sentences.

Few conventional text editing devices have a function of mixing horizontal writing and vertical writing in one text, and an extremely complicated text even having a function of mixing horizontal writing and vertical writing. It has an editing structure and a user interface.

In such a text editing apparatus, for example, it is necessary to specify an area for vertical writing and format editing with a user interface for a character string to be written vertically on a print screen. Also has a very complicated structure because it has to use a control code.

[0005]

Therefore, in order to create a sentence in which vertical writing and horizontal writing are mixed, the sentence is divided into a plurality of blocks, and vertical writing or horizontal writing can be performed in one block area. A complicated operation for performing so-called format editing is required. Further, there is a problem that it is necessary to prepare a plurality of row management tables in relation to the operation, and therefore the structure is complicated and the load on the CPU becomes large.

An object of the present invention is to solve the above-mentioned conventional problems and to provide a text editing device capable of improving the processing of text shaping.

[0007]

According to the present invention, an input character,
A primitive storage unit that converts each of graphics, images, and edit control data into a predetermined data format and stores the converted data as a primitive, a line management table that manages each primitive for each line of a sentence, and the line management A page management table for managing the table, a section management table for managing the page management table, a chapter management table for managing the section management table, a document management table for managing the chapter management table, the primitive storage unit, And an editing execution unit for creating and referring to each of the above management tables and formatting the text, and a display unit for displaying the text formatting output created by the editing execution unit, for writing vertically or horizontally in the line management table. Characteristic information is added to the character.

[0008]

According to the present invention, since the line management table is provided with vertical or horizontal character-specific information and no control code is used, the editing structure is relatively simple, and the number of line management tables is small. It can be reduced, the load on the CPU can be reduced, and the processing efficiency of text editing can be improved.

[0009]

FIG. 1 is a functional block diagram of a text editing apparatus according to an embodiment of the present invention. In FIG. 1, 1 is a character,
Input means for inputting figures, images, or edit control data for editing instructions, 2 is an edit execution section for performing a predetermined edit in response to input from the input means 1, and 3 is edit of the edit execution section 2. Result display means, 4 is a memory management unit that manages memory use and release requests from the editing execution unit 2, and 5
Is a primitive storage unit that transforms the input characters, figures, images, and edit control data into a predetermined format by the edit execution unit 2 and stores the transformed data, and 6 is stored in the primitive storage unit 5. A line management table that collects line management blocks that manage characters, figures, images, and edit control data for each line of a sentence; 7 is a page management table that collects page management blocks that manage the line management blocks for each page; 8 is the section management table that collects the section management blocks that manage the page management blocks for each section, 9 is the chapter management table that collects the section management blocks that manage the section management blocks for each section, and 10 is the above It is a sentence management table which manages the chapter management block of the chapter management table 9.

FIG. 2 is a block circuit diagram which constitutes the sentence editing apparatus of FIG. 11 is a keyboard, 12 is a CRT as a display device, 13 is a CPU, 14 is RAM, and 15 is RO.
In M, the input unit 1 is operated by the keyboard 11, the primitive storage unit 5, the line management table 6, the page management table 7, the section management table 8, the chapter management table 9 and the text management table 10 are further edited by the RAM 14, and further edited. In the execution unit 2 and the memory management unit 4, the CPU 13 has the ROM 15 and the RA.
This can be realized by executing a program stored in the ROM 15 while exchanging data with the M14, and the display means 3 can use a CRT 12, for example.

Primitives include text (character), figure, image, ruled line, and area primitives as shown in FIGS. 3 to 7, and these are stored in the primitive storage unit 5.

First, FIG. 3 shows the structure of a text primitive. 16 is a pointer to the next primitive connected to the same line, 17 is a character indicating the kind of primitive,
Display of figures, images, ruled lines, areas, etc. In addition, 18 is the character feed amount that indicates the distance to the next primitive on the same line,
Reference numeral 19 is character modification information that represents a halftone type, emphasis, character size, and rotation of characters, and 20 is a kanji / kana code portion that represents a kanji or kana code number.

FIG. 4 shows the structure of ruled line primitives.
Is a relative X coordinate indicating the distance from the left edge of the area frame, 22 is a relative Y coordinate indicating the vertical distance from the upper edge of the area frame, 23 is the left, right, up or down direction of the ruled line, and 24 is Relative X, Y
It represents the length from the coordinate value. For example, if the current relative X, Y coordinates (viewpoint coordinates of the ruled line) are (X0, Y0),
If the ruled line length is 1 and the direction of the ruled line end point is left
(X0-1, Y0), if the direction is down (X0, Y0 + 1)
Becomes

FIG. 5 shows an area primitive for securing a rectangular area. The ruled line primitive shown in FIG. 4, the image primitive shown in FIG. 6, which will be described later, and the graphic primitive shown in FIG. 7 are connected to this area primitive. It is managed by the management block.

Xmax25 is the horizontal length of the rectangular area whose upper left corner is the current point, and Ymax26 is the vertical length. Reference numeral 27 is a pointer to a row management block that manages rows in this rectangular area.

FIG. 6 shows the structure of the image primitives, where Xmax28 is the width of the image area and Ymax29 is the height thereof. The image command 30 is an instruction for an image, such as dithering or emphasis, and the link 31 to the image data is a pointer to the actual state of the image data.

FIG. 7 shows the structure of a graphic primitive. The graphic command 32 is an instruction to move a drawing graphic, for example, to move the current position, a circle, an ellipse, or a line. The figure parameter 33 displays the parameters for the figure command 32. For example, in the case of a circle, the radius and the angle are shown, and in the case of an ellipse, the major axis, the minor axis and the angle are shown.

FIG. 8 shows the configuration of the row management block stored in the row management table 6. Next block link 34 is a pointer to the next line management block, previous block link
35 is a pointer to the previous row management block.
You can easily scroll or back scroll with two pointers.

The primitive head 36 is a pointer to the first primitive connected to the same row, and the primitive tail 37 is a pointer to the primitive at the end of the row connected to the same row. These two pointers can easily manage the primitives on the same row. The line pitch 38 is a line interval with the next line, that is, the next line management block, and the coordinate of the line in the page can be obtained by taking the sum from the first line of the page. The line head relative X / Y coordinate 39 represents the line direction coordinate from the left margin of the page, that is, the line direction start coordinate of the first primitive, and the line end relative X / Y coordinate.
40 is the coordinate in the row direction of the last primitive connected to the row.

The line information 41 is used for information about lines such as vertical writing / horizontal writing, ruby, prohibition, etc., and the heading line information 42 is used for identifying whether the line is a large heading, a middle heading, or a small heading.
The next subheading link 43 is a pointer to the row management block of the next subheading row, and is for facilitating paragraph search within the page.

FIG. 9 shows the structure of the page management block stored in the page management table 7. The next block link 44 points to the next page management block, and the previous block link 45 points to the immediately preceding page management block. Pointers, with which you can easily control scrolling or backscrolling. The line head 46 is a pointer to the row management block of the first row connected to the same page, and the line tail 47 is a pointer to the row management block of the last row connected to the same page. The row management block can be easily managed.

The page number 48 indicates the total page number from the first page in the section, and the page layout 49 indicates in the document management table 10 how many columns the layout of the page is, vertical writing mode or horizontal writing mode. Is a pointer to the entity of the page layout managed by the page layout link of.

The subheading format 50 is a pointer to the subheading format managed by the subheading format link in the document management table 10 that determines the subheading format such as the area in the page and the character type.
The subheading line link 51 is a pointer to the line management block of the subheading line in the page.

FIG. 10 shows the structure of the section management block stored in the section management table 8. The next block link 52 is a pointer to the next section management block, and the previous block link.
53 is a pointer to the previous clause management block, these pointers facilitate scrolling or backscrolling within a clause. The page head 54 is a pointer to the page management block of the first page connected in the same section, and the page tail 55 is a pointer to the page management block of the last page connected in the same section. You can easily manage the page management block inside.

The page count 56 shows the number of pages in the section, and the section No. 57 shows the total section number from the first section in the chapter. The medium heading format 58 is a document management table 10 that determines heading formats such as section areas and character types.
Is a pointer to the medium header format data entity managed by the medium header format link in
The middle heading line link 59 is a pointer to the line management block in which the middle heading in the section is designated.

FIG. 11 shows the structure of the chapter management block stored in the chapter management table 9. The next block link 60 is shown in FIG.
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 pointers facilitate scrolling or backscrolling within a chapter.

The section head 62 is a pointer to the section management block of the first section connected to the same chapter, and the section tail 63 is a pointer to the section management block of the last section connected to the same chapter. Management of section management blocks in chapters becomes easy. The start page link 64 is a pointer to the page management block of the start page.
No. 65 shows what chapter is in the relevant chapter. The large headline format 66 is a pointer to the large headline format data entity managed by the large headline format link in the document management table 10 that determines the heading format of the chapter area, character type, etc., and the large headline row link 67 is the large headline. Is a pointer to the specified row control block.

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 same document, and the chapter tail 69 is the chapter of the last chapter in the same document. Pointers to control blocks, which make it easier to manage chapter control blocks in a document. 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 large headline format link 71 is a pointer to a data group that stores the format of the large headline area, character type, etc., and manages a plurality of large headline format data. The middle headline format link 72 is a pointer to a data group that stores the appearance of the middle headline area, character type, etc., and manages a plurality of medium head format data.

The subheading format ring 73 is a pointer to a data group in which the format of the subheading area and character type is stored, and manages a plurality of subheading format data. The format link 74 is a pointer to data that stores a format such as a document indent and a tab, and the document information 75 is used as information about the document.

FIG. 13 is an overall schematic view in which the relationships between the tables and blocks shown in FIGS.
Indicates that the nodes and structures are hierarchically configured. In FIG. 13, 76 is a primitive, 77 is a row management block,
78 is a page management block, 79 is a section management block, 80 is a chapter management block, 81 is a document management table, 82 is a primitive storage unit, 83 is a line management table, 84 is a page management table, 85 is a section management table, and 86 is a section management table. This is a chapter management table.

FIG. 14 is a flowchart for referring to or updating the primitive storage unit 5, the row management table 6, and the page management table 7 with the above-described configuration to insert a text. Each operation will be described in abbreviated form.

First, a character is input by the character input means 1 (S
1) The input character string creates a text primitive as shown in FIG. 3 (S2). If the input mode is the insert mode (S3, Y), insert processing is performed (S4). Since the insertion processing inserts between the text primitive connected to the insertion line management block in the line management table 6 and the text primitive immediately before it, the pointer of the next primitive link 16 in FIG. Rewrite (setting of line end coordinates) (S5). After that, it is checked whether the line length of the line inserted by the inserted text exceeds a predetermined line length (S6), and if the next line does not exceed the page length (S7N), the next line insertion process ( Proceed to step S9), and if it exceeds, insert to the next page and proceed to next page processing.
(S8). In S9, the remaining text primitive of the previous line is inserted at the beginning of the line management block of the next line, and the process returns to S5.
Repeat until the line length of 6 does not exceed.

As can be seen from the above, the tables are in a close relationship with each other, and the basic editing operations such as insertion and deletion can be easily processed.

FIG. 15 is a flow chart for creating the clause management table 8 and shows the movement of the management information in the layers below the page management table 7.

First, in order to create the section management table 8, a middle heading line is first designated (S10). By this designation, a middle headline is marked in the headline line information 42 of the line management block in FIG. 8 (S11). Next, if there is no large headline line in the page, the line tail 47 in the immediately preceding page management block is displayed.
To the line management block just before the middle heading line.
(S12), by connecting the line head 46 of the page management block to the line management block of the heading line therein,
The middle headline is bound to the page management block.

Next, the page head 54 shown in the section management block of FIG. 10 is connected to the page management block having the middle heading, and the page tail 55 of the immediately preceding section management block is connected to the page management block having the middle heading. Connect to the previous page management block (S13). Furthermore, by connecting the line management block of the middle heading line to the middle heading line link 59 of the section management block, it is possible to manage the sentence in units of sections.

FIG. 16 is a flowchart showing the creation of the chapter management table. First, the main heading line is designated to create the section management table (S14). By this designation, a large headline is marked in the headline line information 42 of the line management block in FIG. 8 (S15). Next, the line tail 47 in the page management block immediately before the page management block is connected to the line management block immediately before the large heading line (S16), and the line head 46 is connected to the line management block of the large heading line. Binds the heading line to this page management block.

Next, the page head of the section management block in FIG.
The page management block 54 is connected to the page management block having the major heading, and the page tail 55 in the preceding section management block is connected to the page management block immediately before the page having the major heading (S17). Finally, the section head in the chapter management block in Figure 11
Connect 62 to the section management block that made the headline (S1
8), connect the section tail 63 in the previous chapter management block to the section management block immediately before the section that made the headline. further,
The page management block specifying the major headline is connected to the start page link 64, and the line management block of the major heading line is connected to the major heading line link 67. As described above, the chapter is managed for each sentence.

As described above, the present invention hierarchically manages chapters and sections of a document using the chapter management table, section management table, page management table, and line page management table.
It is possible to easily mix vertical / horizontal writing in the row information 41 of the row management table in FIG. 8 by executing an editing instruction for data such as characters, figures, images, and ruled lines while referring to or changing these management tables. become.

If the line information indicates horizontal writing, the line start relative X / Y coordinate 39 indicates the line start X coordinate, the line end relative X / Y coordinate 40 indicates the line end relative X coordinate, and the line pitch 38 indicates the feed amount in the Y axis direction. Similarly, if the line information 41 is vertical writing, the line head relative X /
The Y coordinate 39 indicates the line beginning Y coordinate, the line end relative X / Y coordinate 40 indicates the line end relative Y coordinate, and the line pitch 38 indicates the line feed amount in the X axis direction. At this time, the Kanji / Kana code 20 of the text primitive of FIG. 3 is the line information of the line management table of FIG.
According to 41 vertical writing / horizontal writing, printing will be performed using the font for vertical writing / horizontal writing.

[0041]

As described above, in the document editing apparatus of the present invention, it is easy to add the vertical writing / horizontal writing information to the line management table, paying attention to the fact that each character has information unique to the character. With the configuration, it is possible to mix vertical writing / horizontal writing relatively easily and improve the processing efficiency of sentence shaping.

[Brief description of drawings]

FIG. 1 is a functional block diagram of a document editing apparatus according to an embodiment of the present invention.

FIG. 2 is a block circuit diagram of FIG.

FIG. 3 is a configuration diagram of a text primitive of an essential part of the present invention.

FIG. 4 is a configuration diagram of a ruled line primitive that is an essential part of the present invention.

FIG. 5 is a configuration diagram of a region primitive of an essential part of the present invention.

FIG. 6 is a configuration diagram of an image primitive of an essential part of the present invention.

FIG. 7 is a configuration diagram of a graphic primitive that is an essential part of the present invention.

FIG. 8 is a configuration diagram of a row management block which is a main part of the present invention.

FIG. 9 is a configuration diagram of a page management block of the essential part of the present invention.

FIG. 10 is a configuration diagram of a section management block of the essential part of the present invention.

FIG. 11 is a configuration diagram of a chapter management block of the essential part of the present invention.

FIG. 12 is a configuration diagram of a document management table of a main part of the present invention.

FIG. 13 is a schematic diagram showing an entire management table of the present invention.

FIG. 14 is a flowchart showing insertion of text in the present invention.

FIG. 15 is a flowchart for creating a clause management table in the present invention.

FIG. 16 is a flowchart for creating a chapter management table in the present invention.

[Explanation of symbols]

1 ... Input means, 2 ... Editing execution unit, 3 ... Display means,
4 ... Memory management unit, 5 ... Primitive storage unit, 6 ...
Line management table, 7 ... Page management table, 8 ... Section management table, 9 ... Chapter management table, 10 ... Document management table.

Claims (1)

[Claims] 1. A primitive storage unit that converts each of input characters, figures, images, and edit control data into a predetermined data format and stores the converted data as a primitive, and manages each primitive for each line of a sentence. Row management table, a page management table that manages the row management table, a section management table that manages the page management table, a chapter management table that manages the section management table, and a document that manages the chapter management table The line management includes a management table, the primitive storage unit, an editing execution unit that creates and references the management tables, and edits a text, and a display unit that displays the text formatting output created by the editing execution unit. A text editing device characterized in that information unique to characters for vertically or horizontally writing is added to a table.