JPH07105196A - Character data management device and character output device including the same - Google Patents

Abstract

(57) [Abstract] [Purpose] To provide a character shape data management device having means for reducing obstacles in data exchange between different models and a character output device having the same. A character memory 16 in the present character shape data management device stores character shape data defining a character shape, a character concept code designating a character concept, and at least two or more variant characters to which the same character concept code is assigned. Is stored so that it can be designated by a type code selectively defined by the type, the input means 18 inputs the character concept code and the type code, and the reading means is the input means 1.
The character shape data corresponding to the character concept code and the type code input in 8 are read from the character memory 16. Also,
The code designating means in the character output device designates the character concept code and the type code to the character shape data management device, and the output means displays or prints the character shape data outputted by the character shape data management device.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention generally relates to Japanese kanji, and more particularly to a glyph data management device capable of handling variant kanji and a character output device having the same.

[0002]

2. Description of the Related Art Conventionally, in a system for handling Japanese kanji, a unique code is assigned to each font due to the spread of digital computers, and data can be exchanged between different models by referring to the code. It was being appreciated. And for such a code system, JIS
A JIS code kanji table based on a code system commonly known as a code is widely used. This JIS code kanji table, like the common kanji table, is arranged based on the social conventions of the times, and has been revised several times to date.

The typeface has been changing over time, and among the typefaces that have been introduced from China since ancient times, it is now used only for proper names such as personal names and place names, and in the case of other ordinary sentences, the typeface has changed. Is used, so-called new,
There are many distinctive fonts that are called old fonts. In addition, in distinguishing the fonts, they are sometimes called regular characters, abbreviations, and slang characters, and it seems that they may be confused and used, but when trying to clarify the definition of terms, the culture of kanji Since the theoretical element becomes stronger and deviates from the main point of this paper, each term is defined based on social convention.

In the JIS code Chinese character table described above, some fonts are included in only one of the old JIS code Chinese character table and the new JIS code Chinese character table. For example, the characters shown in FIGS. 6A, 6B, and 6C are examples, but these are treated as the same value in the JIS standard, and the same JIS code is assigned. . Regarding personal names, slang and abbreviations that are not corrected by "Ministry of Justice Citizen No. 5200 No. 5200 Civil Affairs Bureau Notification October 20, 1990" due to computerization of family register work are shown. For example, this is the case as shown in FIG. Many of these fonts are not included in the JIS code kanji table.

By the way, in ordinary sentences, the use of characters should be based on the cultural background of the user, and if there is a choice, it will be used according to each preference. However, in place name and person name,
The stronger the elements of the official document, the more the defined font itself must be used.

Therefore, conventionally, when there are a plurality of variants for one Chinese character as shown in FIG. 6, one of the characters is assigned a code in the JIS code table, and the other character has a so-called external character area. The code was allocated.

[0007]

However, in the above-described conventional system for handling Japanese kanji, there is no particular regulation on how to allocate codes in the external character area, and it is left to the discretion of the person who manufactures the system. Therefore, different fonts may be assigned to the same code between different models, or the font may not be defined, which is an obstacle to data exchange.

The present invention has been made in view of the above-mentioned problems, and provides a character shape data management device having means for reducing a trouble in data exchange between different models and a character output device having the character shape data management device. It is an object.

[0009]

In order to achieve this object, a glyph data management apparatus of the present invention is a means for storing glyph data which is data defining the shape of a character. A font data storage means for storing a character concept code designating a concept and a type code selectively defining at least two variant characters to which the same character concept code is assigned by the type; A code input means for inputting the character concept code and the type code, and a reading means for reading the glyph data corresponding to the character concept code and the type code input by the code input means from the font data storage means. is doing.

The glyph data management device further comprises glyph data existence determining means for determining whether or not glyph data corresponding to the character concept code and the type code is stored in the font data storage means. When the code input means determines that there is no character shape data by the character shape data existence determining means, no input may be made.

