JPH0442350A - Character processor - Google Patents

Abstract

PURPOSE:To attain the field-based KANA (Japanese syllabary)/KANJI (Chinese character) conversion at a high speed by preparing a single field-based dictionary and retrieving the field-based words via a single bus at retrieval of the dictionary. CONSTITUTION:A CPU serving as a microprocessor performs the arithmetic operations, the logical decision, etc., for character processing and controls the component elements connected to an address bus AB, a control bus CB, and a data bus DB via these buses. Then just a single field-based dictionary is prepared not several types of them, and the field information is described to each word in the dictionary for decision of a field at conversion. Thus the field-based KANA/KANJI conversion is attained at a high speed.

Description

[Detailed Description of the Invention] [Industrial Field of Application] The present invention creates sentences containing kanji and kana through kana-kanji conversion,
This invention relates to a human-powered character processing device.

``Prior Art'' Currently, character processing devices such as 5 Japanese word processors generally use kana-to-kanji conversion to manually convert sentences containing kanji and kana.

This kana-kanji conversion converts the input pronunciation sequence into kanji by referring to a dictionary. Generally speaking, in kana-kanji conversion, if the number of words in the dictionary is small, the word desired by the operator cannot be converted, resulting in a low conversion rate, and if the number of words is large, there is a possibility that the word desired by the operator will be converted. However, if the number of words increases too much and even words from special fields are registered in the dictionary, all of the operator's undesired words will be converted, resulting in a poor conversion rate. Sometimes it happens.

For example, the pronunciation sequence ``Totsukiyoukikai'' is usually converted to ``Tokyo Kikai'' and is divided into 5 and 7. However, if the place name "Tokyo" and the place name "Kankai" are registered,
The pattern of 10 place names is preferentially converted for use in manually determining addresses, and is sometimes converted to ``Tokyo Kankai.'' In this case, for an operator who has no idea about address input, the conversion rate will actually drop because of the abundance of registered place names.

Therefore, a method called field-specific dictionaries has been proposed in order to increase the conversion rate of unreliable documents.゛A field-specific dictionary is a dictionary that stores words for each major field, and operators can perform optimal conversion by selecting and converting field-specific dictionaries that suit their purposes. can. In the above example, an operator whose purpose is to input an address specifies a field-specific dictionary for place names and converts it, and an operator who does not intend to input an address specifies a standard dictionary and converts it. By doing this, ordinary operators will use a standard dictionary, so even if they manually say "Dokyo Kikai", it will be correctly converted to "Tokyo Kikai". In addition, since the operator who inputs the address uses a dictionary by place name field, "Tokyo Kikai"
conversion will fail, but the conversion rate will be higher when you enter an address instead.

There are two methods for realizing this field-specific dictionary.

The first method is to set up a standard dictionary that stores universal words that do not belong to a specific field, and on the other hand, prepare a field-specific dictionary that stores only words from special fields. This method is achieved by searching and converting both the dictionary and the field-specific dictionary for the specified field.

The second method is to prepare a dictionary in which the contents of the standard dictionary and the contents of a specific field-specific dictionary are merged in advance. In this method, only one dictionary needs to be searched during conversion.

[Problems to be Solved by the Invention] However, the above-mentioned first method and second method for realizing a field-specific dictionary both have serious problems.

If the first method is followed, processing time during conversion will be burdened.

In other words, if you are only converting a standard dictionary, you only need to search in one dictionary, but if a field is specified, you will have to search in another dictionary, and the conversion will be done to compensate for the extra search processing. It takes time.

If you follow the second method, you only need to search the dictionary once, so there is no burden on the conversion time, but if the number of fields increases, the number of field-specific dictionaries will increase dramatically. For example, if there are only four fields: ``place names,''``history,''``architecture,'' and ``medicine.'' It is necessary to prepare 16 types of field-specific dictionaries, such as "Dictionary of place names + History field,""Dictionary of place names, Land and architecture field,""Dictionary of place names, biomedical field," and "History + Architecture field."

