JPH0760437B2 - Usage dictionary - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Outline] Regarding a usage dictionary that manages usage information described in Japanese in a prescribed order, the purpose is to reduce the memory capacity of the required dictionary size. When the usage information to be managed has a common part starting from the first character with the usage information of the preceding order, it is provided for information correspondence, and manages the numerical value according to the number of Japanese characters in that common part, and when there is no common part It is provided in a format that forms a pair with the compression usage information management unit that manages a zero value and the compression usage information management unit. When the compression usage information management unit manages a non-zero value, it is common among the usage information to be managed. When managing only the Japanese information that follows the part and managing the zero value, it is configured to include a usage information management unit that manages all the Japanese information of the usage information to be managed.

[Industrial application field]

The present invention relates to a usage dictionary that manages usage information described in Japanese according to a prescribed order, and more particularly to a usage dictionary that can reduce the memory capacity of the required dictionary size.

In recent years, with the diversification of dictionary types, one data processing system (for example, a word processor) is provided with a plurality of dictionaries to execute data processing. Under such circumstances, one by one
If the size of one dictionary is large, the memory capacity required for the operation of all the dictionaries will become enormous, which will put pressure on other operation modes. From now on, it is necessary to take measures to reduce the dictionary size of each dictionary as much as possible.

[Conventional technology]

A usage dictionary manages specific usage information such as addresses and names in ascending order. FIG. 4 shows the configuration of the conventional art of such a usage dictionary, taking an address dictionary as an example. Here, in this example, it is assumed that the address dictionary manages the address information "Osaki, Unoke Town, Hebei County, Ishikawa Prefecture" following the address information "Nichikaku, Unoki Town, Kawakita County, Ishikawa Prefecture".

As shown in this figure, in the conventional address dictionary, each address information is read as "reading length", "compressed reading length", "reading", "JEF".
It was configured to manage according to "long" and "JEF code". Here, "JEF" is an identifier of the Japanese code system used. To explain it concretely using the address information of "Osaki, Unoke-cho, Kawakita-gun, Ishikawa Prefecture" managed in the area in the figure, enter "Osaki, Unoke-cho, Kawakita-gun, Ishikawa Prefecture" in the entry field for this "reading length." The number of characters "20" for "Ishishikan Kahokungun Nookemachi Osaki" which is how to read is registered, and the entry field of "Compressed reading length" is managed in the area immediately before "Kahoku-gun, Ishikawa Prefecture". The number of characters "16" for "Ishikainka Kahokungun Unokemachi", which is a common reading part with "Unoki-cho Nichikaku", is registered. The code of "Osaki" which is not common is registered, "24" which is double the number of characters of "Osaki, Unoke Town, Kawakita-gun, Ishikawa Prefecture" is registered in the entry field of "JEF length", Then, in the entry field of "JEF code", "Kawakita Ishikawa Prefecture" Osaki, Unoki Town, Gun
The code of will be registered. Where "JEF length"
The reason for registering twice the number of characters in the entry field is because "JEF" represents one Japanese character in two bytes.

As described above, in the conventional usage dictionary such as the address dictionary, the usage size of the managed usage information is compressed in the common part to reduce the size of the dictionary.

[Problems to be Solved by the Invention]

However, in the conventional usage dictionary, the entry column of the "JEF code" does not have a structure in which the data is compressed even if there is a common part. In other words, in the example shown in FIG. 4, the managed address information “Hikaku in Unoke-machi, Hebei-gun, Ishikawa Prefecture” and “Osaki, Unoki-cho, Kawakita-gun, Ishikawa Prefecture” are combined into “Kaboku, Ishikawa Prefecture”. Although there is a common part of "Gun Unoki-cho", the "JEF code" was configured to be managed as it is without compressing the data. From now on, under the situation that a plurality of dictionaries must be provided, the memory capacity required for the dictionaries increases, which causes a problem of putting pressure on other operation modes.

The present invention has been made in view of the above circumstances, and in a usage dictionary that manages usage information described in Japanese in a prescribed order, the usage information is also configured to be data-compressed. The purpose is to solve the problem of.

[Means for Solving the Problems]

FIG. 1 is a principle configuration diagram of a data format of usage information managed by a usage dictionary according to the present invention.

