JPH11195013A - Document processor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document processor which can deal with a document containing a character and a pattern, which are expressed by an irregular code. SOLUTION: A document file 1 being a processing object is constituted of a character code and a handwriting code. The handwriting code corresponds to the character code by one to one. A font name is specified from a font information table with the handwriting code as a key and font data are generated based on the font name and the character code. When the font name corresponding to the handwriting code does not exist in the table, the table outputs the code showing the alternate font name. Unique character can be outputted by the irregular code by making data of an external character or the pattern correspond to the alternate code so as to register it.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing apparatus for processing a document including characters and patterns represented by codes, and more particularly to a document processing apparatus for processing a document including characters and patterns represented by codes not conforming to the code standard. The present invention relates to a document processing device that can be handled.

[0002]

2. Description of the Related Art In a document processing apparatus such as a word processor or a computer, characters constituting a document to be processed therein and various kinds of modification information relating to the characters are all encoded. The codes expressing these characters and modification information are standardized in order to provide data compatibility between different models. Although there are many code standards, if the codes are within the same standard, document compatibility is maintained regardless of the model of the document processing apparatus. As a code standard,
The JIS code system is well known.

[0003] However, many of the above-mentioned code standards code frequently used characters, such as common kanji, and personal name kanji and old kanji are often excluded from the standard. Manufacturers can define external characters such as characters and patterns that do not conform to the standard, for example, by assigning them to unused code areas in the JIS code system.

FIG. 14 is a block diagram showing a main part of a character processing apparatus described in Japanese Patent Application Laid-Open No. 6-259426. In the figure, character data 100 in a processed document is represented by a font name and a character code. If the character data 100 is a normal character (character in a standard code), the font data is read from the font file 110 according to the font name and the character code, and supplied to an output device.

On the other hand, if the character data 100 is an external character, the external character storage position in the external character file 130 is extracted by referring to the relative table 120. Then, the external character font data is read from the external character file 130 based on the external character storage position, and supplied to the output device. In this example, the storage position “1” is extracted from the font name “Gothic” and the character code “2147”, and the external character “A” is output.

FIG. 15 is a block diagram showing a main part of a document creating apparatus described in Japanese Patent Application Laid-Open No. 7-141332. In this apparatus, a character in a document is replaced with a character having the same type as the character on the JIS code but having a different font, that is, a different font. In the figure, document data 200 in a processed document is represented only by a character code. When replacing the character represented by character data “3548” of the fourth character in the document data 200 with an allograph, when this character on the display screen is designated, the character / allograph table 210 is referred to. The pointer is pulled. The pointer indicates a storage position on the data storage area 220. Then, a code representing an allomorph, that is, a converted character code is stored in the storage position of the data storage area 220 indicated by the pointer, and the character code “3548” is replaced with the pointer “0002”. The document data 230 is composed of a character code string including the character code after replacement.

[0007] In the case of outputting the character thus replaced, it is determined whether the character code is a pointer or a normal character code based on whether or not the upper three bits of the character code are "000". For example, the converted character code is read from the storage position of the data storage area 220 indicated by the pointer.

FIG. 16 is a block diagram showing a main part of a character shape management device described in Japanese Patent Application Laid-Open No. 7-105195. In this apparatus, character data in a processed document is represented by a character concept code conforming to a code standard and a character type code, instead of recognizing an allomorph by referring to a table. As shown, two character data 300, 3
10 has a common character concept code "3548", but differs in that the character type codes are "Mincho" and "Gothic". Characters a, 300a, and 310a are characters represented by only character concept codes and characters represented by character data 300 and 310, respectively.

[0009]

The above-mentioned conventional apparatuses have the following problems. JP-A-6-25942
In the device described in Japanese Patent Laid-Open No. 6-206, a code other than the standard code is used. Therefore, when processed by a different model, the code is not understood or a character completely different from a desired character is output. There is.

Further, the apparatus described in Japanese Patent Application Laid-Open No. 7-141332 uses a large number of tables, so that the processing becomes complicated and the document created by this apparatus does not have a table. There is a problem that if the data is output by another model, it is not interpreted.