Alternatively, the glyph data management device determines whether or not the glyph data of the variant character designated by the type code corresponding to the character concept code input by the code input means is in the font data storage means. If there is no glyph data by the glyph data existence determining means and the glyph data determining means, the font data using the glyph data of the normal character or another glyph corresponding to the character concept code as a substitute character. The substitute character reading means for reading from the storage means may be further provided, and when the substitute character reading means determines that there is glyph data by the variant character data judging means, the glyph data may be read.

Further, a substitute character converting means for converting the glyph data of the substitute character into data representing that the glyph is a substitute character is provided, and the substitute character reading means is obtained by the substitute character converting means. It may output data.

Further, the character output device of the present invention has any configuration of the character shape data management device, and code specifying means for specifying the character concept code and the type code to the character shape data management device, An output unit is provided for displaying or printing the character shape data output by the character shape data management device.

Further, the character output device may be provided with variant character explanation giving means for giving the explanation according to the type code designated by the code designation means to the character outputted by the output means.

[0015]

The font data storage means in the character shape data management device of the present invention having the above structure is means for storing character shape data which is data defining the shape of a character, and the character shape data is designated by a character concept. The character input code is stored so that it can be designated by a character concept code and a type code selectively defining at least two variant characters to which the same character concept code is assigned. The concept code and the type code are input, and the reading means reads the character shape data corresponding to the character concept code and the type code input by the code input means from the font data storage means.

The character shape data existence determining means determines whether character shape data corresponding to the character concept code and the type code is stored in the font data storage means, and the code input means determines the character shape data. If the presence determining means determines that there is no glyph data, no input is made.

Further, the variant character data existence determining means determines whether or not the character shape data of the variant character designated by the type code corresponding to the character concept code input by the code input means is in the font data storage means. If it is determined that the variant character data determining unit determines that there is no character shape data, the substitute character reading unit uses the normal character corresponding to the character concept code or the character form data of another variant character as the substitute character. When the glyph data is read from the font data storage means and the glyph data is determined by the glyph data determination means, the glyph data is read.

Further, the substitute character converting means converts the glyph data of the substitute character into data representing that the glyph is a substitute character, and the substitute character reading means obtains the data obtained by the substitute character converting means. Is output.

Next, the code designating means in the character output device of the present invention designates the character concept code and the type code to the character shape data management device, and the output means outputs the character shape data management device. Display glyph data,
Or print it.

The variant character explanation imparting means imparts an explanation according to the type code designated by the character designating means by the character output device to the character output by the output means.

[0021]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

This embodiment is an example in which the character shape data management device of the present invention is preferably applied to a Japanese document creation device.
FIG. 3 is a block diagram mainly showing a portion of a glyph data management device in the control circuit of the Japanese document creation device of this embodiment.

The microcomputer unit 10, which is the main body of this control circuit, includes a CPU 12, a program memory 13,
A working memory 14, a code memory 15 and a character memory 16 are provided. And these CPU12
Etc. are connected by a bus 17, and an input unit 18 and an output unit 19 are connected to the bus 17.

Next, the outline of the configuration of each of the above parts will be described.
The CPU 12 performs processing for implementing the present embodiment according to a given program, and the program memory 13 stores a program for performing a series of processing procedures related to reading and registration of the glyph data of the present embodiment. is there. Further, the working memory 14 temporarily stores data necessary for executing the program, and the code memory 15 stores information associating the character code for instructing the character shape with the character shape data. The details will be described later. Character memory 1
Reference numeral 6 stores character shape data.

The code memory 15 will be described below. The glyph code of the present embodiment is a new character type code that indicates the character concept, with new types of JIS punctuation point code and variants.
It consists of the type code part shown in old. For example, in FIG.
The characters shown in (b) are originally the same characters, but the new JIS
The character shape of (a) is defined by and the character shape of (b) is defined by the old JIS. Therefore, these are the same JIS ward code 2
710 characters. When these character shape data are stored together, since the types (a) and (b) cannot be classified only by the character concept code, information for distinguishing new characters / old characters is added. This is the type code. That is, since (a) is a new character, glyph code 2710-new, and (b) is an old character, glyph code 2710-old. Code memory 1
Reference numeral 5 stores such a glyph code and the address of the glyph data of the glyph indicated by the glyph code in the character memory 16 in association with each other.