In the figure, 1 is a reading length management unit that manages the number of characters for reading the usage information to be managed by 1 byte, and 2 is a compression reading length management unit, which has a preceding order starting from the first character. One that manages the number of characters in the common part of the reading with the usage information by 1 byte, 3 is a reading management unit, and the character information of the non-common part of the reading in the usage information that is not managed by the compression reading length management unit 2 Items managed by EBCDIC code, 4
Is a usage information length management unit that manages a value according to the number of Japanese characters of the usage information to be managed with 1 byte, and 5 is a compression usage information length management unit, which starts from the first character One byte manages the value corresponding to the number of Japanese characters in the common part with the order usage information, 6 is a usage information management unit, and is not common in usage information not managed by the compressed usage information length management unit 5. The Japanese information of a part is managed by JEF code, for example.

[Action]

In the present invention, when there is a common part starting from the first character with the usage information of the order that the usage information to be managed precedes,
The compressed usage information length management unit 5 manages a numerical value other than “0” corresponding to the number of Japanese characters in the common portion, and the usage information management unit 6 manages only the Japanese information that follows the common portion.
On the other hand, when the usage information to be managed does not have a common part with the usage information in the preceding order as the starting point, the compressed usage information length management unit 5 manages “0” and the usage information management unit 6 Manage all Japanese information of usage information.

As described above, in the usage dictionary of the present invention, when there is a common part with the usage information of the preceding rank, the usage information management unit 6 of the subsequent usage information does not manage the common Japanese information part. Therefore, the usage information can be managed according to the memory capacity smaller than that of the conventional technique.

〔Example〕

Hereinafter, the present invention will be described in detail with reference to an embodiment according to an address dictionary.

FIG. 2 shows the configuration of an embodiment of the present invention. In this embodiment, as in the case of FIG. 4 described above, the address dictionary manages the address information "Osaki, Unoki-cho, Kawakita-gun, Ishikawa Prefecture" following the address information "Nichikaku, Unoki-cho, Kawakita-gun, Ishikawa Prefecture". Consider an example. In the figure, as explained in FIG. 1, 1 is a reading length management unit, 2 is a compression reading length management unit, 3 is a reading management unit, 4 is a usage information length management unit,
Reference numeral 5 is a compression usage information length management unit, 6 is a usage information management unit, and the items with the identifier "a" are related to "Inner corner of Unoke-cho, Kawakita-gun, Ishikawa prefecture" managed as address information in the previous rank. On the other hand, those related to the management department are those related to "Osaki, Unoki-cho, Kawakita-gun, Ishikawa Prefecture" that are managed as address information in the second rank.

As shown in this embodiment, in the present invention, the reading length management unit 1a is a method of reading this address information in order to manage "Hikaku in Unoki-cho, Hebei-gun, Ishikawa Prefecture" as the address information in the first rank. The number of characters "21" in "Ishika-Ikenen Kahokungun Unokemachi Uchihisumi" is managed, and the compressed reading length management unit 2a has a reading part that is common to the address information that is managed immediately before this address information. The number of characters “0” is managed to indicate that there is no, the reading management unit 3a manages how to read this address information according to the EBCDIC code, and the usage information length management unit 4a reads “Hikaku in Unoke-cho, Kawakita-gun, Ishikawa prefecture”. JE is twice the number of Japanese
Manages the F code length of "26", and compresses information length management unit 5a
Manages the JEF code length "0" to indicate that there is no Japanese information common to the address information managed immediately before this address information, and the usage information management unit 6a JEF for Japanese information on "Uchinomikaku, Unoke-cho, Kawakita-gun, Ishikawa Prefecture"
Manage according to code.

