JPH033063A - Application information control system in applied dictionary - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed Description of the Invention] [Summary] Regarding a usage information management method in a usage dictionary that manages usage information for each usage described in Japanese in a prescribed order, the memory capacity of the required dictionary size can be reduced. The purpose of this is to display the character length of the common part to determine whether each usage information has a common part starting from the first character with the usage information managed as the preceding one. In addition, when this character length is displayed as having a length, the character information following the common part is also managed.

[Industrial application field]

The present invention relates to a usage information management method in a usage dictionary that manages usage information written in Japanese according to a prescribed order, and in particular to an usage information management method for a usage dictionary that manages usage information written in Japanese according to a prescribed order. This relates to a usage information management method in a separate dictionary.

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

[Prior Art] There is a usage dictionary that manages specific usage information such as addresses and names in ascending order. FIG. 4 shows the configuration of the prior art of such a usage-specific dictionary using an address dictionary as an example. In this example, the address dictionary contains address information such as "Nichikaku, Unoke-machi, Kahoku-gun, Ishikawa Prefecture." Next, we assume an example where address information is managed such as ``Osaki, Uki-machi, Kahoku-gun, Ishikawa Prefecture''.

As shown in this figure, in the conventional address dictionary, each address information is divided into "reading length", "compressed reading length", "yomi", "JEF
It was configured to be managed in accordance with the ``JEF Code'' and the ``JEF Code''. Here, "JEF" is the identification name of the Japanese code system used, and is specifically explained using the address information of "Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture", which is managed in the ■ area in the diagram. In this case, the number of characters ``20'' is registered in the entry column of ``Long Reader'', which is the pronunciation of ``Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture.'' In the entry column of "Compressed reading length", the number of characters of "Ishikawakenka Hokugun Unokemachi" which is the common pronunciation with "Ishikawa Prefecture Kahoku District Unoke Town Uchinikaku" managed in the previous ■ area is displayed. “16
” is registered, and in the entry field of “Reading”, “Osaki”, which has a different reading from the previous address information, is registered.
The code is registered, and the entry field for "JEF length" is
"24'", which is twice the number of characters for "Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture", is registered, and the code for "Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture" is registered in the entry column of "rJEF code". That will happen. Here, twice the number of characters is registered in the entry column of ``rJEF length'' because ``JEF'' expresses one Japanese character in 2 bytes.

In this way, in purpose-specific dictionaries such as conventional address dictionaries,
Regarding how to read the managed usage information, we tried to reduce the size of the dictionary by compressing data in common parts.

[Problem to be solved by the invention]

However, in the conventional usage-specific dictionary, the entry column for "rJEF code" is not configured to compress data even if there are common parts. In other words, if we look specifically at the example in Figure 4, the managed address information ``Uchihikaku, Unoke-machi, Kahoku-gun, Ishikawa Prefecture'' and ``Osaki, U-ki-machi, Kahoku-gun, Ishikawa Prefecture'' are the address information of ``Ishikawa Although there was a common part, ``Unoke Town, Kahoku District, Prefecture,'' the rJEF code was configured so that it was managed as is, without data compression.

In the future, it will be necessary to have multiple dictionaries, and the memory capacity required for the dictionaries will increase, creating the problem of putting pressure on other operational modes.

The present invention has been made in view of the above circumstances, and provides a dictionary for each purpose that manages usage information written in Japanese in accordance with a prescribed order, which is configured to compress data for the usage information as well. The purpose is to solve the problems of the prior art.

[Means to solve the problem]

FIG. 1 is a diagram illustrating the basic structure of a data former 7) for usage information managed by usage dictionaries according to the present invention.