[0011] Furthermore, in the device described in Japanese Patent Application Laid-Open No. Hei 7-105195, allomorphs represented by character type codes are characters having the same reading or the same meaning with the same "bias" and different "sides", for example. And two kinds of kanji, etc., which mean the fish "mackerel" described in the publication. In the device described in this publication, such an image pattern such as a symbol other than a kanji or a logo mark cannot be represented by a standard code. Therefore, the only way to deal with these symbols and logo marks is to express them with codes other than the standard code.In the end, as with the former two, if they are processed by different models, they become completely incomprehensible documents. It may be output.

[0012] The present invention solves the above-mentioned problems and enables symbols and logos to be represented by codes. In addition, when a document containing these codes is exchanged between different document creation environments, at least the document An object of the present invention is to provide a document processing device capable of preventing the meaning from being unclear.

[0013]

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems and to achieve the object, the present invention provides a character code string in a document file and a type code corresponding to each character code of the character code string. A font information table that outputs a font name using the font code as a search key, and a font information table that outputs a font data represented by the character code by interpreting a font code string composed of the character code and the font name And a font data storage means for outputting font data by using as a search key.

According to this feature, the document is output from the output device using the font data of the font designated by the character code and the font code. Even if a character code that conforms to the code standard is used, characters and patterns that are not included in the code standard can be output in correspondence with the character code by the typeface code.

[0015]

Embodiments of the present invention will be described below in detail with reference to the drawings. First, the configuration of data handled by the document processing apparatus of the present embodiment will be described. FIG. 2 is an example of a document file showing the configuration of input data. The data on the document file 1 includes a document character code (hereinafter simply referred to as “character code”) 1A and a typeface code 1B. In FIG. 2, the data on the document file 1 is represented by characters in an output form instead of codes for easy understanding.
The character code 1A describes a character in a document by a code, and a code within a code standard is used. The font code 1B is one for each character in the character code 1A.
Font information corresponding to one to one. The typeface code 1B depends on the document creation environment and the document output environment. In the typeface code 1B, "Min" indicates the Mincho font, "I" indicates the allograph, and "B" indicates the logo mark.

Character code 1A and typeface code 1 in FIG.
FIG. 3 shows an example in which the document represented by B is output to a printer device or a display device. FIG. 3A shows a typeface code 1B.
In this example, “high” is output as “high” in allographs, and “confirmation” is output as an imprint of “Takahashi”. On the other hand, when the character code 1B is output without referring to the typeface code 1B, the character code 1A is directly converted according to the code standard, so that an output result as shown in FIG. 3B is obtained.

FIG. 4 is a diagram showing an example of table control data used for changing a table used during the processing. The table control data includes data indicating whether the target table is a character code conversion table or a font information table, data indicating control contents such as output / update / addition / deletion, and a specific table structure, that is, data contents. Is described. Processing based on this table control data will be described later.

Next, the function of the document processing apparatus for processing the document file 1 illustrated in FIG. 2 will be described. FIG.
FIG. 1 is a block diagram illustrating a configuration of a document processing apparatus according to an embodiment of the present invention. In FIG. 1, a CPU 2 controls the whole document processing apparatus and performs arithmetic processing. The working memory 3 temporarily stores data being processed. The external interface 4 receives a document file (see FIG. 2) created by an external document creation device such as a host computer.

The font information analyzer 5 compares the typeface code of the input document file with the font information table 6 and specifies a font to be used when outputting a document.
The character code conversion unit 7 compares the character code and the typeface code with the character code conversion table 8 when the code sequence of the character code of the input document file satisfies a predetermined condition (described later). Replace with a predetermined character code or typeface code. The table information control unit 9 controls output, update, addition, and deletion of table information used during processing.

The rasterizing unit 10 develops image data on the page memory 11 using the font and character code to be used. The font data storage unit 12 stores font data for output. The printer interface 13 is an interface for outputting image data to an image output terminal (IOT) 14. The font code generation unit 20 generates a font code by specifying individual characters in a document file including only character codes in which no font code is set, on the assumption that a default font is used.

FIG. 5 is a diagram showing an example of the font information table 6. As shown in FIG. As shown in the figure, the font information table 6 stores a font name and a font data storage unit 12.
Above font storage location, default, code check is described. Here, the default is a number indicating the font name to be used when the data indicated by the typeface code does not exist, and the code check is a flag indicating whether to convert the character code. When this flag is set, a character code string composed of a plurality of character codes is checked according to a procedure described later, and the character code string is replaced with a predetermined character code by using the character code conversion table 8.