[Means for solving the problem (and action)] The present invention has the following features:
Instead of preparing multiple types of field-specific dictionaries, only one dictionary is prepared, field information is written for each word in that dictionary, and the field is determined at the time of conversion, thereby achieving high-speed field-specific conversion. It is something to do.

[Example] The present invention will be described in detail below with reference to the drawings.

FIG. 1 is an example of the overall configuration of the present invention.

In the illustrated configuration, the CPU is a microprocessor that performs calculations, logical judgments, etc. for character processing, and includes an address path AB, a control path CB, and a data path D.
B to control each component connected to those paths.

Address path AB transfers address signals indicating the components to be controlled by the microprocessor CPU. The control path CB transfers and applies control signals for each component to be controlled by the microprocessor CPU. The data path DB transfers data between each component device.

Next, ROM is a read-only fixed memory, and the first
Microprocessor CP, which will be described later with reference to Figures 5 to 22.
The control procedure by U is memorized.

The RAM is a writable random access memory with a 16-bit word structure, and is used for temporary storage of various data from each component. I BtJF is an input buffer that stores key data entered manually,
0BUF is an output buffer that temporarily stores the results of kana-kanji conversion. DIC is a dictionary for performing kana-kanji conversion. BCTBL is a phrase candidate table that stores phrase candidates that are currently being converted. TBUF is a text buffer in which text data being edited manually is stored. DOBUF is a homophone buffer, and when a homophone candidate exists for a character stored in the text buffer TBUF, that candidate is stored. 5BUNF is a system field flag, and when converting kana to kanji, a flag that specifies the field of the word to be converted other than the standard field is stored.

KB is a keyboard, which includes character/symbol input keys such as alphabet key, hirakana key, katakana key, conversion key, next candidate key, selection key, field setting key, field save key, field call key, execution key, It is equipped with various function keys, such as a release key, for instructing various functions to the character processing device.

The DISK is an external storage section for storing document data, system flags, illustration data, graphic data, etc. Documents created on the text buffer TBUF, system field flags, etc. are stored in this external storage section. The stored data can be recalled when necessary using keyboard instructions.

CR is a cursor register. The CPU can read and write the contents of the cursor register.

A CRT controller CRTC, which will be described later, displays a cursor at a position on the display device CRT corresponding to the address stored here.

DBUF is a display buffer memory that stores data patterns to be displayed. When displaying text contents, a display pattern is created in DBUF according to the contents of text buffer TBUF, and the text is displayed.

CRTC is cursor register CR and buffer DBUF
It plays the role of displaying the contents stored in the CRT on the display device CRT.

Further, a CRT is a display device using a cathode ray tube or the like, and a CRT controller controls the dot-configured display pattern and cursor display on the display device CRT.

Furthermore, CG is a character generator that stores patterns of characters and symbols to be displayed on the display device CRT.

The character processing device of the present invention, which is composed of each of these components, operates in response to various inputs from the keyboard KB, and when the input from the keyboard KB is supplied, the included signal is first sent to the microprocessor CP.
The microprocessor CPU reads various control signals stored in the ROM, and various controls are performed in accordance with these control signals.

FIG. 2 is a diagram showing an example of conversion for each field by the apparatus of the present invention. In the figure, r//J means to press the conversion key there. All of the conversion examples are for the case where ``Habikinoshikkonta no Oujinden no Uriou'' is given as the input reading string.

2-1 is a diagram showing an example of conversion in the standard field. In response to the input, the first candidate is converted to ``Oujin Emperor's dormitory with cargo that was trained in Habikino''. This is because the field of (place name) (history) is not set, so the place name ``Honda'', the personal name ``Ojin'', and the noun ``Ryo'' do not exist, resulting in incorrect translation.