In the figure, 1 is a reading long tube ring part, which manages the number of characters in the reading method of managed usage information in 1 byte, and 2 is a compressed reading long tube ring part, which is used to read the leading character starting from the first character. 3 is a reading management part that manages the number of characters in the common reading with the ranking usage information in 1 byte, and 3 is the reading management part, which is the character in the reading that is not common in the usage information that is not managed by the compressed reading long tube ring part 2. 4 is a usage information length management section that manages information in 1 byte according to the number of Japanese characters in usage information to be managed;
Reference numeral 5 is a compression usage information length management unit that manages, in one byte, a value corresponding to the number of Japanese characters in the common part with the usage information of the preceding rank starting from the first character, and 6 is a usage information management unit. For example, the Japanese information of the non-common parts in the usage information that is not managed by the compression usage information length management unit 5 is
It is managed by code.

When there is a common part starting from the first character and the first character of the usage information, the compression usage information length management section 5 manages a value other than "O" according to the number of Japanese characters in the common part, and the usage information management section 6 Only the Japanese information following the common part is managed. On the other hand, when the usage information to be managed does not have a common part starting from the first character with the usage information in the preceding order, the compression usage information length management section 5 manages "0", and the usage information management section 6 Manage all Japanese usage information.

In this way, in the purpose-specific 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 following usage information does not manage the common Japanese information part. As a result, usage information can be managed according to a smaller memory capacity than in the prior art.

[Effect]

In the present invention, the order in which the usage information to be managed comes first [Example] The present invention will be described in detail below according to an example according to an address dictionary.

FIG. 2 shows the configuration of an embodiment of the present invention. In this embodiment, the address dictionary manages the address information ``Oosaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture'' following the address information ``Nichikaku, Unoke-machi, Kahoku-gun, Ishikawa Prefecture'', as in Figure 4 above. Among the six diagrams assuming an example, as explained in FIG. 1, 1 is the reading long pipe ring part, 2 is the compressed reading long pipe ring part, 3 is the reading management part, 4 is the usage information length management part,
5 is a compression usage information length management unit, 6 is a usage information management unit, and those with the identifier “a” are related to “Nichikaku, Unoke-machi, Kahoku-gun, Ishikawa Prefecture”, which is managed as address information in the previous rank. It is related to the management department, and on the other hand, information with the identifier "b" is managed as address information in the next rank.
This is related to the management department of "Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture."

As shown in this example, in the present invention, in order to manage "Nichikaku, Unoke-cho, Kahoku-gun, Ishikawa Prefecture" as the address information in the first rank, the reading long pipe ring part la is set according to the reading method of this address information. Manage the number of characters "212" in "Ishikawa Kenka Hokugun Unokemachi Uchihisumi", and the compressed reading of the long pipe ring part 2a is,
The number of characters "0" is managed to indicate that there is no common pronunciation with the address information managed immediately before this address information, and the pronunciation management unit 3a sets the pronunciation of this address information to E.
The usage information length management unit 4a manages the JEF code length "26", which is twice the number of Japanese characters in "Ishikawa Prefecture Kahoku District Uki-machi Uchihikaku", according to the BCD I C code,
The compression usage information length management unit 5a manages "θ" of the JEF code length to indicate that there is no Japanese information in common with the address information managed immediately before this address information, and manages the usage information management. The unit 6a manages the Japanese information of the address information "Nichikaku, Unoke-machi, Kahoku-gun, Ishikawa Prefecture" according to the JEF code.

On the other hand, in order to manage "Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture" as the address information in the latter rank, the long reading pipe ring part 1b uses the reading method of "Ishikawa-kenka-hoku-gun-unoke-machi-o" as the address information in the next rank. Managing the number of characters “20” for “Saki”, the compressed reading long tube ring portion 2b is
The number of characters in "Ishikawakenka Hokugun Unokemachi", which is the common pronunciation with "Uchihikaku, Unokemachi, Kahoku District, Ishikawa Prefecture", which is managed one address before this address information, is "16".
”, and the reading management unit 3b manages the address information that is managed one level earlier and the reading is different from the address information “4 Osaki”.
is managed according to the EBCDIC code, and the usage information length management unit 4b manages the JEF code length ``24'', which is twice the number of Japanese in [Osaki, Uki-machi, Kahoku-gun, Ishikawa Prefecture].
The compression usage information length management unit 5b stores the Japanese number of "Unoke-machi, Kahoku-gun, Ishikawa Prefecture", which is the common Japanese information part with "Nichikaku, Unoke-machi, Kahoku-gun, Ishikawa Prefecture" of the address information managed immediately before. The usage information management unit 6b manages the JEF code length "2G" which is twice the number of JEF code lengths, and uses the JEF code length "Osaki" to
Manage according to F code.