On the other hand, in order to manage "Osaki in Unoke-cho, Hebei-gun, Ishikawa Prefecture" as the address information of the second rank, the reading manager 1b uses the reading method of this address information. The compressed reading length management unit 2b manages the number of characters "20" and is a reading part that is common to the address information "Uchinomikaku, Unoke-cho, Kawakita-gun, Ishikawa Prefecture" that is managed immediately before this address information. The number of characters "16" in "Ishika Nyan Kahokungun Unokemachi" is managed, and the reading management unit 3b follows the EBCDIC code for "Osaki," which is the address information that is managed immediately before and the part that does not have the same reading method. The usage information management unit 4b manages the JEF code length "24", which is twice the number of Japanese words in "Osaki, Unoki-cho, Kawakita-gun, Ishikawa Prefecture", and the compression usage information length management unit 5b manages 1 The address information managed in front is "Uno, Kawakita-gun, Ishikawa Prefecture". It is a common Japanese information part of the town date angle "2 Japanese number of" Ishikawa Prefecture, Hebei County, Unoke-cho "
It manages double the number of JEF code, "20", and the usage information management unit 6b manages "Osaki", which is the Japanese information part that is not common with the address information managed immediately before, according to the JEF code. .

As described above, according to the present invention, when the managed address information has the common part starting from the first character and the address information in the preceding rank, the compression purpose information length management unit 5 determines the number of Japanese characters in the common part. The usage information management unit 6 manages only the Japanese information following the common part and does not manage the common Japanese information. Then, even when the common part of the address information is generated from the address information of the preceding order which is further before the preceding stage, the use information management unit 6 of the address information of the order following the generation source is the common part. Only the Japanese information that follows is managed, and the common Japanese information is not managed. From now on, since it is not necessary to manage the common Japanese information part of the address information in duplicate, the address information can be managed according to a memory capacity smaller than that of the conventional technique.

To explain it concretely in the example of FIG. 2, the reading management unit 3a
21 bytes, 26 bytes in usage information management unit 6a, reading management unit 3b
4 bytes for the application information management section, 4 bytes for the usage information management section 6b, and 1 byte for each of the other management sections. Therefore, in accordance with the present invention, “Uchinomikaku, Unoku-cho, Kawakita-gun, Ishikawa Prefecture” When "Osaki" is managed, a total of 63 bytes will be required, whereas the conventional method shown in FIG. 4 has a total of 81 bytes, which means that the memory capacity can be reduced by 18 bytes.

FIG. 3 shows a flowchart for setting data in the compressed usage information length management unit 5 and usage information management unit 6. As shown in this flowchart, first, the compressed JEF code length (JEF code length to be compressed as a common Japanese information part) stored in the compression purpose information length management unit 5 is initialized, and then, The JEF code of the immediately preceding word and the JEF code of the comparison word managed as the next order are judged in character units, and when they match, the compressed JEF code length is counted up and compared. The character positions that do not match are obtained by updating the character positions of the words, and the count-up value at this time is set as the compressed JEF code length in the compression application information length management unit 5, and the set compressed JEF is set. When the code length is “0”, the JEF code of the comparison word is directly set in the usage information management unit 6, and when the set compressed JEF code length is not “0”, the comparison word is set. Only the non-compressed portion, which is the non-common portion in the JEF code, is set in the usage information management unit 6.

〔The invention's effect〕

As described above, according to the present invention, the dictionary size memory capacity can be greatly reduced. This is particularly effective for a data processing system that uses a plurality of dictionaries.

[Brief description of drawings]

FIG. 1 is a principle block diagram of a data format of use information managed by a use dictionary according to the present invention, FIG. 2 is a configuration diagram of an embodiment of the present invention, and FIG. 3 is a compressed use information length management unit and use information management FIG. 4 is a flow chart for setting data in a section, and FIG. In the figure, 1 is a reading length management unit, 2 is a compression reading length management unit, 3 is a reading management unit, 4 is a usage information length management unit, 5 is a compressed usage information length management unit, and 6 is a usage information management unit.

Claims (1)

[Claims] 1. In a usage dictionary that manages usage information described in Japanese in a prescribed order, the usage information corresponding to the usage information is common, and the usage information to be managed starts from the preceding usage information and the first character. A compression purpose information management unit (5) that manages a numerical value according to the number of Japanese characters in the common part when there is a part, and a zero value when there is no common part; and the compression purpose information management unit (5). When the compression usage information management unit (5) is provided in a pair format and manages a non-zero value, it manages only Japanese information following the common part of the usage information to be managed, and a zero value. When managing, the application information management unit (6) that manages all the Japanese information of the application information to be managed is provided to thereby manage the application information described in Japanese. When Use a dictionary that.