FIG. 6 shows an example of the character code conversion table 8. As shown in the figure, the character code conversion table 8 describes a typeface code, a character code string, a replacement character code, and a replacement typeface code which are used conditions. Here, the replacement character code is a character code used when the condition is matched, and the replacement font code is a font code used when the condition is not matched.

In the above configuration, data input through the external interface 4 is temporarily stored in the working memory 3. The input data includes the above-described document file and table control data (FIGS. 2 and 4). The document file is transferred to the font information analysis unit 5, and the table control data is transferred to the table information control unit 9. The font information analysis unit 5 includes a typeface code and a font information table 6
Identify the font to use based on the content of If the font corresponding to the typeface code does not exist on the font information table 6, another font is selected based on the description on the font information table 6. For example, if "Mincho foreign body" is indicated in the typeface code, "1" is described as the default value in the font information table 6 of FIG. 5, so the Mincho font of the number "1" is specified. Is done.

Further, when "logo mark" is designated by the font code, since the code check flag is set in the font information table 6 of FIG. Character code converter 7
Then, the character code is replaced depending on whether or not the input data, that is, the character code and the typeface code match the conditions described in the character code conversion table 8.

For example, as a result of referring to the font information table 6, if the code check flag of the corresponding type code is set, the character code string is checked with reference to the character code conversion table 8. As a result, if the character code string matches the character code string in the character code conversion table 8, the replacement character code is selected, and if not, the replacement font code is selected.

FIG. 7 is a diagram showing an outline of the processing when the code check flag is set. In the figure, document data X consisting of a character code string “88c9, 9301” and a typeface code string “8001, 8001” exists, and a character code conversion table Ta is set. In this case, since the character code string “88c9, 9301” is included in the character code conversion table Ta, the character code string “88c9, 9301” is replaced with the replacement character code “200”.
1 ". If the character code string matches the character code string in the character code conversion table Ta, the typeface code “8001” is maintained. That is, the code indicating the document is the character code “2001” and the typeface code “800”
1 (document data X1).

On the other hand, if the character code string does not match the character code string in the character code conversion table Ta, the character code string "88c9, 9301" is maintained, and the font code "8001, 8001" is used as the replacement font code. It is converted to the default value “4001, 4001” (document data X2).

The rasterization processing unit 10 extracts font data from the font data storage unit 12 using the character code as a search key from the fonts selected by the font code (including the replacement font code), and stores the image data in the page memory 11. Expand as The image data is sent to the IOT 14 through the printer interface 13.

Next, the above processing will be described with reference to a flowchart. FIG. 8 is a flowchart showing the entire processing. In step S1, data existing in the working memory 3 is checked. If the document code and the typeface code exist, the process proceeds to step S2, where font information analysis for specifying the font type based on the typeface code is performed. In step S3, font data is acquired from the font whose type is specified, using the character code as a search key. In step S4, the acquired font data is developed in the page memory 11. In step S5, IOT1
4 to output data from the page memory 11 in response to the request.

If only the character code exists on the working memory 3, the process directly proceeds to step S3 without passing through step S2. In this case, in step S3, font data is acquired from the default font. Also,
If the table control data exists on the work memory 3, the process proceeds to step S6, and the table control process is executed according to the instruction of the table control data.

Next, the processes of the font information analysis (step S2), font data acquisition (step S3), and table control (step S6) will be described in more detail. First, the font information analysis will be described. In the font information analysis, for each character code, the typeface, that is, the type of the font is specified by comparing the typeface code with the font information table. In this collation operation, if the code check flag is associated with the designated typeface code, the processing shifts from collation for each character code to collation of a character code string. FIG. 9 is a flowchart of the font information analysis. Step S
At 10, the typeface code is checked. Step S
At 11, it is determined with reference to the font information table 6 whether the designated typeface code corresponds to a mark other than a character, that is, a symbol or a logo mark, that is, whether a code check flag is set. If the mark has been designated, the process proceeds to step S12, where the character code string is checked, and as a result, it is determined whether the character code string matches the character code string on the character code conversion table 8 (step S13). ). That is, the mark is represented by a plurality of character codes, and each character code is associated with the same typeface code (in the document file 1 in FIG. 2, the typeface code "Rororo" representing the logo is attached to the document code "confirmation mark"). Therefore, it is determined whether or not the character code strings corresponding to the plurality of typeface codes match the character code strings on the character code conversion table 8.

