JPH01222368A - Input editing method - Google Patents

Abstract

PURPOSE:To perform proofreading more correctly and more efficiently by generating a document file having been proofread by proofreading an inputted document file, and next, generating a second document file having been proofread separately, and comparing the corrected parts of two files. CONSTITUTION:A line address code to maintain an initial line address even if increase or decrease is generated in one line on account of the proofreading is inserted into the optional position of the document file. Then, by inserting further a correction code in the proofread part, two files (proofread file and second document file) which were proofread separately are generated, and the proofread parts are compared, and the mistake of the proofreading is corrected. Thus, proofreading work having been influenced hitherto by the ability or the degree of skill of a worker can be performed correctly and efficiently.

Description

[Detailed Description of the Invention] [Industrial Application Field 1] The present invention is applicable to input devices of phototypesetting machines, word processors,
This invention relates to an input 11IA collection method that makes it possible to easily check whether there are any errors in the proofreading due to human error or the like when inputted document data is proofread in a device such as a workstation.

[Prior art and its problems] When proofreading input document data, there is a risk that errors may occur in the proofreading due to input errors or the like. Conventionally, the accuracy of calibration depends on the skill level and ability of the operator, and it is difficult to reliably eliminate calibration errors.

Output the calibrated results, check 'ft1, and calibrate! Although it is possible to consider methods such as eliminating errors, such a method has the problem of not being able to confirm whether the errors can be reliably eliminated since there may be oversights, and the problem is that work efficiency decreases.

[Means for Solving the Problems] Therefore, in the present invention, in order to reliably and efficiently proofread document data that has been created, set codes and character codes that indicate character niceness, font, layout, etc. When proofreading a document file created by inserting a line number code indicating the line address of each code into the document data configured with and a step of storing a proofread document file created by inserting a correction code indicating the correction start point and correction end point; reading the document file and making the same corrections as those made to the proofread document file; Adding a correction code and storing it as a second document file; and (2) reading the proofread document file or the second document file to detect the correction code, and detecting the correction code in the correction code corresponding to the 4th to 46th line address of the correction No. 11. A step of detecting the line address of the two-sentence circular file and comparing the contents in the same line address of both files; If there is a discrepancy in the comparison step, the proofreading document file or the second one is detected.
It is characterized by a process of re-correcting one side of the document file and outputting it.

[Operation 1] In the present invention, an input document file is proofread to create a proofread document file, and then a second document file is created which has been separately proofread, and the two files are corrected. By comparing the parts and, if the contents of the corrected parts do not match, correcting one of the two files, the proofreading can be executed more accurately and efficiently.