2-2 is a diagram showing an example of conversion in the standard field + place name field. In response to the input, the first candidate is converted to ``Ouujin Emperor Dormitory for Habikino Shigesho.'' This is because the field of (history) has not been set, so the person's name ``Ojin'' and the noun ``Ryo'' do not exist, resulting in incorrect translation. Compared to 2-1 (
Since the field of place name) has been set, the place name ``Honda'' can be converted.

2-3 is a diagram showing an example of conversion between the standard field and the history field. In response to the input, the first candidate is converted to "Emperor Ojin's mausoleum with cargo, which was built in Habikino." This is because the field of (place name) has not been set and the place name ``Honda'' does not exist, so it is misconverted. Compared to 2-1, the field of (history) is set, so the personal name ``Ojin'' and the noun ``Ryo'' can be converted.

2-4 is a diagram showing an example of conversion in the standard field + place name field + history field. In response to the input, the first candidate is correctly converted as ``Emperor Ojin's tomb located in the Habikino camp.''

FIG. 3 is a diagram showing an example of field setting and saving operations.

3-1 shows the initial screen.

Normal document creation and editing is done on this screen. The angle line indicates the position of the cursor.

3-2 shows the screen when the field setting key is pressed. The cursor is at the first setting item, ``Place name field''. For each field, "0" means that words in that field are not converted, and "1" means that words in that field are converted. In the screen 3-2, since all fields [rO,j are set, it means that words in any field are not converted, but only words in the standard field are converted. If you press the key "1" here, the screen 3-3 will appear. In 3-3, the setting item in the place name field is Fll, which means that the words in the place name field can now be converted. The cursor has moved to the next setting item, the history field. If you press the key "1" again, the screen 3-4 will appear. Here, the setting item for the history field is also changed to "IJ," which means that words in the history field can also be converted.The cursor moves to the next setting item, the architecture field.Here When you press the field save key, the currently displayed field status (the state in which the words of the standard field + place name field and history field are converted) is saved in the external storage unit DISK,
The screen becomes 3-5. This screen is no different from screen 3-4. If the execution key is pressed here, the field information is updated, the field setting screen disappears, and the screen returns to the original document editing screen as shown in 3-6.

FIG. 4 is a diagram showing an example of a field calling operation. 4-1
is the initial screen for normal document creation and editing. If the field call key is pressed in this state, the field information existing in the DISK will be called up and the screen will appear as shown in 4-2, for example. This example shows "Standard field + Place name field + Architecture field" in the DISK.
This indicates that the field information for the conversion happened to have been saved. It is also possible to perform the operation described in FIG. 3 in the state 4-2. If the execution key is pressed as it is, the field setting screen disappears and the screen returns to the original document creation/editing screen as shown in 4-3.

FIG. 5 is a diagram showing an example of an operation for converting kana to kanji. 5
-1 is an initial screen for performing document creation and editing. Reading sequence “
If you enter "Habikinoshikonda", the screen shown in 5-2 will appear.

In 5-2, the cursor is displayed next to the input reading string. If you press the conversion key here, the screen shown in 5-3 will appear. 5
In -3, the pronunciation sequence "Habikinoshikonda" is converted to "Habikino tuneiyo j".The operator wants to convert "Habikino city kanyen" and presses the next candidate key, 5-
4 screen will appear. Here, conversion candidates for "Konda" are displayed. The first candidate is "Honda" and the second candidate is "Kinyen"
It is. The current candidate is the second candidate "Kinyen", and 2 is highlighted. If you press the selection key here, 5-
5 screen will appear. The second candidate "Kinyen" is determined and stored in the text data, and at the same time "Kinyen" is learned.
Word likelihood is improved.

Figure 6 shows input buffer I BUF and output buffer 0BU.
It is a figure showing the composition of F.

Both IBUF and 0BUF have the same configuration. first 2
The byte is size information for each buffer, and contains a value obtained by subtracting 1 from the number of characters stored in the buffer and multiplying it by 2. r//J at the end of the input buffer means that the conversion key was pressed there. Each character is 1 character 2
It consists of bytes and is stored in JIS X 0208 code.

FIG. 7 is a diagram conceptually showing the stored contents of the kana-kanji conversion dictionary DIC. Each word consists of fields for ``pronunciation,''``orthography,'' ``part of speech,'' ``word likelihood,'' and ``field information.''

"Yomi" means the reading of the word, "notation" means the notation of the word, "
``Part of speech'' stores the part of speech of a word.

"Word Likelihood" stores information indicating the likelihood of the word itself, such as frequency information, as a value of 1 to 5.

A likelihood value of 5 means the most likely, and the smaller the value, the more doubtful it is. Since the likelihood value O means that it is completely unthinkable, it does not exist as a word likelihood value.

"Field information" includes multiple fields in which the word is used, such as (place name) (history) (architecture) (medicine), etc. - Boat fishing. No field information is written for words that do not belong to a specific field.

FIG. 8 is a diagram showing the specific structure of the kana-kanji conversion dictionary DIC.

8-1 shows a storage structure for words other than standard fields.

The reading uses the lower byte of the JIS X 0208 code, and has a variable length of 1 byte per character.

Since this is the lower byte of the JIS X 020g code, the MSB of each byte is OFF. The field consists of one byte, and the word field is set in bit correspondence as shown in the figure. When a word belongs to that field, 1 is stored in the corresponding bit, and when the word does not belong, O is stored. M
SB is turned ON. Therefore, the field value range is 0x80
~0x8f. The notation uses the JIS X 0208 code and is stored in a variable length of 2 bytes per character. However, the MSB of each byte is turned ON. JIS X 02
Each byte of the 08 code has a value of Ox21 to 0x7e, so each byte of the 2 notation is Ox a l = Ox f
falls within the range of e.

The part of speech consists of one byte, and the part of speech code of the word is stored. MSB is turned off. The frequency also consists of one byte, and the MSB in which the frequency of the word is stored is O.
It will be FF.

8-2 shows the storage format of words in the standard field. It is roughly the same as the storage format for words other than standard fields, but the difference is that fields are not included. In addition, the field value range (Ox21 to 0x7e) and the notation value range (Ox
al~0xff) are different, so by checking the value, you can tell whether there is a field after the reading or whether there is a notation.

FIG. 9 is a diagram conceptually showing the storage contents of the clause candidate table BCTRL. The phrase candidate table is a binary tree representation of possible phrase candidates as a result of the analysis of the input reading. In the figure, the horizontal line means a child pointer,
The vertical line means the first pointer. The second pointer links another clause candidate (usually a shorter candidate) starting from a certain reading position, and the child pointer links the clause candidate that follows that clause.

The beginning of the input pronunciation string ``Habikinoshikonda'' has the following interpretations: ``Habikino'', ``Tooth'', and ``Leaf'', and these are linked in order by the pointer (vertical line).

The phrase that follows ``Habikino'' is thought to be ``Shikumita''.
Linked by child pointer.

Once a phrase candidate table like this is completed, it will be translated into words such as ``Habikino Shimashita'' and ``Habikino Shigeonyo J ``Habikino Shimashita''.
``It is easy to create a string of bunsetsu candidates, such as ``tobuki-noshi-sho-dej''.

FIG. 10 is a diagram showing the specific structure of the phrase candidate table BCTBL.

"Independent word" stores a pointer to the top position in the dictionary where the independent word of the bunsetsu candidate exists.

The "adjunct word string" consists of 2 bytes, and is an area for specifying the adjunct word string that follows the independent word of the bunsetsu candidate. The first 1 byte indexes the first character of the attached word string on the input buffer, and the next 1 byte indexes the last character of the attached word string on the input buffer. For example, when using the large buffer shown in Figure 6, to express ``da'', the first byte contains 12
, set 14 in the second byte. When an adjunct word string does not exist, it is indicated by "φ" in the figure.

The "first link" links another clause candidate that starts from the same reading position as the clause candidate.

"r-flat link" links the clause candidate that follows the clause candidate.

Note that a link is terminated when the value is 0.

For example, the No. 1 link of phrase candidate 0 (Habikino) is 50, which links phrase candidate 50 (teeth). The child link of phrase candidate 0 (Habikino) is 100, which links phrase candidate 100 (prepared). The child link of phrase candidate 100 is O, and it can be seen that the input reading ends there.

FIG. 11 is a diagram showing the structure of the text buffer TBUF.

A text buffer consists of a sequence of characters, each character consisting of 2 bytes. The MSB of each character is a homophone flag, where 0 means a normal letter and l means a homophone. The remaining 15 bits represent the character code in the case of normal characters, and the homophone number in the case of homophones. The character code is J
Use IS X 020g code. The homophone number is a number indicating which homophone is on the homophone buffer DOBUF shown in FIG.

FIG. 12 is a diagram showing the configuration of the homophone buffer D OB' UF. Each homophone is identified by a homophone number.

Each homophone is "reading", "total number of candidates", "current candidate number"
It consists of "i-th candidate information".

"Yomi" stores the reading of the same sound 3go.

"Total number of candidates" stores the total number of candidates included in the same sound.

The "current candidate number" stores the currently displayed candidate number of the homophone. Since the first candidate is displayed as the initial value immediately after conversion, rlJ is stored.

The "i-th candidate information" stores the "notation J" word address" of each candidate.

"Notation" stores the notation of the candidate.

The "word address" stores the address where the word exists.

FIG. 13 is a diagram showing the configuration of the system field flag 5BUNF.

It has almost the same structure as the field information for each word in the dictionary DIC, and specifies the field of the word to be converted. If only words in the standard field need to be converted, bits in all fields may be turned OFF. The difference from the field information of each word in the dictionary DIC is that the MSB is OFF.

FIG. 14 is a diagram showing the configuration of the external storage section DISK.

As shown in 14-1, the inside of the DISK is divided into a plurality of areas according to the data stored therein. For example, when document data TBUF is stored in l0SK, it is stored in the document data storage area. The system flag storage area exists only in one place in the DISK and stores various flags related to the system.

14-2 shows a further detailed configuration of the system flag storage area. For example, it consists of a system field flag, conversion mode (immediate conversion, - bracket conversion, etc.), selection mode (automatic selection, specified selection, etc.), and input mode (Romaji input, kana input, etc.). System field flag 5BUN
When F is saved on the DISK, it is saved in the area shown in 4-2 "System field flag".

The operation of the above-mentioned embodiment will be explained in accordance with the flowcharts shown in FIG. 15 and subsequent figures.

FIG. 15 is a flowchart of the part that takes in key human power and performs processing.

Step 15-1 is a process of capturing data from the keyboard. In step 15-2, the type of the retrieved key is determined, and the process branches to a processing routine for each key.

If it is a conversion key, the process branches to step 15-3, and in step 15-3, conversion processing for kana-kanji conversion is performed as detailed in FIG. 16. If it is the next candidate key, the next candidate process detailed in FIG. 19 is performed in step 15-4.

If it is the selection key, the second key is pressed in step 15-5.
The selection process detailed in Figure 0 is performed.

If it is the field setting key, field setting processing detailed in FIG. 21 is performed in step 15-6.

If it is a field call key, the field call process detailed in FIG. 22 is carried out in step 15-7, and then the process branches to field setting process in step 15-6.

If it is any other key, the process branches to step 15-8, and other processing such as insertion, deletion, etc. performed in a normal character processing device is performed.

When the processing of each key is completed, the process branches to step 15-1.

FIG. 16 is a detailed flowchart of the "conversion process" in step 15-3.

In step 16-1, a phrase candidate creation process detailed in FIG. 17 is performed to create a phrase candidate table BCTBL.

In step 16-2, a first candidate determination process is performed to determine the most likely conversion candidate from the created phrase candidates.

In step 16-3, a conversion result is created and output based on the determined first candidate.

FIG. 17 is a detailed flowchart of the phrase candidate creation process j in step 16-1.

In step 17-1, the input buffer index i and phrase candidate table index j are initialized to zero.

In step 17-2, a dictionary is searched based on the pronunciation in the power buffer indicated by i, and a list of word candidates is created.

In step 17-3, as detailed in FIG.
``Field check processing'' is performed to check whether the created word candidates are appropriate based on the system field flag settings, and to omit those that are not appropriate.

In step 17-4, morphological analysis processing is performed to analyze adjunct word strings connected to the listed word candidates. As a result, phrase candidates are obtained.

The phrase candidates obtained in step 17-5 are stored in the phrase candidate table. When storing, it is stored in the j±1st entry. Also, set the necessary information. For example, for a phrase candidate whose child or first phrase is this phrase candidate, a child link and a first link are set. After storing, count up the value of j.

In step 17-6, an unterminated phrase candidate, that is, a phrase candidate whose child link has not yet been determined, is found in the phrase candidate table, and the next reading position is determined.
Assign to .

In step 17-7, it is determined whether the child links of all clause candidates have been determined, and if there are any child links that have not been determined, the process branches to step 17-2. Otherwise, return.

FIG. 18 is a detailed flowchart of the "field check process" in step 17-3.

In step 18-1, one word candidate is selected from the list.

In step 18-2, it is determined whether or not all word candidates have been checked, and if so, the process returns. If not finished, step 18-3
Proceed to.

In step 18-3, whether a field is described in the word candidate (whether it is a standard field word or not)
If the field is not described, the word belongs to a standard field, and the process skips to step 18-7. If the field has been described, proceed to step 18-4.

In step 18-4, the system field flag 5BU
NF, field information of word candidates, all ANDs of OxOf
(logical product) and check whether the word candidate is a single word in the field to be converted.

In step 18-5, the above value is determined and 0
In this case, it is not a word to be converted, so step 18-6
is excluded from the list of word candidates. If it is not O, the process branches to step 18-7, and the word candidate is left in the list.

Thereafter, the process loops to step 18-1 to process the next word candidate.

FIG. 19 is a detailed flowchart of the "next candidate processing" in step 15-4.

In step 19-1, the homophone number of the homophone to be viewed as the next candidate is obtained from the text buffer TBUF.

In step 19-2, the position of the homophone buffer is determined from the homophone number, and the current candidate number is counted up.

In step 19-3, a list of candidates is displayed.

FIG. 20 is a detailed flowchart of the "selection process" in step 15-5.

In step 20-1, the homophone number of the homophone to be selected is obtained from the text buffer TBUF.

In step 20-2, the position of the homophone buffer is determined from the homophone number, the notation is extracted from the candidate information indicated by the current candidate number, and is set as a confirmed character in the text buffer TBUF.

In step 20-3, a word address is similarly obtained from the candidate information indicated by the current candidate number, and the word likelihood of the indicated word is counted up.

However, if the word likelihood is already 5, no count-up is performed.

In step 20-4, a word address is similarly obtained from the candidate information indicated by the first candidate, and the word likelihood of the indicated word is counted down. However, if the word likelihood is already 1, no countdown is performed.

FIG. 21 is a detailed flowchart of the "field setting process" in step 15-6.

In step 21-1, the original screen state is saved and the field setting screen is displayed.

In step 21-2, the current value of the system field flag 5BUNF is saved.

In step 21-3, data from the keyboard is captured.

In step 21-4, the type of the retrieved key is determined, and the process branches to a processing routine for each key.

When the key "1" is pressed, the process branches to step 21-5, and the bit of the corresponding field of the system field flag 5BUNF is set to 1. Also, move the cursor to the next setting item.

When the key FOJI is pressed, the process branches to step 216, and the bit of the corresponding field of the system field flag 5BUNF is reset to O. Also, move the cursor to the next setting item.

When a screen-related key (such as a cursor movement key) is pressed, the process branches to step 21-7, and screen control processing such as cursor movement is performed.

When each process in steps 21-5, 21-6, and 21-7 is completed, the process branches to step 15-1 and waits for the next key input.

When the field save key is pressed, the process branches to step 218, and the system field flag 5BUNF is stored in the external storage unit DIS.
Save it in the designated category of K. Then step 21
Branch to −10.

When the release key is pressed, the process branches to step 21-9, and the value of the system field flag is restored to the saved value. Thereafter, the process branches to step 21-10.

When the execution key is pressed, the process branches to step 21-10, the screen is restored to the state before the field setting key was pressed, and the process returns.

FIG. 22 is a detailed flowchart of the "r field calling process" in step 15-7.

In step 22-1, the current value of the system field flag 5BUNF is saved.

In step 22-2, the value of the system field flag in the system flag storage area in the external storage section DISK is retrieved.

In step 22-3, the above extracted value is set to 5B.
Assign to UNF and return.

[Other Embodiments] In the above description, it has been explained that there are only four types of fields, but dictionaries of any field can be processed in the same way.

[Effects of the Invention] As is clear from the above explanation, according to the present invention, field information is included in the dictionary, so there is no need to prepare multiple field-specific dictionaries (and only one dictionary is required). Since all you have to do is search for , you can achieve high-speed kana-kanji conversion by field.

As a result, the operator does not encounter erroneous conversion due to the presence of a word in a field that is not desired by the operator, making it possible to realize a comfortable character processing device with a high conversion rate.

[Brief explanation of the drawing]

Fig. 1 is a block diagram of the overall configuration of a character processing device according to the present invention, Fig. 2 is a diagram showing an example of kana-kanji conversion in the present invention, and Fig. 3 is a diagram showing field setting and storage operations in the present invention. Figure 4 is a diagram showing an example of the field calling operation in the present invention. Figure 5 is a diagram showing an example of the kana-kanji conversion operation in the present invention. Figure 6 is a diagram showing an example of the operation of kana-kanji conversion in the present invention. A diagram showing the configuration of the power buffer I BUF and the output buffer 0BUF, FIG. 7 is a diagram conceptually showing the storage contents of the kana-kanji conversion dictionary Drc in the present invention, and FIG. 8 is a diagram showing the storage contents of the kana-kanji conversion dictionary Drc in the present invention. FIG. 9 is a diagram conceptually showing the storage contents of the bunsetsu candidate table BCTBL in the present invention, and FIG. 10 is a diagram showing the specific structure of the bunsetsu candidate table BCTBL in the present invention. FIG. 11 is a diagram showing the configuration of the text buffer TBUF in the present invention. FIG. 12 is a diagram showing the configuration of the homophone buffer DOBUF in the present invention. FIG. 13 is a diagram showing the configuration of the system field flag 5BUN in the present invention.
FIG. 14 is a diagram showing the configuration of the external storage section DISK according to the present invention. FIGS. 15 to 22 are flowcharts showing the operation of the character processing device according to the present invention. DISK...External storage CPU...Microprocessor ROM
...Read-only memory RAM ...Random access memory I BUF ...Oiriki buffer 0BUF ...Output buffer IC CTBL BUF 0BUF BUNF ...Kana-kanji conversion dictionary ...Bunsetsu candidate table ...Text buffer ... Homophone buffer ... System field flag ↓ Reading input ↓ Conversion key diagram ↓ Next candidate key ↓ Selection key Homophone number Figure (14-1) External storage DISK configuration 2 System flag storage area configuration

Claims (1)

[Scope of Claims] 1. An input means for inputting a pronunciation sequence, a dictionary means that stores pronunciations, notations, and fields in correspondence, and is not classified by field, and specifies which field of words should be converted into. field information storage means for storing field information to be stored in the field information storage means; field setting means for setting field information in the field information storage means; conversion means for converting the input reading string into notation based on the dictionary means; control means for controlling the conversion means to use different words for conversion according to the description in the field information storage means when converting into notation; A character processing device characterized in that a character is searched in one pass.