Incidentally, this kind of data is not only new / old,
For example, even data showing the type of regular / abbreviated / slang,
This may be data that simply indicates a variant, or data that includes identification information of the same type such as old-1, old-2, etc. if there are multiple cases in each case. In the example, only the new / old type data will be described for ease of explanation. If no kind data is specified, new is specified as the default.

Further, the input section 18 and the output section 19 are for inputting / outputting data to / from the microcomputer section 10. The JIS division code and the type code are inputted from the input section 18 and read out to the output section 19. It is designed to output glyph data.

The processing performed by the character shape data management device of this embodiment will be described in detail below.

First, the glyph reading process will be described below with reference to the flowchart shown in FIG. 3. First, the JIS division point code and the type code input in S31 are converted into glyph codes. For example, when the JIS ward code is 2710 and the type code is "old", it is converted to 2710-old here. If the type code is not input, it is treated as if the default "new" is input. Next, in S32, it is determined whether or not the glyph code is registered by referring to the code memory 15. Here, if it is determined that there is no (NO), S33,
When S34 is executed and the process proceeds to S35, and it is determined that there is (YES), the process proceeds to S35.

If NO in S32, the following process is executed. First, in S33, a glyph code of a substitute character is created. In the present embodiment, the substitute character is converted into the glyph data designated by the JIS code which is the designated character concept code and "new" which is the default of the type code. Therefore, here 2710-old is converted to 2710-new.
Further, in order to show that the glyph does not belong to the character designated by the input unit, a shape obtained by combining the shapes in the glyph data corresponding to the default glyph code is output. In this embodiment, a square shape that surrounds the entire character is output. S3
In 4, the synthesized shape is read from the character memory 16 and stored in a character buffer (not shown) in the working memory 14.

In step S35, the glyph data is read from the address of the glyph data corresponding to the specified glyph code and stored in a glyph buffer (not shown) in the working memory 14. If there is a shape stored in the glyph buffer in S34, it is combined with the shape and stored. For example, when the character as shown in FIG. 2A is registered as the character shape data and the character shape code is registered as 2710-new, but the old character corresponding thereto is not registered, the shape of FIG. 2C is created. ,Output.

Although the glyph data is read by the above-described processing, if there is no glyph data of the character corresponding to the glyph code, that is, if NO in S32, the glyph data is not output. It is also possible to output the glyph data corresponding to the default glyph code for that glyph data without synthesizing the shape that indicates that it is not the glyph data corresponding to the input glyph code. is there. Furthermore, when a large number of type codes are defined in addition to the old characters, the shape to be combined can be changed according to the type. For example, when the type code is defined by regular characters / abbreviated characters / slang characters, it is possible to synthesize a square if there is no registered abbreviation, and to synthesize a round shape if there is no registered slang character. . Further, without performing the determination of S32, S31, S35
It is also possible to configure only the processing of.

The character display / printing unit serving as the client unit of the character shape data management apparatus of this embodiment will be described below.

In step S41, the character display / printing section reads out the character code of one character and the information indicating whether or not the description of the variant character is added to the character code. Next, in step S42, the character code is converted into a JIS division code, and the type is obtained for characters with new / old instructions, and the default new is used as type data for characters without instructions. Next, in S43, the input unit 1 of the character shape data management device.
8, the character shape data is read and obtained from the output unit 19. Next, in step S44, the character shape data read in step S43 is sent to the display unit / printing unit and output. In addition, in S45, S41
It is determined whether or not the description of the variant character is added to the character input in step S4, and if the description is added, in S46, if the specified type code is "old", it is "old character". In order to perform the explanation given, for example, by underlining the output character shape or by outputting a message such as "This character is an old character.", The information is output to the display unit / printing unit. This processing is effective when the character / display unit receives a character output request from kana-kanji conversion or the like, or when the document creation apparatus has a function of checking the attributes of kanji. These processes are repeated until it is determined in S47 that the process is completed.