As described above, in the present invention, when the address information to be managed has a common part starting from the first character with the address information of the previous rank, the compression usage information length management unit 5 performs the following according to the number of Japanese characters in the common part. In addition, the usage information management section 6 is configured to manage only the Japanese information following the common part and not to manage the Japanese information of the common part. Even if the common part of the address information is generated from the address information of the preceding rank that precedes the previous stage, the usage information management unit 6 of the address information of the rank following the origin of the occurrence generates the Japanese information following the common part. The configuration is configured so that the Japanese information in the common parts is not managed.From now on, there will be no need to manage the common Japanese information parts of the address information redundantly. This allows address information to be managed using a smaller memory capacity.

To explain specifically using the example of FIG. 2, the reading management section 3a
21 bytes are required for the usage information management section 6a, 26 bytes for the usage information management section 6a, 4 bytes for the reading management section 3b, 4 bytes for the usage information management section 6b, and 1 hide for each of the other management sections. Ishikawa Prefecture, Kahoku District, U)ki Town, Uchihikaku”
and "Osaki, Unoke-machi, Kahoku-gun, Ishikawa Prefecture" would require a total of 63 bytes, whereas the conventional method shown in Figure 4 requires a total of 81 bytes, which means that the memory capacity can be reduced by 18 bytes. Become.

FIG. 3 shows a flowchart for setting data in the compression usage information length management unit 5 and usage information management unit 6. As shown in this flowchart, first, the length of the compressed JEF code stored in the compression usage information length management unit 5 (JEF code length, which is to be compressed as a long common Japanese information part) is initialized, and then 1 JEF of the previous word
JEF of the comparison word managed as the code and this next rank
Judge whether the codes match or not on a character-by-character basis, and if they match, count and amplify the compressed JEF code length while updating the character position of the comparison word to find the character position where there is a mismatch. The count-up value at the time is set in the compression application information length management unit 5 as the pressure 41 JE F code length, and the set compression JE
When the F code length is “0”, the JEF of the comparison word
In addition to setting the code as it is in the usage information management unit 6, if the set pressure 1i1 JEF code length is not “0”, only the uncompressed part that is a non-common part in the JEF code of the comparison word is stored in the usage information management unit 6. Set.

〔Effect of the invention〕

As described above, according to the present invention, the memory capacity of the dictionary size can be significantly reduced.

From now on, it will be particularly effective for data processing systems that use multiple dictionaries.

[Brief explanation of drawings]

Figure 1 is a diagram showing the basic structure of the data format of usage information managed by the usage dictionary according to the present invention, Figure 2 is a diagram showing the configuration of an embodiment of the invention, and Figure 3 is a diagram showing the compression usage information length management unit and usage. A flowchart for setting data in the information management section, FIG. 4 is an explanatory diagram of the prior art. In the figure, l is the reading length management section, 2 is the pressure Im reading length management section, and 3
4 is a reading management section, 4 is a usage information length management section, 5 is a compression usage information length management section, and 6 is a usage information management section.

Claims (1)

[Claims] In a usage dictionary that manages usage information for each usage written in Japanese in a prescribed order, each usage information is
The system is configured to manage whether or not there is a common part starting from the first character with usage information that is managed as a preceding rank by displaying the character length of the common part, and if the character length is long. When displaying as having
Further, a usage information management method in a usage-specific dictionary, characterized in that the usage information management method is configured to manage character information following the common part.