[Miura Example 1 FIG. 1 is a flow diagram illustrating an example of the present invention.

SL: Input the character code and set code (coded information such as character size, font, layout, etc.) and create a preface file that does not indicate the line address of each code but inserts the line address code. , the document file is stored in the auxiliary storage unit (Fig. 2
4) and store it.

Proofread the document file created in S22SL, including the line address code, and if there are any corrections, insert the specified correction and the correction code indicating the correction start point and correction end point. The created proofread document file is created and temporarily stored in the auxiliary storage section 24.This proofread document file is created in another 'JAN and is temporarily stored in a floppy disk or the like. 21).Hereinafter, this case will also be referred to as copying.

S3: Transfer the document file created in Sl from the auxiliary storage unit 24 to J'
:, read it out to the memory/II (FIG. 2, 23) and prepare to perform calibration again.

S4: Read the 52cm created proofread text file and search to see if there is a correction code inserted at the correction start point and correction end point of the corrected part. If there is, proceed to S5; if not, proceed to 811. .

S5: When the correction code is read out by searching in S4, find the line address of the line where the correction code is located, and read the line in the direction of this line address from the sentence file prepared in S3 above. ,
It is displayed on the screen of the display unit (FIG. 2 28). In other words, use the line address code to determine which line (line address) of the corrected document data stored in the corrected document file the line with the correction code is, and if it is the Sth line, then the main memory The sentence 1 stored in section 23 (recalls the Sth line from the file and displays it.As will be described later, the line address code remains the first added line address no matter how it is modified. Since the row address is maintained, no matter how you modify it, the row address will not change.

S6: In accordance with the operator's instructions, the same corrections as those made in S2 are added to the necessary locations of the lines of the Bunzuki file displayed at 85 (read out to the main storage unit 23), and the corrected state is saved. Display on the display screen. Furthermore, correction codes are inserted at the start and end points of the correction, and the corrected document data is stored in the main storage unit 23 as a second sentence 1 file.

S7: The second Bungetsu 7 created by modifying it in S6? The data comparison unit (Fig. 2 27) checks whether the contents of the revised part of the file match the contents of the revised part of the proofread document file modified in S2.
Compare and judge, and if they match, read out the next correction code.
Proceed to step 4, and if they do not match, proceed to S8.

In addition, in the above two files, the number of characters Jj from the beginning of the line to the correction code ([[start point]) and the correction code (
It is also determined whether the number of characters from the point where the modification ends) to the end of the line matches. This is because even if the contents of the modified parts match, the ffi surrounds of the modified parts may differ.

In S8, an error message is displayed to indicate that there is no match. for example,[
The display section (second
It is displayed on the screen shown in Fig. 28).

S9: If it is necessary to correct the proofreading data of the second document file input in S6, return to S6 and re-input the proofreading data using the Averator; if it is not necessary, proceed to S10.
In ν, the month/month data of the proofread document file is (automatically) corrected.

S10: 82'r'' The proofreading data of the created proofread text 77? is (automatically) corrected so that it matches the data proofread in 86.

S11: 86'c Corrected character numbering data is stored in the auxiliary storage section 24 in the second
Store it as a sentence 1 file.

S12: Output the proofreading flow 177 file to a recording medium such as a floppy disk or magnetic tape, or print it out from a thermal printer, dot impact printer, etc. In addition, the data of the proofread document file 7 files can be directly transferred to the Japanese processing device (character size, m type, etc. according to the set code specification).
It is also possible to print out the block copy by transferring the rough typed data to an output device such as a laser printer or CRT typesetting machine online.

As described above, proofreading is performed twice on the data of one input document file, the proofreading results are compared, and if there are any discrepancies, they are corrected to make the proofreading more accurate.

FIG. 2 is an example of an i-row suitable for implementing the present invention.

Reference numeral 21 denotes an input unit for inputting character codes, group codes, etc., and inputting data created in another [1], and the input data is transferred to the control unit 22.

The υ1'#J unit 22 controls the entire device and transfers data.

The main storage unit 23 is a storage device that temporarily stores document data, various commands, etc., and performs data selection by exchanging data with the control unit.

24 is an auxiliary storage unit, in addition to the Bungetsu file, proofreading etc.
g! Then, the corrected text file, the second document file, etc., in which necessary embellishments and corrected characters are manually stored, are also stored.

Reference numeral 25 denotes a corrected part detection unit which reads out the proofread text 117 file stored in the auxiliary storage unit 24 and detects the part in which a correction code has been inserted at 84 in FIG.

Reference numeral 26 denotes a data modification section which executes the modification of the month/month data performed in S2 and S6.810 in response to a command from the input section 21, and inserts modification codes at the start and end points of the modified portion.

Reference numeral 27 denotes a data comparison unit that compares the data corrected part of the corrected text-damaged file with the data corrected part of the second document file, determines whether each piece of data matches, and executes the process performed in S7. .

Reference numeral 28 denotes a display section that displays an arbitrary part of the document file, the contents of the modified part, error messages, the line address of the displayed line, etc., according to commands from the entry section.

When the input and proofreading are completed, the output unit 29 outputs the contents of the second document 7F file or the proofreaded Bungetsu file. The output format is one that is output to a recording medium such as a floppy disk or magnetic tape, or one gram of a low-pixel cutter that is mainly used for galley printing using a thermal transfer printer, dot impact printer, etc.

In addition, the second document file or the proofread document file is input to the navy blue processing system, and Japanese processing is performed, and according to the Japanese processing data, it is suitable for high-pixel printing using a laser printer, CRT phototypesetting machine, etc. 1 cutlery! You can also.

FIG. 3 is a diagram showing a data groove structure of a proofread document file suitable for this embodiment. 31 is a row address code. The line address code 31 in this example is not necessarily limited to the one inserted at the line break position when outputting or displaying on the display section, but the line address code 31 from the beginning of each document file. The position of each character code or set code in each document file may be indicated by counting the codes. As a result of proofreading, even if the character codes and set codes before and after the row address code are erased, the row address code remains without being erased.11 On the other hand, after proofreading, more codes than the original line Even if a number is included, do not increase the row address code or change the number. This is to ensure that the line address (the number of lines counted from the beginning of the file) of the data after the calibrated portion does not change before and after the calibration. Therefore, the length of data (number of codes) for one line is variable.

32 is a character code, and 33 is a set]-do. The character code and set code are codes expressed as N-byte numbers, and the character code indicates which character it is, and the set code indicates what size, typeface, and layout the character is. 7J There are 16 codes that specify J. Character codes and set codes are treated in exactly the same way during input editing. When calibrating, it is simply corrected as a number 1+1 with N bytes in the middle, without any distinction.

Reference numeral 34 denotes a correction code inserted before and after the corrected portion of the proofread document file, that is, at the correction start point and the correction end point. The portion 35 surrounded by the correction code is a portion that differs from the original document data due to the correction. 84 in Figure 1
Specifically, the search for the modified portion in is executed by searching for this modification code and finding its line address. Note that even when document data in the Bungetsu file is deleted due to proofreading, two correction codes are inserted in the deleted portion to indicate that corrections have been made.

FIG. 4 specifically shows how data is corrected by the method of the present invention described above. (1) is input through the input unit 21, stored in the auxiliary storage unit 24 as a document file 7I, and is IC document data. In the figure, 11 is the row address code (31 in Figure 3), and 12 is the set code (31 in Figure 3).
3), 13 is the character code (Fig. 3, 32). first,
(This is called from the auxiliary storage unit 24 and proofread, and if necessary, corrections are made to create the corrected document data.)

1/la, 14b is a correction code inserted by proofreading and corresponds to 34 in FIG. 15a is the corrected part “E”
, and is sandwiched between modification codes [PSJ14a and rPEJ14b.

The document data that has been proofread is stored in the auxiliary storage unit 24 as a proofread document file.

On the other hand, as explained in FIG.
The document file is read from I24 to the main storage section 23, proofreading is performed, and the result is stored in the main storage section 23 as a second document file. This second document data is shown as (3), but the modified part [EJ15b is the modification mark F31'PSJ
14a and 1PE114b.

Next, proofreading (2), document proofreading? The modified part (2) is determined by reading out the file and detecting its modification code. Next, the second document data (3) is read out, and the line corresponding to the line where the correction point 15a is located is searched by the line address code to find the correction point ■, and both the correction points (0) are The data comparison unit 27 compares them and determines whether they match (37 in FIG. 1).

In this case, there is a mismatch between [E] and [E], and an error message is displayed (Fig. 1, 38), instructing whether to modify the proofreader document file or the second document file. (Fig. 1, 89) and correct either (4) or (2). The corrected document data is stored in the auxiliary storage unit 24 as a proofread text file and a second text file. In this way, the sentence nI data (6) resulting from matching the document data proofread the first and second times is shown in FIG.
Output at 12.

In this embodiment, as explained in FIG. 1, the corrected literary file is output, but it is clear that the second document file may also be output.

Also, when adding a row address, 1.2.3. In addition to giving the line address of..., you can also specify a column consisting of multiple lines,
You can also specify the number of pages, columns, and lines in units of pages consisting of multiple columns.

Furthermore, when comparing the contents between correction codes 14, the entire line including the correction code may be compared.

FIG. 5 is a flowchart illustrating another embodiment.

In the embodiment shown in FIG. 1, it is necessary to match the proof document data and the second document data. In FIG. 5, one of the files is designated as a file (in FIG. 5, data BI]#) second document file) that has undergone accurate proofreading. In the embodiment shown in Fig. 1, it does not matter whether the proofreader document file or the second sentence-i file is output, but in the embodiment shown in Fig. 5, the second document file (data B in the figure) must be output. Must be.

81, 82, and 83 in FIG. 5 are the same processes as in FIG.

In FIG. 5, the calibrated Bungetsu data is abbreviated as data 8.

S4: Create second document data from the inputted proofreading data in the same way as the proofreading performed in S2. The second document data may be created (copied) by another device and input from the input unit 21 . In FIG. 5, the second document data is abbreviated as data B.

S5: If the proofread document data (data A) and the second document data (data B) are to be compared according to the comparison instruction, the process advances to S6; otherwise, the process returns to S4.

$6 = Search for a location containing a correction code included in the proofread document data or the second document data. If there is no modification code in the searched range, the process proceeds to S12, and if there is, the process proceeds to S7.

S7: Compare the content of the line containing the corrected part of the proofread sentence south data and the second document data or the content between the correction groups @, and determine whether they match. 81 if the two data match
Proceed to step 2, and if they do not match, proceed to S8.

S8: The error message will be displayed, and the proofread document data and the second
Indicates that the document data did not match.

S9: Input a command as to whether or not the second document data needs to be corrected. If necessary, proceed to 810; if not, proceed to 811.

810: Modify the second document data.

S11: Re-compare data 11fl (specify Q position. By specifying this, it is possible to avoid comparing the already compared portions again.

S12: According to the calibration termination command, if the calibration is not to be terminated, proceed to S4; if it is to be terminated, proceed to 813.

S13: Output the second document data (data B). In this example, only the second document data is proofread correctly, so only the second document data is corrected.

[Effects of the Invention] In this way, a line address code that maintains the first line address even if an increase or decrease occurs in one line after proofreading is inserted at an arbitrary position in the document data, and a correction code is added to the proofreaded part. By inserting , it is possible to correct errors in proofreading by comparing the proofread parts of two files (proofreader document file and second intersection file) that were proofread separately. As a result, calibration work, which conventionally depended on the ability and skill level of the worker, can be performed accurately and efficiently.

[Brief explanation of the drawing]

Fig. 1 is a flowchart explaining an example of the present invention, Fig. 2 is an example of an apparatus suitable for carrying out the present invention, Fig. 3 is an example of data corruption of a proofread document file, and Fig. 4 is a flow chart of the present invention. This is a specific example of the proofreading work according to the invention, and FIG. 5 is a flowchart illustrating another embodiment. 11: Row address code 12: Set code 14a, b: Modification code 21: Input section 22: Control section 23: Main storage section 24: Auxiliary storage section 25: Modified portion detection section 26: Data correction section 27: Data comparison section 28 :Display section 29: Output section 31: Row address code 32: Character code 33: Group code 34: Modification code

Claims (1)

[Claims] A document file created by inserting a line address code indicating the line address of each code into document data consisting of a set code and character code indicating character size, font, layout, etc., and stored. When proofreading, the step of copying the document file including the line address code and inserting correction codes representing the specified correction and the correction start point and correction end point, and storing a proofread document file created; reading the document file, adding corrections and correction codes similar to those made to the proofread document file, and storing the same as a second document file; reading the proofread document file or the second document file and adding correction codes; detecting the line address of the second document file that corresponds to the line address where the correction code is located, and comparing the contents in the same line address of both files; and when there is a discrepancy in the comparison step, proofreading is performed. An input editing method comprising the steps of re-modifying and outputting either the completed document file or the second document file.