It is also possible to change to a configuration for determining whether or not the character to be read in advance exists in the character memory 16 before the reading process of S43. That is, S
Between S43 and S44, S51 as shown in FIG.
At 51, it is checked with reference to the code memory 15 whether or not the designated glyph code is registered. If YES, S44 and subsequent steps are executed, and NO
If so, the process proceeds to (1).

Although the present embodiment has been described by taking the Japanese document creation device as an example, it can be applied to any device that outputs the kanji character shape.

In the present embodiment, the character memory 16 and the code memory 15 are shown as separate structures, but the present invention is not limited to this, and they may be arranged in the same memory.

Although the font data format is not particularly described in the present embodiment, it may be any format such as a bitmap font, an outline font, or any other format. Is also good.

In addition, the present embodiment can be variously applied without departing from the spirit of the present invention.

[0040]

As is apparent from the above description, according to the glyph data management device and the character output device having the same of the present invention, glyph data of different characters can be managed without breaking the existing glyph code system. Therefore, it is possible to display or print characters using a font data group in which obstacles in data exchange between different models are reduced.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment embodying a configuration of a character shape data management device of the present invention.

FIG. 2 is a diagram showing an output example of variant characters.

FIG. 3 is a flowchart showing a glyph data reading process of the present embodiment.

FIG. 4 is a flowchart showing a character display / printing process of this embodiment.

FIG. 5 is a flowchart of an application part added to the character display / printing process of the present embodiment.

FIG. 6 is a diagram showing an example of variant characters.

FIG. 7 is a diagram showing an example of variant characters.

[Explanation of symbols]

15 Code Memory (Font Data Storage Means) 16 Character Memory (Font Data Storage Means) 18 Input Means (Code Input Means) S35 Read Processing (Read Means, Substitute Character Read Means, Substitute Character Conversion Means) S51 Character Shape Existence Determining Means S32 Variant data existence determination means S33 Substitute character glyph code creation processing (substitution character reading means) S34 Synthetic shape reading processing (substitution character conversion means) S41 Code reading processing (code designation means) S42 Code conversion processing (code designation means) S44 Display / Print processing (output means) S46 Explanation output processing (variant character explanation giving means)

Claims (6)

[Claims] 1. A means for storing glyph data which is data defining a shape of a character, wherein the glyph data is assigned at least two character concept codes designating a character concept and the same character concept code. Font data storage means for storing one or more variant characters so that they can be designated by a type code selectively defining the type, code input means for inputting the character concept code and the type code, and the code input means 2. A glyph data management apparatus comprising: a reading unit that reads the glyph data corresponding to the character concept code and the type code input in 1. from the font data storage unit. 2. A glyph data existence determining unit that determines whether or not glyph data corresponding to the character concept code and the type code is stored in the font data storage unit, and the code input unit has the glyph data. 2. The glyph data management device according to claim 1, wherein when the presence judging means judges that there is no glyph data, no input is made. 3. Glyph data existence determining means for determining whether or not the glyph data of the glyph designated by the type code corresponding to the character concept code input by the code inputting means exists in the font data storing means. If the variant data determination means determines that there is no glyph data, the normal character corresponding to the character concept code or glyph data of another variant is read from the font data storage means as a substitute character, and the substitute character reading is performed. The glyph data management according to claim 1, further comprising: means for reading the glyph data when the substitute character reading means determines that the glyph data is present by the glyph data determining means. apparatus. 4. The substitute character converting means for converting the glyph data of the substitute character into data representing that the glyph is a substitute character, wherein the substitute character reading means is data obtained by the substitute character converting means. The character shape data management device according to claim 3, wherein 5. A character output device comprising the character shape data management device according to claim 1 for displaying or printing the shape of a character, wherein the character concept code and the character concept code are supplied to the character shape data management device. A character output device comprising: a code designating device for designating a type code; and an output device for displaying or printing the character shape data output by the character shape data management device. 6. The character according to claim 5, further comprising variant description giving means for giving a description according to the type code designated by said code designating means to the character outputted by said output means. Output device.