If it is determined that the character code strings match, the process proceeds to step S14, in which a replacement character code corresponding to the typeface code is output as the character code, and the font data of the mark created and stored in advance is stored. Is adopted. If it is determined in step S13 that the character code strings do not match, the flow advances to step S15 to select a replacement font code, for example, default font data.

If it is determined in step S11 that there is no mark designation, the flow advances to step S16 to determine with reference to the font information table 6 whether or not the font specified by the font code exists. If there is a designated font, the process proceeds to step S17, and the designated font is adopted according to the designated typeface code. If there is no designated font, the process proceeds to step S18, where a default font is selected.

Next, the acquisition of the font data will be described in detail. At the time of entering this process, the font type has already been determined. In FIG. 10, in step S20, the character code is checked to obtain font data corresponding to the character code (including the replacement character code) from the font of the font name selected based on the font code (including the replacement font code). .

In the case of a general Japanese font, a character code is represented by 2 bytes. Thus, font data is obtained from the font data storage unit 12 using the upper half and the lower half of the character code as search keys. If there is no font data corresponding to the character code (if step S21 is affirmative), the process proceeds to step S22, where a substitute code when there is no font data, for example, a code corresponding to a blank or “□” is acquired. Step S23
Then, font data corresponding to the character code (including the substitute code) is output.

Next, the table control processing will be described in detail. In FIG. 11, in step S30, processing contents, that is, output, update, addition,
Determine whether it is a deletion. The processing content is read from the header area of the table control data. Step S31
Then, the target table is determined. If the target table is the font information table 6, the process proceeds to step S32. If the target table is the character code conversion table 8, the process proceeds to step S32. In the control of the font information table 6, any of output, update, addition, and deletion is controlled based on the processing content. If output, the contents of the font information table 6 are output. If it is to be deleted, the contents of the font information table 6 are deleted. If added, the contents of the table control data are added to the font information table 6. If it is updated, the font information table 6 is temporarily cleared, and the contents of the table control data are written into the font information table 6.

The target table is the character code conversion table 8
If so, the process proceeds to step S33. The control on the character code conversion table 8 is the same as the control on the font information table 6, and the description is omitted. When a new character or mark is set, the character code conversion table 8
Must be changed to set a font code, a character code string, a replacement character code, a replacement font code, etc., but the font information table 6 does not need to be changed when a new character or the like is registered.

Next, a description will be given of a processing example of the typeface code creating section 20 for creating a typeface code from a document having only character codes. In the above-described embodiment, it is assumed that a document file including a character code and a typeface code, which is created externally such as a host computer, is input. However, in some cases, a document file containing only character codes to which no typeface data is added may be input. Therefore, it may be desired to create a typeface code from a document file containing only this character code. Therefore, the typeface code creating unit 20 performs a process of converting the typeface code of the character code of the designated character into a type indicating a font other than the default.

In the flowchart of FIG. 12, in step S100, it is determined whether or not there is a typeface code creation request. If there is no typeface code creation request, step S11
The process proceeds to 0, and the process proceeds to the character data acquisition process (step S120) by using the default font. If there is a font code creation request, the process proceeds to step S130,
Referring to the font information table, the type of font that can be used is notified to the user. Specifically, a font name on the font information table is displayed on a display screen (not shown) of the document processing apparatus. If the user's response to this display, that is, an instruction of a character and a font name is input (Yes at step S140), the process proceeds to step S150. In step S150, a font code indicating the font type of the designated font name is output as the font code of the designated character. The character code and typeface code of the character are stored in the respective registration areas.

The font code creation processing will be further described with reference to the block diagram of FIG. In FIG. 13, a document file 19 is read from the working memory 2 and characters are displayed on the display unit 15. Characters are displayed in the default typeface. The user designates a character whose font is to be changed for each displayed character and selects a displayed font name. Designation and selection of characters can be performed by a well-known input method such as operating a key or a mouse or the like having a function set in advance by moving a cursor to a character whose font is to be changed or a displayed font name.

In this manner, the font information corresponding to the selected font type, that is, the font, is stored in the font information table 1.
6 and acquired. Characters designated by the user are assigned the changed typeface code, characters other than the designated type are assigned a typeface code indicating a default typeface, and each typeface code is stored in the storage unit 17.
And the character code is stored in the storage unit 18.

The typeface code creating section 20 is not limited to generating a typeface code for a document file consisting of only character codes, but can also be applied to a case where a typeface code previously associated with a character code is changed. .

As described above, according to this embodiment, characters and marks outside the code standard can be represented by codes.
Since the character codes used in character codes and typeface codes that represent characters etc. are within the code standard, even if characters etc. are output in an environment where the typeface code cannot be interpreted, it is considered that the document has no meaning at all. It will not be.

When a code check instruction is detected by the font information table, the character code conversion table determines whether the character code string matches the expected code string, and cannot be represented by a single character code. A logo mark or the like can be easily output.

The present invention can be applied not only to a case where a document is output by a printer device but also to a case where a document is displayed on a display screen. For example, Windows
dows) If font data in a form corresponding to the environment is prepared in the font data storage unit 12 and rasterized data is developed in a frame buffer for a window, irregular fonts, logo marks, and the like are displayed in the window. Can be displayed.

[0046]

As is clear from the above description, according to the present invention, a character or pattern not included in the code standard is output in correspondence with the character code by the typeface code associated with the character code. Can be.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a document processing apparatus according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of a document file processed in an embodiment of the present invention.

FIG. 3 is a diagram illustrating an example of an output result of a document file.

FIG. 4 is a diagram showing an example of table control data.

FIG. 5 is a diagram illustrating an example of a font information table.

FIG. 6 is a diagram illustrating an example of a character code conversion table.

FIG. 7 is a block diagram illustrating an example of a character code conversion process.

FIG. 8 is a flowchart of document processing according to an embodiment of the present invention.

FIG. 9 is a flowchart of a font information analysis process.

FIG. 10 is a flowchart of a font data acquisition process.

FIG. 11 is a flowchart of a table control process.

FIG. 12 is a flowchart of a typeface code creation process.

FIG. 13 is a block diagram illustrating an example of a typeface code creation process.

FIG. 14 is a block diagram illustrating an example of a conventional device.

FIG. 15 is a block diagram illustrating an example of a conventional device.

FIG. 16 is a block diagram illustrating an example of a conventional device.

[Explanation of symbols]

1: Document file, 5: Font information analysis unit, 6:
Font information table, 7 ... character code converter, 8 ...
Character code conversion table, 9 ... Table information control unit,
12: Font data storage unit, 20: Font code creation unit

Claims (6)

[Claims] A font data represented by the character code is output by interpreting a character code string in a document file and a character code string corresponding to each character code of the character code string. The document processing apparatus, comprising: a font information table that outputs a font name using the typeface code as a search key; and a font data storage unit that outputs font data using the character code and the font name as a search key. Document processing device. 2. The font information table holds a default font name in place of a font name not set in the font data storage means, and a font code indicating the font name not set is input. 3. The document processing apparatus according to claim 1, wherein the default font name is output in some cases. 3. When the font information table inputs a typeface code indicating a font name not set in the font data storage means, the character code or the typeface code is converted into a substitute character code or a substitute typeface code. In addition to outputting the instruction information for making the determination for, in response to the instruction information, it is determined whether a character code string consisting of a plurality of character codes matches the planned conversion condition Judging, converting the character code string into a predetermined replacement character code when they match, and converting the font code into a predetermined replacement font code when they do not match. 3. The document processing apparatus according to claim 1, wherein 4. The character code conversion means comprises: a font code, a character code string set in correspondence with the font code, a replacement character code, and a character code conversion table in which a replacement font code is described. 4. The document processing apparatus according to claim 3, wherein the determination of the code string and the conversion into the replacement character code and the replacement typeface code are executed using the character code conversion table. 5. A means for receiving table control data including a target table name, control contents, and controlled data for controlling the font information table and the character code conversion table; and control contents described in the table control data. 5. The document processing apparatus according to claim 4, further comprising table information control means for outputting / updating / adding / deleting data of a target table based on the controlled data. 6. A display means for displaying a character string on a document file, a character constituting the displayed character string, and an input means for designating a typeface of the character, and a character other than the specified character A default typeface code, and a typeface code generation unit that sets a typeface code of a specified typeface to the specified character; and a character code of the character and a typeface code set by the typeface code generation unit. The document processing apparatus according to any one of claims 1 to 5, further comprising storage means for registering a document.