JP2024007582A - Kearm fixed conversion of japanese input system - Google Patents

Abstract

To provide a method that can process kana-kanji conversion and KEARM conversion simultaneously.SOLUTION: The present method causes transition from a kana-kanji conversion screen to a KEARM conversion screen or transition from a regular conversion screen of KEARM conversion to a screen with translation conversion (conversion between two languages of KEARM conversion) to be realized by simply pressing a KEARM fixed conversion key.SELECTED DRAWING: Figure 1

Description

"Kana-Kanji Conversion/KEARM Conversion Japanese Input System" (an exact match search type sequential conversion Japanese input system described in Non-Patent Document 2, hereinafter also referred to as the Kana-Kanji Conversion/KEARM Conversion System) is a combination of Kana-Kanji conversion and KEARM Conversions can be processed concurrently, but in order to give priority to kana-kanji conversion, KEARM conversion has the following constraints: (1) ``Katakana words that have the same reading as kanji are not converted to KEARM'' and (2) ``The term attribute is the initial value. When , KEARM conversion becomes forward conversion.'' The present invention allows regular KEARM conversion to be performed with simple operations for constraint (1), and forward conversion of KEARM conversion (input string and conversion result) for constraint (2) with simple operations. This is a method that allows you to perform translation conversion (conversion between two languages in KEARM conversion) instead of (conversion that results in the same character type).

KEARM conversion is ``Katakana (K) by kana input, English (E) by half-width alphanumeric input, English abbreviation (A) or Romaji (R), 3 categories (K, E, A, or R), 4 inputs. It is a conversion method that can perform multilingual processing and is named after the acronym "Conversion that can mutually convert (K, E, A, and R) and can also output multilingual (M)."

The present invention is also item (5) "KEARM standard conversion of Japanese input system" of the multifunctional Japanese input system described in paragraph number 0025 of Non-Patent Document 2, and the multifunctional Japanese input system shown in FIG. 21 of this book. In the block diagram of the word input system, this corresponds to the ``KEARM standard conversion'' located in the center of the screen and the ``KEARM standard conversion key'' in the upper left (both backgrounds are shown as blocks with a dot pattern). The multifunctional Japanese input system shown in FIG. 21 is a system that has 12 functions added to the core of the Kana-Kanji conversion/KEARM conversion system (the part indicated by the gray block in the background).

Regarding the constraint (1) of KEARM conversion described in paragraph number 0001, "Katakana words that have the same reading as kanji are not converted to KEARM", for example, if the input string is "man", there are kanji that can be converted, so katakana " Performs only the sequential conversion of kana-kanji conversion using ``man'' without performing KEARM conversion using ``man''. When the KEARM standard conversion key (logical key, physical key is the Tab key) is pressed from the successive conversion screen, regular KEARM conversion is executed using the KEARM standard conversion of the present invention. At this time, if the term attribute value of the katakana word "man" is the initial value (the symbol "/", the numerical value -1), the input string "man" will be translated (bilingual conversion of KEARM conversion). , if the output language is English, the conversion result will be English man, and if the output language is French, the conversion result will be French homme. To perform KEARM conversion of the katakana word "man" which has the same pronunciation as a kanji character, in addition to the KEARM fixed form conversion of the present invention, there is a KEARM priority conversion described below.

KEARM priority conversion literally gives priority to KEARM conversion over kana-kanji conversion, so it is possible to perform KEARM conversion using the input string ``man'' in katakana ``man''. However, as shown in the block diagram of the multifunctional Japanese input system in FIG. 21, the "KEARM priority conversion execution unit" 56 belongs to the "batch conversion unit" (b) at the bottom of FIG. Conversion will not start until a certain KEARM priority conversion key is pressed. On the other hand, "kana-kanji conversion/KEARM conversion execution units" 4 to 33 belonging to (a) "successive conversion unit" in the upper part of FIG. 21 start kana-kanji conversion immediately when "man" is input, Since KEARM conversion is prohibited due to description constraint (1) in paragraph number 0001, only kana-kanji conversion will be performed in the successive conversion when "man" is input. If priority is given to KEARM conversion in successive conversion, normal kana-kanji conversion will not be possible, so it is unavoidable to give priority to kana-kanji conversion in successive conversion. Therefore, it cannot be said that KEARM priority conversion necessarily takes precedence over kana-kanji conversion, so the feature of KEARM priority conversion is that it can perform predictive conversion using partial match searches such as prefix match search and suffix match search. KEARM priority conversion refers to item (6) "KEARM priority conversion of Japanese input system" of the multifunctional Japanese input system described in paragraph number 0025 of Non-Patent Document 2, and the details are in the document scheduled to be filed separately. I will explain.

For KEARM conversion constraint (2) described in paragraph number 0001, "KEARM conversion is a forward conversion when the term attribute is the initial value," KEARM By pressing the standard conversion key, you can execute translation conversion, which is a KEARM conversion between two languages. Regarding constraint (2) of KEARM conversion, if you change the term attribute value in the KEARM learning conversion of the Japanese input system of Non-Patent Document 3, which is another invention, you can change the output order of conversion candidates, so you can select the desired candidate. This can be done as a conversion result, but if you change the term attribute value, you must change the attribute value again to return to the initial term setting value -1. The KEARM fixed form conversion of the present invention allows translation conversion, which is bilingual conversion of the KEARM conversion, to be easily executed with the KEARM conversion in its initial state.

Basic functions of Kana-Kanji conversion system JISX4064: 2002

Kana-kanji conversion/KEARM conversion type Japanese input system Patent application 2022-017542 (paragraph numbers 0085-0087, 0104-0105, 0118-0119, 0123-0124, 0127-0129, 0131-0133, 0135-0136, 0138-0139 , 0180-0181, 0197-0218, Fig. 23, Fig. 25, Fig. 27, Fig. 28, Fig. 29, Fig. 30, Fig. 31, Fig. 32, Fig. 42, Fig. 46)

KEARM learning conversion of Japanese input system Patent application 2022-080529

The Kana-Kanji conversion/KEARM conversion system can perform KEARM conversion simultaneously with Kana-Kanji conversion. However, since the purpose of a Japanese input system is to input kana and convert it into a sentence containing kanji through kana-kanji conversion, the KEARM conversion function has to be subordinate to the kana-kanji conversion function. The results are KEARM conversion constraint (1) ``Katakana words that have the same reading as kanji are not converted to KEARM'' and constraint (2) ``KEARM conversion is a forward conversion when the term attribute is the initial value.'' .

Add the necessary components and logical keys (KEARM fixed form conversion key) to add the KEARM fixed form conversion function to the Kana/Kanji conversion/KEARM conversion system, and execute sequentially under constraint (1) or constraint (2). By pressing the KEARM fixed form conversion key while the conversion screen is displayed, KEARM fixed form conversion is executed for each clause that can be converted sequentially from the first clause on the successive conversion screen, and constraints (1) and constraint (2) are executed. And, based on the attribute value registered in the KEARM conversion dictionary of the term targeted for KEARM conversion, regular KEARM conversion or translation conversion (conversion between two languages in KEARM conversion) is performed. As mentioned above, the KEARM fixed-form conversion is designed based on processing multiple clauses, but in reality, users are likely to mainly execute it on single clauses.

The Kana-Kanji conversion/KEARM conversion system can process KEARM conversion and Kana-Kanji conversion at the same time, but if both Kana-Kanji conversion and KEARM conversion are possible, KEARM conversion must be canceled or KEARM conversion cannot be executed. The first candidate for conversion is the same as the character type of the input string to ensure compatibility with kana-kanji conversion. The present invention can transition from the Kana-Kanji conversion screen to the KEARM conversion screen by simply pressing the KEARM standard conversion key, which is an operation key, from the successive conversion screen in the above state, or from the forward conversion screen of KEARM conversion to translation conversion (KEARM conversion). You can transition to a screen that allows you to convert between two languages.

For forward conversion of KEARM conversion (conversion where the input character string and conversion result are the same character type), use KEARM learning conversion in Non-Patent Document 3 to change the term attribute value of the KEARM conversion dictionary to obtain the conversion result. Although the first conversion candidate can be selected, the present invention can easily perform translation conversion (bilingual translation of KEARM conversion) by simply pressing the operation key while maintaining the conversion state equivalent to the Kana-Kanji conversion in the initial state of KEARM conversion. conversion). Since the term attribute value is not changed, the state of KEARM conversion that prioritizes kana-kanji conversion can be maintained from next time onwards.

This is a screen showing a method for dealing with two constraints (1) and (2) of KEARM conversion in the Kana-Kanji conversion/KEARM conversion system. Block diagram of a system that incorporates the necessary components (areas surrounded by dotted lines) to add the KEARM standard conversion function to the Kana-Kanji conversion/KEARM conversion system. Output order of conversion candidates for KEARM standard conversion (translation conversion) An explanatory diagram of the operation of the “KEARM standard conversion execution unit” 55 in Figure 2 Explanation diagram of Katakana KEARM conversion operation in ``Kana-Kanji conversion/KEARM conversion execution unit'' 4 to 33 in Figure 2 Diagram explaining the KEARM conversion operation for English, English abbreviations, and Roman characters in Figure 2 "Kana-Kanji conversion/KEARM conversion execution unit" 4 to 33 Detailed diagram of “conversion unit” 9 in Figure 5 (KEARM conversion of Katakana) Detailed diagram of "conversion section" 9 in Figure 6 (KEARM conversion of English, English abbreviations, and Roman letters) Term attributes of KEARM conversion dictionary KEARM conversion dictionary (StdWork0 to StdWork9 for selected language) Example 1 KEARM conversion of katakana with the same reading as kanji (1) Screen transition diagram for executing KEARM standard conversion from the successive conversion screen for single phrase, single term, exact match search, output language is English, attribute value -1 Example 2 KEARM conversion of katakana with the same reading as kanji (2) Screen transition diagram for executing KEARM standard conversion from the successive conversion screen for single phrase, single term, exact match search, French, and attribute value 0 Example 3 KEARM conversion of katakana with the same reading as kanji (3) Screen transition diagram for executing KEARM fixed conversion from the successive conversion screen for simple clause, single term, single character search, output language is French, attribute value 5 Example 4 KEARM conversion of katakana with the same reading as kanji (4) Screen transition diagram for executing KEARM standard conversion from the successive conversion screen for single clauses, multiple terms, and the output language is English Example 5 KEARM conversion of katakana with the same reading as kanji (5) Screen transition diagram for executing KEARM fixed conversion from the successive conversion screen for single clauses, multiple terms, and the output language is French Example 6 KEARM conversion of Katakana with the same reading as Kanji (6) Screen transition diagram for executing KEARM standard conversion from a single phrase, a single term, and a sequential conversion screen with multiple output languages Example 7 KEARM conversion of katakana with the same reading as kanji (7) Screen transition diagram for executing KEARM standard conversion from a single clause, multiple terms, and sequential conversion screen with multiple output languages Example 8 KEARM conversion of Katakana with the same reading as Kanji (8) Screen transition diagram for executing KEARM standard conversion from a sequential conversion screen with complex clauses, multiple terms, and the output language is English Example 9 KEARM conversion with initial value of term attribute (1) Multiple screen transition diagram for executing KEARM fixed form conversion from the successive conversion screen of single phrase and various output languages Example 10 KEARM conversion with initial value of term attribute (2) Screen transition diagram for executing KEARM fixed conversion from the successive conversion screen for complex clauses and output language as German Block diagram of multifunctional Japanese input system

This book uses various terms, so I will explain them first. JISX4064 prescribed terms and computer terms are not included here. There is no difference in the level of terminology explanation in paragraph number 0016 between the Kana-Kanji conversion/KEARM conversion system and the system shown in Figure 2 which incorporates the necessary components to add the KEARM standard conversion function to the system. Both systems will be referred to as the present system.

(A) Summary of terms Terms are explained individually in no particular order. Since the terminology for the linking function of the multifunctional Japanese input system is not directly related to the present invention, only the title is listed.
(A) Japanese Input System This is a Japanese input system using a kana-kanji conversion method (specified in JISX4064 or a system equivalent thereto), and is a Japanese input system for a personal computer that is combined with a computer keyboard and a monitor of sufficient size. Search methods include a ``batch conversion type'' that uses an exact match search, and a ``predictive conversion type'' that uses a prefix search. Although this system is a batch conversion type, it is a ``successive conversion type'' that has a conversion activation section and repeats batch conversion by exact match search for each input character. Although the "predictive conversion type" is also a successive conversion formula using a prefix search, here we distinguish a method that is a successive conversion formula using an exact match search and can also perform KEARM conversion as a "successive conversion formula."
(a) (a) Batch conversion formula
After inputting a character string, the JISX4064 Kana-Kanji conversion system divides the input string into segments based on the kanji reading and performs exact match search and conversion in order from the beginning of the sentence. After conversion, you can also edit the phrases by changing the break position of the phrases or selecting other candidates for each phrase. Finally, press the confirm key to collectively output the conversion candidates for each clause as the conversion result as a confirmed character string.
(a) (b) Predictive conversion type When you input 1 to 3 characters, the system automatically starts converting, converts the input character string to the kanji reading, and presents multiple predictive conversion candidates based on the prefix search. A method in which the user selects the desired candidates one by one to create a final character string. However, if the user continues to input without selecting a candidate, the number of predictive conversion candidates gradually decreases, and in the end there is only one candidate based on an exact match search, resulting in an operation similar to (c) successive conversion method. However, KEARM conversion and sound output are not possible.
(a) (c) Sequential conversion method This system's method follows the exact match search and conversion method of JISX4064, and adds a conversion startup section that starts a new conversion for each character input, and further improves the conventional An exact match search type successive conversion system that adds KEARM conversion and pronunciation functions to Kana-Kanji conversion with various functions such as multilingual processing, selection of search method, change of output order of conversion candidates, change of input mode after conversion, etc. It is. The features of this method are that it can successively generate conversion candidates that completely correspond to the input character string, and that it can perform KEARM conversion and pronunciation output. Similar to batch conversion formulas, you can also edit after conversion.
(B) Input mode This system has six modes: hiragana, katakana, full-width alphanumeric, half-width katakana, half-width alphanumeric, and MP mode, as well as a direct input mode in which the Japanese input system does not intervene. The first five modes are the same as commercially available systems, and the MP mode is not used in the present invention. Katakana for KEARM conversion is entered in hiragana, katakana, or half-width katakana mode, and English, English abbreviations and Roman characters for KEARM conversion are entered in half-width alphanumeric mode. In half-width alphanumeric mode, the background color of input characters is designed to be yellow-green. When performing KEARM conversion in half-width alphanumeric mode, it is in conversion mode and the input string is underlined with a dotted line. However, there is also a non-conversion mode in half-width alphanumeric mode. In this system, if you switch to half-width alphanumeric mode without inputting anything, it will enter non-conversion input mode, and if you switch to half-width alphanumeric mode in the middle of a sentence, it will enter conversion mode. To enter conversion mode when no input has been entered, press and hold the [Kanji] key, a low beep will sound, and you will be in half-width alphanumeric mode where you can convert.
(c) Output language One of the 10 languages can be selected as the output language using the mouse. The default setting is English (English), and English is standard equipment, and if you select a language other than English (Korean to Arabic), English + selected language will be installed. When set to multilingual, words from 10 languages are listed in the conversion candidate list.
(c) (a) Output language selection switch
A switch that allows you to select the output language of KEARM conversion using the mouse.
(c) (b) Selected language (c) Among the output languages selected with the output language selection switch in (a), 10 languages other than multilingual (multilingual) from English (English) to Arabic (a) are selected. Although it is a selected language, English is the standard output language, so if English is in a separate frame, the other nine languages other than English are called selected languages.
(d) Dictionaries This system uses a kana-kanji conversion dictionary, a user dictionary, a KEARM conversion dictionary, and an automatically generated dictionary. The kana-kanji conversion dictionary has standard contents and cannot be changed. User dictionaries and KEARM conversion dictionaries have tools that allow users to add, change, and delete registered words. Automatically generated dictionaries are automatically created and deleted by the system as necessary.
(D) (a) Dictionary for Kana-Kanji Conversion This dictionary is located in "Dictionary for Kana-Kanji Conversion" 36 in Figure 2 and is used for Kana-Kanji Conversion.
(D) (b) User Dictionary Located in "User Dictionary" 37 in Figure 2, it is used for the learning function of Kana-Kanji conversion. The conversion candidates for KEARM conversion are a set of fixed-form candidates, so a user dictionary is not used.
(d) (c) Dictionary for KEARM conversion This dictionary has the structure shown in Figure 10 and is used in KEARM conversion.
(d) (d) Automatically generated dictionary
In order to process half-width alphanumeric character strings and full-width alphanumeric symbols/signs for compound phrases that are not registered in the KEARM conversion dictionary, the system automatically registers the strings in a special dictionary. It will not be updated and will be overwritten and deleted after the conversion is completed.
(e) Conversion mode Although there are successive conversion, new prediction conversion, KEARM priority conversion, and MP mode, only the successive conversion mode is used in the present invention.
(e) (a) Sequential conversion A mode in which conversion is performed by exact match search for each character input, and performs kana-kanji conversion, ANS conversion, KEARM conversion, and automatically generated dictionary conversion. For English input and kana input for KEARM conversion, if you set the term attribute value of the KEARM conversion dictionary to 4 or higher, you can also convert one character by searching for one character. Even in a single character search conversion, there is still a one-to-one correspondence between a single input character and a conversion candidate.
(F) Operation mode
There are ND, ADP, AD and ARP modes. Only the ND mode is used to convert single clauses such as words and phrases, and the order of ND --> ADP --> AD mode is used to convert sentences. The ARP mode becomes 1 when executing the KEARM standard conversion of the present invention, and is 0 during other conversions.
(F) (a) ND (Non-Div)
Used to convert single clauses such as words and phrases. Even when converting a string that is a compound clause, it is necessary to first check whether it is a simple clause or not, so start the conversion from ND mode.
(f) (b) ADP (AutoDivProcess)
A character string that is a compound clause is divided into clauses sequentially, starting from the first clause, and subjected to kana-kanji conversion, ANS conversion, KEARM conversion, or automatically generated dictionary conversion. The purpose of conversion in ADP mode is to select the most suitable conversion candidate for each clause.
(f) (c) AD (AutoDiv)
After completing the conversion in ADP, return to the first clause in AD mode and convert the input buffer ss11[0] again as the conversion string. From then on, when the phrase is moved using the left and right arrow keys, the conversion is performed in the same way using the input buffer ss11[n] (n is the phrase number 0 to 49) as the conversion character string. Conversion in AD mode is called AD conversion. The purpose of AD conversion is to obtain the maximum number of conversion candidates. However, the standard for kana-kanji conversion is limited to five candidates.
(f) (c) ARP (AutoRecProcess)
If you press the KEARM standard conversion key while the KEARM conversion successive conversion screen is displayed, the ARP mode becomes 1 and KEARM standard conversion is executed in ADP mode at the same time. Using the input buffer ss11[n] (n is the clause number from 0 to 49) as the conversion string, convert the clause numbers of clauses that can be converted to KEARM (clause information ArrayAuto[n][3] is 1, 3, or 6). KEARM conversion is performed in ascending order of age, and finally, AD conversion is performed on the first clause that has undergone KEARM conversion, a list of conversion candidates for that clause is displayed, and the operation ends in AD mode. The KEARM standard conversion also ends and the ARP mode becomes 0.
(g) Input/output character display The part that displays input/output character strings on the screen of an application program. Although this part does not have a screen frame, it has a display structure, and the displayed character strings are underlined according to the display attributes. In successive conversion, the input string becomes a display string of the same character type and is used as an input character display. After transitioning to the conversion candidate list screen, conversion results that are selection candidates are displayed instead of display character strings.
(g) (a) Input string A character string input into this system from the keyboard is divided into a display string and a conversion string in the input processing section, and is actually used for input display through successive conversion. are display strings of the same character type.
(g) (b) Display character string This character string has the same character type as the input character string and is used to display the input character string on the input/output character display screen of the application program.
(g) (c) Conversion character string A character string used as a search input during conversion. If the input character string is kana, full-width katakana is used. For alphanumeric characters and symbols, the input string becomes the conversion string as is.
(g) (d) Display attributes For input/output character display, specify the display attributes and draw a unique underline for the character string. By default, the display attribute on the successive conversion screen is "input" (dotted line), and on the conversion candidate list screen, the segment the user is working on is marked as "converted notable phrase" (solid thick line), and other clauses are marked as "input" (dotted line). They are distinguished by "converted clauses" (solid thin lines).
(g) (e) Conversion result The character string displayed on the input/output character display after the transition from the successive conversion screen to the conversion candidate list screen is the selected candidate and is called a conversion result. In the initial operation using the conversion operation transition key, the first conversion candidate becomes the conversion result, but other candidates can also be directly selected using the mouse. In a compound clause, the character string is a combination of not only the relevant clause but also the output buffer ss12[n] (n is clause number 0 to 49) from the first clause to the final clause. When you press the confirm key, the conversion result becomes a fixed string.
(h) Successive conversion screen Although this screen is just for inputting character strings, this system has a conversion startup section, so it performs successive conversion for each input character, displays a list of conversion candidates for simple clauses, and displays a list of conversion candidates for complex clauses. Then, a character string that is a combination of the first conversion candidates for each phrase is displayed. Kana-Kanji conversion uses only exact match search, but KEARM conversion allows not only exact match search but also single character conversion. The input/output character display displays a display string of the same character type as the input string.
(h) (a) Single-character search As shown in the attribute value setting table in (a) and (c) of "Term attributes of KEARM conversion dictionary" in Figure 9, the attributes of registered terms in English and Katakana in the KEARM conversion dictionary. If the value is set to 4 or more, the search method when executing KEARM conversion will be a single character search. One-character search searches and converts one character, but the search target terms are only registered terms, which is different from normal prefix search that searches and converts one character. Even in the conversion of a single character search, there is still a one-to-one correspondence between a single input character and a conversion candidate.
(h) (b) Output order (for successive conversion screen)
The output order of conversion candidates on the successive conversion screen of KEARM conversion (arrangement order starting with the first conversion candidate) is based on the term attribute value of the relevant KEARM conversion dictionary, according to the attribute value setting table shown in (a) to (c) in Figure 9. It can be changed as follows. The initial value of the term attribute value is -1, and the first conversion candidate for KEARM conversion at this time is forward conversion, which is the same as the first conversion candidate for the conventional kana-kanji conversion system. Attribute values can be set separately in three categories: (a) English, (b) English abbreviations or Roman letters, and (c) Katakana attribute value setting table.
(h) (c) Conversion output (for successive conversion screen)
The conversion output is a string output obtained by conversion, and is processed as follows in Kana-Kanji conversion, ANS conversion, and KEARM conversion. The output obtained by integrating and unifying one or more conversion outputs becomes conversion information szBufz.
(1) In Kana-Kanji conversion, a Kana-Kanji conversion dictionary and a user dictionary are used to search and convert each character input using a conversion character string as input. For example, if the conversion character is ``shi'' and the obtained conversion candidates are ``shi'', ``shi'', ``ushi'', ``shi'', etc., these conversion candidates are arranged in chronological order and converted into a character variable. Save it and get the string information ``Shi City Mr. Shi Death...''. This string information becomes the converted output. Place the control character \0 at the end of each candidate for conversion output. The conversion output is divided into classes (called item numbers) according to the part of speech of the dictionary, etc., and adverbs and nouns (item number 4) are classified as character variables szBufa, nouns + particles (item number 5) as character variables szBufb, and verbs (item number 8). is stored in the character variable szBufc, and the user dictionary (mainly item number 2) is stored in the character variable UserDic.
(2) ANS conversion is the conversion of alphanumeric symbols and codes that cannot be converted into kana-kanji, and is included in the function of kana-kanji conversion in a broad sense, similar to the JIS standard. All full-width alphanumeric symbols and codes are eligible. Of the half-width alphanumeric symbols and codes, half-width alphanumeric words and phrases registered in the KEARM conversion dictionary are subjected to the following (3) KEARM conversion, and the rest are converted to ANS. ANS conversion uses a user dictionary, an automatically generated dictionary, or a dedicated program without using a dictionary. Numbers and symbols are converted into full-width/half-width or half-width/full-width, and numbers are also converted into Chinese numerals. , parentheses, and other symbols are converted to various similar symbols. Character string information compiled from converted character strings as candidates becomes the conversion output. Place the control character \0 at the end of each candidate for conversion output. The noun (item number 4) is a character variable szBufa, the noun + particle (item number 5) is a character variable szBufb, the user dictionary (mainly item number 2) is a character variable UserDic, the program conversion of a single phrase (item number 1, item number 6) ) conversion output is saved in the character variable szSymbol.
(3) For KEARM conversion using half-width alphanumeric input, a KEARM conversion dictionary is used, and for each character input, the conversion string is used as a search input to search for registered terms in the dictionary. When the attribute value of the term is between -1 and 3, conversion is performed using an exact match search, conversion is stopped when one character is input, and conversion is performed when there is a complete match when two or more characters are input. For example, if the English attribute value of "rule" is the initial value -1, search and convert the conversion string "rule", save the obtained conversion candidates in a character variable in chronological order, and use the string information " rule rule rule, rule, ruler, solution ///'. If the attribute value is 4 to 8 (English only), conversion is performed using a single character search, and character string information equivalent to "rule" can be obtained by simply entering "r". Furthermore, when the attribute value is changed, the output order of conversion candidates and the input mode after conversion also change. The character string information at this time becomes the converted output. Place the control character \0 at the end of each candidate for conversion output. The conversion output is classified according to part of speech in the dictionary (called item numbers), and nouns (item number 4) are stored in szBufa, nouns + particles (item number 5) in szBufb, and conjugated verbs (item number 8) in szBufc. .
(4) For katakana conversion using kana input in KEARM conversion, the katakana word (synonymous with katakana) is extracted as a conversion candidate in the class-based conversion (items 2 to 8) using kana-kanji conversion in (1). In addition, only when kana-kanji conversion has not been performed, KEARM conversion is performed for the relevant katakana language. When the Katakana attribute value of the registered term is -1 to 3, conversion is performed using an exact match search. For example, when the attribute value of "rule" is -1, the obtained conversion candidates are stored in a character variable in chronological order, and the string information "rule rule, rule, ruler, solution ///" is obtained. The character string information at this time becomes the converted output. Place the control character \0 at the end of each candidate for conversion output. If the attribute value is set to 4 to 7, conversion will be performed using a single character search, but when inputting a single character in kana, kana-kanji conversion takes precedence, so KEARM conversion will not be performed. From this state, the KEARM fixed form conversion of the present invention can be executed to perform KEARM conversion or translation conversion (two-language conversion of KEARM conversion). The input mode after conversion remains kana mode.
(h) (d) Sequential conversion simple display screen
If there are multiple terms to be converted in KEARM conversion, if the output language is English, it will be displayed as "English + Simple Japanese Translation", and if the output language is in other selected languages (for example, French), it will be displayed in one line as "French + English". The character string information displayed becomes conversion candidate information for each term. This is a screen in which conversion candidate information for a plurality of terms is arranged in order, left-aligned and with a new line for each candidate.
(h) (e) Successive conversion confirmation key The first conversion candidate on the successive conversion screen is the output that corresponds one-to-one to the input character string (and display character string) at the time of conversion, and is the most suitable conversion. It is a candidate. In addition, since the first conversion candidate is a selection candidate, in this system, by pressing this logical key (the physical keys are Shift+Enter keys), the first conversion candidate can be output as a confirmed character string. Since the predictive conversion type does not have a one-to-one correspondence between input and output, it is necessary for the user to select a candidate.
(h) (f) Sound output key (for successive conversion screen)
On the successive conversion screen of KEARM conversion, the first conversion candidate is the selection candidate, and if you press this logical key (physical key is Ctrl + ←), the first conversion candidate of successive conversion will be pronounced.
(k) Conversion candidate list screen (also called conversion operation screen)
If you press the conversion operation transition key from the successive conversion screen, AD conversion will be performed, and the conversion operation screen will display a list of conversion candidates. In the case of a single clause, AD conversion is not performed because the conversion information szBufz obtained during successive conversion is used.
(k) (a) Output order (for conversion candidate list screen)
The output order of conversion candidates on the conversion candidate list screen (arrangement order starting with the first conversion candidate) is the same as the output order on the successive conversion screen when you press the conversion operation transition key to transition from the successive conversion screen to the conversion candidate list screen. However, if you execute KEARM standard conversion or KEARM priority conversion and transition to the conversion candidate list screen, the output order will be different.
(ke) (b) Conversion output (for conversion candidate list screen)
On the conversion candidate list screen, when you move a phrase to the left or right or click any phrase with the mouse, AD conversion is performed using the character string in the input buffer ss11[n] (n is 0 to 49) for each phrase as input. Similar to the conversion on the successive conversion screen, the candidate character strings obtained by AD conversion are arranged in chronological order and saved in character variables as the conversion output. For example, in the case of kana-kanji conversion, "shi shi shi shi shi..." is saved in a character variable and used as the conversion output. ANS conversion outputs full-width/half-width conversion, half-width/full-width conversion, Chinese numeral conversion, and various character type conversions, and KEARM conversion outputs conversions such as "rule, rule, ruler, solution ///". Become. In both conversion outputs, a control character \0 is placed at the end of each candidate. Kana input will be converted to kana-kanji, full-width alphanumeric symbol input will be converted to ANS, half-width alphanumeric input will be converted to KEARM, or character strings not registered in the dictionary will be converted to ANS using an automatically generated dictionary for compound phrases, but kana input will be converted to ANS. There is also a KEARM conversion by KEARM conversion is performed for kana input when the clause information ArrayAuto[n][3] obtained by successive conversion is 1. The method of summarizing the conversion output is almost the same as (h) (a) conversion output (for sequential conversion screen), and the final conversion output is saved in the character variable szBufz and used as conversion information.
(i) (c) Conversion operation transition This is an operation for transitioning from the sequential conversion screen to the conversion candidate list screen which is the conversion operation screen. The conversion operation transition key is a logical key, and the physical key differs depending on the purpose. Use physical keys such as the Space key for Kana-Kanji conversion, and the arrow ↓ key for KEARM conversion. If you directly click on the desired candidate with the mouse, you can perform the same function and select the candidate at the same time. By default, the conversion candidates for kana-kanji conversion display a list of up to five conversion candidates, the same as for sequential conversion. To display the maximum number of conversion candidates, use the [Convert] key as a physical key.
(i) (d) Selection candidates You can select the desired candidate on the conversion candidate list screen using the up and down arrow keys or the mouse. Candidates that can be selected are limited to the output language; Japanese translations and term attributes are not candidates that can be pronounced, so they cannot be selected using normal operations. The selected candidate is called a selected candidate. The background color of a single selection candidate becomes light blue, and the background color of the selection term candidate on the simple display screen when there are multiple terms to be converted becomes light red.
(i) (e) Conversion candidate simple display screen This is a simple conversion candidate list screen obtained by pressing the conversion operation transition key from the successive conversion simple display screen. Although the display form is the same, in the initial state of the conversion candidate simple display screen, the first conversion candidate is highlighted as a selection candidate, and at the same time, the selection candidate is displayed as a conversion result.
(k) (f) Pronunciation output key (for conversion candidate list screen)
On the conversion candidate list screen for KEARM conversion, pressing this logical key (the physical key is Ctrl+←) will produce the pronunciation of the selected candidate word.
(k) Kana-kanji conversion
Entering kana and converting it into a sentence with kanji. In systems other than this system, kana-kanji conversion is performed using the reconversion function or KEARM priority conversion. Kana-kanji conversion specified in JISX4064 also includes conversion of alphanumeric symbols and codes, so kana-kanji conversion in a broad sense also includes (sa)ANS conversion.
(Sa) ANS conversion Alphanumeric symbols and codes are called ANS (AlphaNumeric and Symbol). ANS full-width alphanumeric symbols are converted to half-width alphanumeric symbols (full-width/half-width conversion), half-width alphanumeric symbols are converted to full-width alphanumeric symbols (half-width/full-width conversion), and paired with each conversion string. Choose two conversion candidates. If it is a number, it is also converted to Chinese numerals. Codes such as parentheses are converted to various similar codes. For terms registered in the KEARM conversion dictionary in half-width alphanumeric English, English abbreviations, and Roman letters, KEARM conversion is performed instead of ANS conversion.
(C) Kanji information conversion, (S) Conversation text conversion, (C) New prediction conversion, (S) Reconversion function, (T) Memo function, (C) Kanji-kana conversion, (T) Kanji-hikana conversion, ( T) Sentence segmentation/conversion Neither of these are used in this system.
(g) KEARM conversion
This method uses the KEARM conversion dictionary to search and convert. There are 11 in total in the KEARM conversion dictionary, one for multiple languages and one for each language (Figure 10). KEARM conversion is based on three categories (K, E, A, or R): Katakana (K) by kana input, English (E) by half-width alphanumeric input, English abbreviations (A), and Romaji (R), and four inputs (K). , E, A, and R), as well as multilingual (M) output. The initials are K for Katakana, E for English, A for Acronym, R for Romaji, and M for Multilingual.
(g) (a) Forward conversion
When the term attribute of the KEARM conversion dictionary is -1 in the initial state, the first conversion candidate that becomes the conversion result of KEARM conversion is the same character type as the input string (and display string) (conversion from hiragana to katakana is possible) However, this is designed to have the same behavior as kana-kanji conversion). This is to ensure that even if KEARM conversion is executed, the conversion result will initially be equivalent to conventional kana-kanji conversion.
(n) Term attribute The initial setting of the term attribute in column number 7 of the KEARM conversion dictionary in Figure 10 is "///", and each "/" is the initial state of three classifications (K, E, A, or R). The first digit on the left is for English, the second digit in the middle is for English abbreviations/Romaji, and the third digit on the right is for Katakana.
(n) (a) Change of term attributes
The term attributes of registered terms in the KEARM conversion dictionary can be easily changed using KEARM learning conversion, but since the KEARM conversion dictionary is a Unicode text file, open the dictionary file with computer administrator privileges and change the attribute value of the term. You can also change it directly.
(d) KEARM learning conversion Not used in this system.
(nu) KEARM standard conversion
If you press the KEARM standard conversion key while the successive conversion screen for KEARM conversion is displayed, the input buffer ss11[n] (n is the phrase number) is used as the conversion string, and the phrases that can be converted to KEARM (clause information Array Auto [n][3] is 1, 3, or 6) Performs KEARM standard conversion in descending order of the clause number, and finally performs AD conversion of the first clause that has been subjected to KEARM standard conversion, and then converts the conversion candidate list or conversion for that clause. Display the candidate simple display screen and end the operation in AD mode.
(NU) (a) Translation conversion
With KEARM conversion, you can change the output order of conversion candidates in the conversion candidate list by changing the attribute value of the term attribute in the KEARM conversion dictionary. With the initial value of -1, even if KEARM conversion is performed, the input character string and the first conversion candidate that is the conversion result will be the same character type, so it is called a forward conversion. KEARM fixed form conversion can be performed by pressing the KEARM fixed form conversion key from the sequential conversion screen of forward conversion. It is called translation conversion because it converts words into Japanese katakana or words in the selected language.
(nu) (b) KEARM standard conversion key
The logical key to start KEARM standard conversion and the physical key is the Tab key.
Neither (N) KEARM detailed conversion nor (N) KEARM priority conversion is used in this system.
(c) Terminology information Alphanumeric symbols and symbols are distinguished by ANS (Alpha-Numeric and Symbol) codes 1 to 4 as shown below. Terms registered in the Kana-Kanji conversion dictionary and the user dictionary are given element information with a yougoCode of a to ? as shown below, which corresponds to 5 to 33 in numerical terms. 1 to 33, which is a combination of both, is used as static information, and 1 to 256, which takes into account the dynamic information (judgment of nouns, verbs, adjectives, etc.) obtained from the conversion outputs szBufa to szBufc, is used as term information for each conversion candidate. Save in szBufzcode[n] (n is a candidate number from 0 to 499). prevCode is terminology information for szBufzcode[0], which is the first candidate for conversion, and is used as information when converting the next clause. There is also prevCode1, which is used when a case particle is included in the relationship with the next clause. szBufzcode[n] is used to underline or change the background color when displaying conversion candidates on the screen.
(c) (a) Make ANS codes (Alpha-Numeric and Symbol) correspond to numbers 1 to 4.
1: Numbers 2: Alphabets 3: Symbols (#$, etc.) 4: Signs (“ ”, etc.)
(c) (b) yougoCode (it is used as needed, so it does not use everything)
Make the following code (a to ?) correspond to the numbers 5 to 33.
a: Last name b: First name c: Country name or place name in Tokyo d: Place name outside Tokyo e: Surname/first name/neutral noun f: Human noun 1 (-director, ~, etc.) g: Human noun 2 ( (Victim, carpenter, etc.) h: Human body parts i: Edible plants j: Vehicles k: Time period (~weeks, etc.) l: Animals m: Season (March, etc.) n: Natural phenomena o: Terrain/historical sites p: Adnominals・Conjunction q: Chinese r: Katakana onomatopoeia s: Memo function t: Kanji numerals v: General verb w: Verb of 5-dan conjugation onbin 2 x: Adjective y: Adjective verb z: Verb-based noun (surprise, etc.) and later Omitted ?: Former municipality name (Yono City, etc.)
The following codes (* and +) can be used together with the above codes (a to ?).
*: Used in kanji information conversion. When added, the value is increased by +120 and the background color of conversion candidates is changed to light yellow.
+: It is added when the kana-kanji conversion is confirmed twice, and when it is added, the value is +80, and the corresponding term is used preferentially.
(c) (c) prevCode (it is used as needed, so it does not use everything)
0: None 1: Numbers 2: Alphabetical characters 3: Symbols ($, etc.) 4: Signs (``, {, etc.) 5: Surname 6: Name 7: Country name or place name in Tokyo 8: Other place names 9: Surname/first name/ Neutral nouns 10: Human nouns 1 (-san, ~, etc.) 11: Human nouns 2 (victim, carpenter, etc.) 12: Human body parts 13: Food plants 14: Vehicles 15: Period (~ weeks, etc.) ) 16: Animals 17: Season (March, etc.) 18: Natural phenomena 19: Terrain/historical sites 20: Adnominals/conjunctions 21: Surnames other than the first candidate 22: Memo function 39: Noun clauses 40: Chinese numerals 60: Verbs ( 61: Verb (conjunctive form) 62: Verb (final/adjunctive form) 70: Adjective 1 (next clause is noun form) 71: Adjective 2 (next clause is verb or noun form) 80: Adverb equivalent 81: Verb form adverb (～te, ～de) omitted 94: KEARM conversion clause 97: AR conversion clause 102-118: Compound verb processing (keep buying, etc.) 126: KEARM fixed form conversion clause 130: Kanji-kana conversion clause (Ha ) (d) prevCode1 (Used when a case particle is involved in the relationship with the next clause. Used only when necessary)
0: None 1: Human noun + case particle (the victim goes there) 2: Quantitative noun + case particle (there are 3) 3: Human body parts + case particle (holds the legs) 5: Edible plant + case Particle (mandarin orange peel) 6: Vehicle + case particle (inside the bus) 7: Region + case particle (earthquake in Niigata) 8: Time/period + case particle (we will meet in March) 11: Not used 12: Terrain/ Historic site + case particle (castle ruins)
(c) (e) szBufzcode[n] (n is candidate number 0 to 499)
szBufzcode[n] is terminology information for all converted candidates, and is used to change the background color or underline the nth candidate.
(H) Conversion information Conversion output of successive conversion obtained by Kana-Kanji conversion, KEARM conversion, and ANS conversion The final conversion output obtained from the character strings szBufa to szBufc, UserDic, and szSymbol becomes conversion information szBufz. After successive conversion, press the conversion operation transition key (Space key, arrow ↓ key, etc.) to perform AD conversion. If the result of successive conversion is a compound clause, press the left or right arrow keys to move the clause and perform AD conversion in the same way. In AD conversion as well, the final conversion output obtained from the conversion outputs szBufa to szBufc and the character string information of UserDic becomes the conversion information szBufz. The conversion information is character string information indicating a list of conversion candidates.
(F) Output information The output information of successive conversion is conversion information szBufz indicating a list of conversion candidates for simple clauses, or ss12[0] to ss12[n, which lists the first conversion candidates of the conversion output of each clause of a compound clause. ] (n is the phrase number 0 to 49) depending on whether it is character string information. It is determined whether the conversion information is for a single phrase or the character string information for a compound phrase, and it is saved in the character variable szBufCan and used as output information. At this time, the standard for kana-kanji conversion is to limit the number of conversion candidates to a maximum of five. The output information of AD conversion is conversion information szBufz indicating conversion candidate list information for each clause.
(F) Clause information (excerpt only)
The term information is information on each clause and has information for each candidate, but the clause information is information as a representative clause. The character variable indicating clause information is ArrayAuto[n][m]. n is the phrase number from 0 to 49, and m is from 0 to 12.
(f) (a) ArrayAuto[n][2]: Clause information Save term information yougoCode.
(f) (b) ArrayAuto[n][3]: Clause information
1: Katakana KEARM conversion completed
3: English, English abbreviation or romaji KEARM conversion completed
6: If ArrayAuto[n][3] is 1 or 3 in a compound clause where Katakana KEARM conversion is possible, the first conversion candidate for the corresponding clause is underlined when displaying conversion candidates, and ArrayAuto[n][3] When is 6, the first candidate for conversion of the corresponding phrase is crossed out.
(f) (c) ArrayAuto[n][4]: Clause information When KEARM conversion of Katakana is possible, save the Katakana attribute nCharKanaAttri (0 to 8).
(f) (d) ArrayAuto[n][5]: Saves clause information term information prevCode.
(f) (e) ArrayAuto[n][6]: Saves clause information term information prevCode1.
(f) (f) ArrayAuto[n][8]: Clause information
Save the input character type information 10 to 12 below during KEARM conversion.
10: English input
11: Romaji input
12: Kana input
13: English abbreviation input (e) Input buffer/output buffer When converting multiple clauses, the conversion character string for each clause and the conversion first candidate or selection candidate of the conversion information obtained after conversion must be saved for each clause. . This is a buffer for storing character strings for each clause. There are KER buffers for input, output, and support, and it is possible to divide up to 50 phrases (n is the phrase number 0 to 49). Up to 128 character strings can be saved.
Input buffer ss11[n][128]: Saves the string for conversion of each clause.
Output buffer ss12[n][128]: Saves the first conversion candidate or selection candidate for each phrase.
KER buffer ss12k[n][128]: For auxiliary use. Not used in this system.
(Ma) List of functions (excerpt only, standard functions not included)
Most of them are newly developed, and some are added functions to existing functions.
(a) AlphaPhrase: Function for executing KEARM conversion/compound character type conversion (b) AddCharN: Function for executing output character display (c) ChangeDatabaseAttribute: Function for changing term attribute value (d) ConvCandidate: Function for executing conversion candidate display (e) ConvClipboard: Function for importing clipboard character strings (f) ConvPhrase: Function for executing kana-kanji conversion/ANS conversion/KEARM conversion/Kanji-kana conversion/kanji information conversion (g) ConvSound: KEARM pronunciation drive/character string specification function (h) ConvWord: KEARM word conversion function (i) ConvWordSound: KEARM pronunciation language identification function (j) DatabaseWrite: Dictionary change function (k) DicWrite: User dictionary registration function, also used to register automatically generated dictionaries (l) GetAlphaWord: KEARM conversion/conversation text conversion/kanji information conversion function (m) GetDatabaseWord: KEARM word search/conversion function (n) GetKanjiWord: Kanji-hiki-kana conversion function (o) GetRefWord: Kana-kanji combination information acquisition function ( p) GetRefaWord: Function for acquiring kana-English combination information (q) SetDatabaseAttribute: Function for setting term attribute value (mi) Variable (excerpt only)
(a) ARHenkan: Set to 1 when converting in English, English abbreviations, or Roman characters (b) ARP: Variable that becomes 1 when in ARP mode (c) ArrayStart: -1 when on the successive conversion screen, when on the conversion operation screen Featured clause number (n is 0 to 49)
(d) AutoLevel: An integer indicating the clause number at which the KEARM fixed-form conversion starts, which is nArray + 1. (e) AutoReconv: A variable that becomes 1 when ARP mode is started. (f) ChikujiHenkan: A variable that becomes 1 in successive conversion mode (g ) KEARMHenkan: Variable that becomes 1 when executing KEARM conversion (h) MpxHenkan: Variable that becomes 1 when executing KEARM standard conversion of multiple clauses (i) MultiSel: Set to 1 when there are multiple corresponding conversion target terms in multilingual conversion. Variable (j) nArray: Integer with clause number 0 to 49 (k) nKEARMStartArray: Integer indicating the first clause number to perform KEARM fixed conversion (l) nEnable: Integer for document analysis (m) n1: Integer in ND mode Character length of conversion character variable ss1 (n) n1Auto: Character length of ss1Auto (o) Romaji: Set to 1 when Romaji is registered in the term to be converted (p) ss1: Versatile as a character variable Use (q) ss1Auto: Character variable for conversion in ADP and ARP mode (r) ss1Cand: Character variable for displaying output characters (s) ss5[n]: Character variable for displaying conversion candidates, n is candidate number 0 to 499
(t) szBuf: Character variable for collecting converted character strings (for collecting individual information)
(u) szBuf3: Character variable for conversion auxiliary information (v) szBufCan: Character variable for output information at the end of conversion (w) szBufa: Character variable for conversion output of noun (item number 4) (x) szBufb: Noun + particle (Item No. 5) Conversion output character variable (y) szBufc: Verb (Item No. 8) Conversion output character variable (z) szBufz: Final conversion output character variable (conversion output unified information)
(α) szBufzcode[n]: Terminology information at the end of conversion, n is candidate number 0 to 499
(β) szSymbol: Character variable for program conversion output (γ) UserDic: Character variable for user dictionary conversion output (δ) yougotitle: Character variable for writing string substitution 1
(ε)yougo: Character variable for writing string substitution 2
(ζ) yougomode: Integer for user dictionary writing mode (B) Operation description and examples

The system in which the present invention can operate is the "Kana-Kanji conversion/KEARM conversion type Japanese input system" (exact match search type sequential conversion type Japanese input system of Non-Patent Document 2, hereinafter referred to as the "Kana-Kanji conversion/KEARM conversion type Japanese input system"). As shown in Figure 2, it is a system that incorporates the components (encircled by dotted lines) necessary to execute the KEARM standard conversion.

The Kana-Kanji Conversion/KEARM Conversion System is software that handles not only Japanese words but also foreign language words, and even in the explanation of this invention, characters and symbols that are prohibited in the patent application documents are used. Therefore, prohibited characters and symbols have been temporarily replaced with other characters and symbols. The characters and symbols on the screen are treated as images and there is no problem, so I used them as they were. The replaced characters and codes are as follows.
(1) Semicolons are used in the Kana-Kanji conversion/KEARM conversion system, but they have been replaced with commas.
(2) The Chinese word "??" corresponding to black was replaced with the Kanji "black".
(3) Replaced superscript characters in several French words with similar English alphabet characters.
(4) Replaced superscript letters in German words corresponding to English brochure with similar English alphabet letters.
(5) The half-width katakana "???" has been replaced with the full-width katakana "computer network."

The Kana-Kanji conversion/KEARM conversion system can process Kana-Kanji conversion and KEARM conversion simultaneously, but the purpose of the Japanese input system is to input kana and convert it into a sentence containing Kanji using Kana-Kanji conversion, so KEARM conversion is It has no choice but to become subordinate to kana-kanji conversion. Therefore, two constraints are placed on KEARM conversion. Constraint (1): ``Katakana words that have the same pronunciation as kanji characters are not converted to KEARM,'' and constraint (2): ``When the term attribute is the initial value, KEARM conversion becomes forward conversion.'' Constraint (2), forward conversion, means that the first candidate for conversion that results in a conversion even if KEARM is converted with kana or romaji input is not English or French, but Japanese katakana or romaji. Even if you perform KEARM conversion, the conversion result is not Japanese or French, but the same English as the input string, and furthermore, even if you input an English abbreviation and perform KEARM conversion, the conversion result remains as an English abbreviation. The reason why KEARM conversion is set to forward conversion in the initial state is to integrate KEARM conversion and kana-kanji conversion, and in the initial state, it is designed so that the conversion results of KEARM conversion and kana-kanji conversion are the same. As a countermeasure to these constraints, just by pressing the operation key from the successive conversion screen for kana-kanji conversion (constraint (1)), you can transition to the conversion candidate list screen for KEARM conversion, and the successive conversion screen for forward conversion (constraint (2)). The KEARM standard conversion of the present invention transitions to a conversion candidate list screen for translation conversion (bilingual conversion of KEARM conversion) just by pressing the operation key. Translation conversion means that words entered in Japanese kana or romaji are converted to words in English or the selected language, and English words entered in half-width alphanumeric characters are converted to Japanese katakana or words in the selected language. English abbreviations entered in half-width alphanumeric characters are converted into regular English or selected language character strings.

FIG. 1 is a screen showing the processing method for constraints (1) and (2) of KEARM conversion explained in paragraph number 0019. In the successive conversion screen (English) executed under the constraint (1) of the upper screen in Figure 1: "Do not KEARM convert katakana words that have the same reading as kanji characters", the display string "man" that indicates the input string is 80 Even if you try to convert KEARM, there are kanji with the same reading, such as ``man'' and ``man,'' so ``man'' will only be converted into kana-kanji and not KEARM. The kana-kanji conversion dictionary also lists katakana candidates, and the third candidate is ``man''. Words written in katakana include not only katakana, but also onomatopoeic words (thump and gatagata) and onomatopoeic words (kirakira and pika pika). Therefore, even if katakana is registered in a kana-kanji conversion dictionary, that katakana does not necessarily become katakana, which can be converted to KEARM. Therefore, even if candidates for KEARM conversion are not displayed, it is checked whether the katakana in question can be converted to KEARM.

Even if KEARM conversion of Katakana is not possible due to KEARM conversion restriction (1), the Kana-Kanji conversion/KEARM conversion system checks whether KEARM conversion can be performed in parallel with Kana-Kanji conversion, and if KEARM conversion is possible. For example, draw a line through "Man" like "Man" 81c in Figure 1. This means that KEARM conversion is possible, but priority is given to kana-kanji conversion, so KEARM conversion is not performed. This allows the user to know that the successive conversion screen is a screen on which KEARM fixed conversion can be executed. KEARM standard conversion can be executed by pressing the KEARM standard conversion key (Tab key is a physical key) from the successive conversion screen (English) of Constraint (1) in Figure 1. In this case, since the term attribute value of "man" is the initial value -1, a translation conversion (a bilingual conversion of KEARM conversion) is performed, and the conversion result becomes "man" 87 in English. On the other hand, if the term attribute value of "man" has been changed from the initial value of -1, the conversion result will be obtained by setting the attribute value in (c) Katakana attribute value setting table of the term attribute of the KEARM conversion dictionary in Figure 9. is determined, so in the case of constraint (1), the result of translation conversion is not necessarily English or the selected language.

In the lower screen of Figure 1, an example of a sentence rather than a word is given as an example of KEARM conversion constraint (2), ``When the term attribute is an initial value, KEARM conversion is a forward conversion.'' In the Kana-Kanji conversion/KEARM conversion system's KEARM conversion text conversion, only the conversion result that is the first conversion candidate among the conversion candidates for each phrase is displayed. The input character string "I read the catalog of desktop computer" 84 on the successive conversion screen is "3 types of catalog of desktop computer" when the term attribute value of all terms related to KEARM conversion is -1. ``I read ``85. In other words, the English words ``desktop'' and ``computer'' remain in English, and the Japanese kana ``katalog'' becomes the Japanese katakana word ``catalog,'' and there is no translation into other languages. A conversion in which the input string and the conversion result are of the same character type is called a forward conversion. Here, the English words "desktop" and "computer" and the Katakana word "catalog" are underlined. The underlined text indicates that KEARM conversion is actually being performed and the conversion results are being displayed.

The output language of the screen at the bottom of FIG. 1 for constraint (2) "When the term attribute is the initial value, the KEARM transformation is a forward transformation" is German. The term attribute values of the words to be converted, ``desktop'', ``computer'', and ``catalog'', are all initial values of -1, so if you run the KEARM standard conversion from the successive conversion screen (German), all KEARM conversions will be completed. It becomes a translation conversion. That is, since the output language is German, the selected language is German, English is converted to German, and katakana is also converted to German. On the other hand, other phrases that have been converted into kana-kanji are displayed as they are without KEARM standard conversion, and the conversion result on the conversion candidate list screen (German) is ``I read three types of Broschure on Desktop Computer.''87. Next, the operation of the KEARM fixed form conversion will be explained using a specific example.

Examples 1 to 8 are examples for KEARM conversion constraint (1) "Katakana words that have the same reading as kanji are not converted to KEARM", and Examples 9 to 10 are examples for KEARM conversion constraint (2) "Term attributes are This is an example of ``KEARM conversion becomes forward conversion when the initial value is set.'' First, in Example 1, KEARM conversion (1) of Katakana, which has the same pronunciation as Kanji, is performed using a single clause, single term, exact match search, and a successive conversion screen where the output language is English and the attribute value is the initial value -1. This is an operational example of executing KEARM fixed conversion. This will be explained with reference to FIGS. 4 and 11.

As described in paragraph number 0019, KEARM conversion has constraints (1) and (2). Conditions (1) and (2) are used to identify successive conversion screens executed under constraints (1) and (2), respectively. As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (English) in FIG. 11, which is the execution screen of the first embodiment, is a screen that satisfies condition (1). This screen is the same as the (1) successive conversion screen (English) in FIG. A check is performed on the katakana word ``man'', which is the third candidate, to confirm whether or not it can be converted into katakana, and as a result, KEARM conversion of the katakana word ``man'' is possible. ) has been crossed out as shown in "Man" 81c. You can now see that the (1) successive conversion screen (English) in Figure 11 is the screen on which you can execute the KEARM standard conversion.

Next, when you press the KEARM standard conversion key (logical key; the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b in Figure 4, the process advances to ``Setting variables required for KEARM standard conversion'' 70c. The variables AutoReconv, MpxHenkan and KEARMHenkan are set to 1. AutoReconv is a variable that requests KEARM standard conversion to the function ConvPhrase that constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33. MpxHenkan is a variable that corresponds to multiple clauses, but since KEARM fixed form conversion is based on processing multiple clauses, it will be 1 even for a single clause. KEARMHenkan works together with MpxHenkan to perform KEARM standard conversion. AutoLevel is an integer that indicates the starting clause number for executing KEARM fixed form conversion.You can specify the starting clause using the left and right arrow keys or the mouse, but if you do not specify it, it will start from the first clause, so the clause number nArray = 0 and AutoLevel = nArray+1, AutoLevel is 1, and KEARM standard conversion starts. nKEARMStartArray is an integer indicating the first clause number of the clause on which KEARM fixed form conversion was actually performed, and is set after KEARM fixed form conversion is performed. After performing the KEARM standard conversion, the process ends with the conversion candidate list screen for the first clause of the executed clause open, so at the end, AD conversion is performed in AD mode on the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in FIG. 4 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1. Enter "next character string detection" 16 at the OR gate indicated by two parallel lines from X1 at the bottom, and in the clause determined by AutoLevel (nArray = 0), clause information ArrayAuto[0][3] is 3. (English, English abbreviation or romaji) or 6 (katakana), it is a clause for which KEARM fixed form conversion can be performed. As explained in paragraph number 0129 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "man" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Let n1Auto = 2. Proceed to the next "Character type" 17, and since "Man" is a kana, enter OR input to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR input from X6 at the top and enter "Conversion section" 9 to go into.

In the table in FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, output language performs KEARM conversion in English. Since the term attribute value of the katakana word "man" is -1, the KEARM conversion becomes a translation conversion, and the first conversion candidate as the conversion result is English. The output order of conversion candidates is as specified in the first row of the "Output language is English" table in Figure 3 (a) where the input character string is kana, the first conversion candidate is English, the second candidate is Katakana, and the second candidate is Katakana. Since the English abbreviations/romanizations for the three candidates are not registered, the third candidate is the simplified Japanese translation, and the last is the term attribute, and the converted output is "man, man, human, husband, lover ///". Place the control character \0 at the end of each candidate for conversion output. Since the conversion is performed in step 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9.

It comes out from the ARP of the compound clause of the kana-kanji conversion in the "conversion section" 9 in FIG. Here, szBufa becomes the converted output szBufz of the main clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, the first conversion candidate "man" is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the first candidate for conversion is English, the second candidate is Katakana, the third candidate is simplified Japanese translation, and the last is It becomes a term attribute, and "man man, human being, husband, lover ///" becomes the conversion output. Place the control character \0 at the end of each candidate for conversion output. Since the conversion is performed in step 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0030, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. Display ss5[3] as "man man, human being, husband, lover ///" 86 on the conversion candidate list screen (English) in FIG. 11(2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The first conversion candidate "man" 86a becomes the selection candidate and the background color becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a simple clause, man of the first conversion candidate ss5[0] is selected in the "character string output selection" 35b and stored in the variable ss1Cand. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the selection candidate man of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, the selection candidate man is displayed on the screen as a conversion result with a thick underline like "man" 87 on the conversion candidate list screen (English) in FIG. 11(2). Next, an example of executing KEARM fixed form conversion from the successive conversion screen (French) shown in FIG. 12(1) of the second embodiment will be shown. Example 2 is a KEARM fixed form conversion from the same successive conversion screen as Example 1, but is an example in which the output language is French and the attribute value is 0 instead of the initial value -1. The operation will be explained with reference to FIGS. 4 and 12.

The (1) successive conversion screen (French) in Figure 12 of Example 2 is not related to the output language because it is a kana-kanji conversion even though the output language is different; Similar to the successive conversion screen, it is the same as the (1) successive conversion screen (English) in FIG. , the third candidate for conversion, the katakana ``man'', has been checked to see if it can be converted into katakana, and as a result, KEARM conversion of katakana is possible, so the (1) successive conversion screen in Figure 12 of this book is the same screen. (French) "Man" 81c is crossed out as shown in 81c. This shows that the (1) successive conversion screen (French) in Figure 12 is a screen on which the KEARM fixed conversion can be executed.

As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (French) in FIG. 12, which is the execution screen of the second embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in FIG. 4 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1 and enter "Next string detection" 16 with OR input from X1, and in the clause determined by AutoLevel (nArray = 0), clause information ArrayAuto If [0][3] is 3 (English, English abbreviation, or Roman alphabet) or 6 (Katakana), the clause is one in which KEARM fixed form conversion can be performed. As explained in paragraph number 0129 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "man" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Let n1Auto = 2. Proceed to the next "Character type" 17, and since "Man" is a kana, enter OR input to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR input from X6 at the top and enter "Conversion section" 9 to go into.

In FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, and output language is French. Perform KEARM conversion with . Unlike Example 1, since the term attribute value of the Katakana word "man" is 0, the output order of the conversion candidates is the conversion number 0, as specified by the attribute value 0 in the "Katakana term attribute value setting table" (c) in Figure 9. The 1st candidate is Katakana, the 2nd candidate is English, the 3rd candidate is English abbreviation/Romanization is not registered, so the 3rd candidate is French, the 4th candidate is a simplified Japanese translation, and the last is the term attribute "man man homme". “Man, Human, Husband, Lover //0” is the converted output. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9.

It comes out from the ARP of the compound clause of the kana-kanji conversion in the "conversion section" 9 in FIG. Here, szBufa becomes the converted output szBufz of the main clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, the first conversion candidate "man" is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the first candidate for conversion is Katakana, the second candidate is English, the third candidate is French, and the fourth candidate is simple, as in the ADP mode. In the Japanese translation, the last word attribute is the term attribute, and the converted output is "man homme man, human, husband, lover //0". Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0038, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. ss5[3] is displayed as "man homme man, human, husband, lover //0" 86 on the conversion candidate list screen (French) in FIG. 12 (2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The first conversion candidate "man" 86a becomes the selected candidate and the background color becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a single phrase, "man" of the first conversion candidate ss5[0] is selected in the "character string output selection" 35b and stored in the variable ss1Cand. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the selection candidate "man" of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, the selection candidate is displayed as a conversion result on the screen with a thick underline like "man" 87 on the conversion candidate list screen (French) in FIG. 12(2). Next, an example of executing KEARM fixed form conversion from the successive conversion screen (French) shown in FIG. 13(1) of the third embodiment will be shown. Embodiment 3 is an operation example in which the term attribute value of the katakana word "black" in the French version of the KEARM conversion dictionary is set to 5, so the search method is a single character search, and the beginning of the input string "black" is set to 5. This is a KEARM standard conversion that is executed from the successive conversion screen for kana-kanji conversion using one character "bu". The operation will be explained with reference to FIGS. 4 and 13.

The (1) successive conversion screen (French) in FIG. 13 of Example 3 is the same as the (3) successive conversion screen (French) in FIG. ~0181, and in paragraph number 0181, a check is performed on the katakana word "bu", which is the third candidate for conversion, to determine whether or not it can be converted into katakana. It is crossed out. The same screen is shown in "B" 81c of (1) Successive conversion screen (French) in FIG. 13 of this book. This shows that the (1) successive conversion screen (French) in Figure 13 is a screen on which the KEARM fixed conversion can be executed.

As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (French) in FIG. 13, which is the execution screen of the third embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1 and enter "Detect next character string" 16 with OR input, and in the clause determined by AutoLevel (nArray = 0), clause information ArrayAuto[0 ][3] is 3 (English, English abbreviation, or Roman alphabet) or 6 (Katakana), the clause is one in which KEARM fixed form conversion can be performed. As explained in paragraph number 0181 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "bu" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Set n1Auto = 1. Proceed to the next "Character Type" 17, and since "B" is a kana, input OR to enter "Kana Character Send" 18, exit from ARP and jump to the top with X6, enter OR from X6 at the top to "Conversion Section" 9 to go into.

In FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, and output language is French. Perform KEARM conversion with . Since the term attribute value of the katakana word "black" is 5, the output order of the conversion candidates is 1st as per the definition of the attribute value 5 in the "Katakana term attribute value setting table" (c) in Figure 9, as in Example 2. The candidate is English, the second candidate is Katakana, the third candidate is Roman letters, the fourth candidate is French, the fifth candidate is a simplified Japanese translation, and the last is the term attribute, ``black, kuro, kuroi, black, black, black.'' , the ominous //5” becomes the conversion output. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9.

It comes out from the ARP of the compound clause of the kana-kanji conversion in the "conversion section" 9 in FIG. Here, szBufa becomes the converted output szBufz of the body clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, the first conversion candidate "black" is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the first candidate for conversion is English, the second candidate is Katakana, the third candidate is Romaji, and the fourth candidate is Simple, as in the ADP mode. In the Japanese translation, the last term is the term attribute, and the converted output is "black kuro, kuroi, black, black, black, ominous //5". Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0046, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. Display ss5[3] as "black kuro, kuroi, black, black, black, ominous //5" 86 on the conversion candidate list screen (French) in FIG. 13(2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The first conversion candidate "black" 86a becomes the selected candidate and the background color becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a simple clause, black of the first conversion candidate ss5[0] is selected in the "character string output selection" 35b and stored in the variable ss1Cand. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the selection candidate black of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, the selection candidate black is displayed on the screen as a conversion result with a thick underline like "black" 87 on the conversion candidate list screen (English) in FIG. 13(2). Next, an example of executing the KEARM fixed form conversion from the sequential conversion screen (English) shown in FIG. 14 (1) of the fourth embodiment will be shown. Example 4, like Examples 1 to 3, converts a single phrase, but the output language is English and there are multiple terms to be converted. If there are multiple terms to be converted, the conversion candidate list screen becomes a simple conversion candidate display screen that displays multiple term candidates. The operation will be explained with reference to FIGS. 4 and 14.

The (1) successive conversion screen (English) in FIG. 14 of Example 4 is the same as the (1) successive conversion screen (English) in FIG. ~0133, and in paragraph number 0133, a check is performed on the katakana word "Ran", which is the second candidate for conversion, to check whether or not it can be converted into Katakana, and as a result, KEARM conversion of Katakana is possible, so "Ran" is crossed out. is being drawn. The same screen is shown in "Run" 81b of (1) Successive conversion screen (English) in FIG. 14 of this book. You can now see that the (1) successive conversion screen (English) in Figure 14 is the screen on which you can execute the KEARM standard conversion.

As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (English) in FIG. 14, which is the execution screen of the fourth embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1, enter "Next string detection" 16 with OR input from the bottom X1, and in the clause determined by AutoLevel (nArray = 0) , if the clause information ArrayAuto[0][3] is 3 (English, English abbreviation, or Roman alphabet) or 6 (Katakana), the clause is one in which KEARM fixed form conversion can be performed. As explained in paragraph number 0133 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "Run" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Let n1Auto = 2. Proceed to the next "Character type" 17, and since "Ran" is a kana, input OR to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR from X6 at the top to "Conversion part" 9 to go into.

In the table in FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, output language performs KEARM conversion in English. Since the output language is English and there are multiple terms to be converted, a simple conversion candidate display screen will appear showing conversion candidates for each term as "English + simple Japanese translation". run "run, leave, point" is the converted output. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9.

It comes out from the ARP of the compound clause of the kana-kanji conversion in the "conversion section" 9 in FIG. Here, szBufa becomes the converted output szBufz of the main clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, "local area network", which is the leading part of the first conversion candidate, is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the conversion output is "local area network, a computer network within one facility." Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item number 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0054, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. Display ss5[1] as ``local area network'' (run, leave, point) 86 on the conversion candidate simple display screen (English) in FIG. 14(2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The first conversion candidate becomes the selection candidate, and the background color of the first part "local area network" 86a of the selection candidate becomes light red.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of successive conversion is a simple clause and a simple display screen, store "local area network", which is the first part of the conversion first candidate ss5[0], which is the selection candidate in "Character string output selection" 35b, in the variable ss1Cand. do. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the "local area network" of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, convert the first part of the selected candidate on the screen with a bold underline like "local area network" 87 in Figure 14 (2) Simple conversion candidate display screen (English) Display it as a result.

If you execute the KEARM detailed conversion from the (2) conversion candidate simple display screen (English) in Figure 14, you can display the conversion candidate list screen (English) for "Ran" (which corresponds to English local area network in Katakana). KEARM detailed conversion refers to item (7) "KEARM detailed conversion of Japanese input system" of the multifunctional Japanese input system described in paragraph number 0025 of Non-Patent Document 2, and the details are in the document scheduled to be filed separately. I will explain. Next, an example of the operation of KEARM fixed form conversion in the case where the output language of the fifth embodiment is French will be shown.

The (1) successive conversion screen (French) in FIG. 15 of Example 5 is not related to the output language because it is a kana-kanji conversion, although the output language is different. ) It is the same as the successive conversion screen (English), and the operation explanation is explained in paragraph numbers 0131 to 0133 of Non-Patent Document 2. A conversion check is performed, and as a result, KEARM conversion of Katakana is possible, so "Ran" is crossed out. The same screen is shown in "Run" 81b of (1) Successive conversion screen (French) in FIG. 15 of this book. This shows that the (1) successive conversion screen (French) in FIG. 15 is a screen on which the KEARM fixed conversion can be executed.

As shown in "Condition for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (French) in FIG. 15, which is the execution screen of the fifth embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1, enter "Next string detection" 16 with OR input from the bottom X1, and in the clause determined by AutoLevel (nArray = 0) , if the clause information ArrayAuto[0][3] is 3 (English, English abbreviation, or Roman alphabet) or 6 (Katakana), the clause is one in which KEARM fixed form conversion can be performed. As explained in paragraph number 0133 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "Run" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Let n1Auto = 2. Proceed to the next "Character type" 17, and since "Ran" is a kana, input OR to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR from X6 at the top to "Conversion part" 9 to go into.

In the table in FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, output language performs the KEARM conversion in French. Since the output language is French and there are multiple terms to be converted, a simple conversion candidate display screen will appear showing conversion candidates for each term as "French + English", and the conversion output will be "reseau local, LAN local area network courir run". become. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It exits from the ARP of the compound clause of Kana-Kanji conversion in "Conversion section" 9, exits from Y based on the judgment of "Success?" 10, and enters "Output selection" 14a with OR input. Here, szBufa becomes the converted output szBufz of the body clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, "reseau local", which is the leading part of the first candidate for conversion, is stored in the output buffer ss12[0] of the first clause. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, "reseau local, LAN local area network courir run" is the conversion output, as in the ADP mode. Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item 4, the conversion output is saved in the character variable szBufa. When the conversion is completed, the process returns to FIG. 5 and exits the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0062, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. Display ss5[1] as "reseau local, LAN local area network courir run" 86 on the conversion candidate simple display screen (English) in FIG. 15 (2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The first conversion candidate becomes the selection candidate, and the background color of the first part of the selection candidate "reseau local" 86a becomes light red.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of successive conversion is a simple phrase and a simple display screen, select "reseau local", which is the first part of conversion first candidate ss5[0], which is a selection candidate, in "String output selection" 35b and set it to variable ss1Cand. Store. Next, the "output character display execution unit" 35c executes the function AddCharN and sends "reseau local" of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, the conversion result is displayed on the screen with a thick underline like "reseau local" 87 on the conversion candidate simple display screen (English) at the beginning of the selection candidate. Display as .

When KEARM detailed conversion is executed from the (2) conversion candidate simple display screen (French) in FIG. 15, a conversion candidate list screen (French) for "Ran" (corresponding to the French word reseau local in Katakana) can be displayed. Next, an example of the operation of KEARM fixed form conversion in the case where the output language of the sixth embodiment is multilingual will be shown.

(1) Sequential conversion screen (multilingual) in FIG. 16 of Example 6 has a different output language, but since it is a kana-kanji conversion, the output language is not relevant, and as in Examples 1 and 2, the screen shown in FIG. 29 of Non-Patent Document 2 It is the same as the (1) successive conversion screen (English), and the operation is explained in paragraphs 0127 to 0129 of Non-Patent Document 2. In paragraph 0129, the third conversion candidate, the katakana "man" KEARM conversion of Katakana is possible, so as shown in "Man" 81c on the same screen (1) Sequential conversion screen (multilingual) in Figure 16 of this book, is being drawn. This shows that the (1) successive conversion screen (multilingual) in Figure 16 is a screen on which KEARM fixed conversion can be executed.

As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (multilingual) in FIG. 16, which is the execution screen of the sixth embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1, enter "Next string detection" 16 with OR input from the bottom X1, and in the clause determined by AutoLevel (nArray = 0) , if the clause information ArrayAuto[0][3] is 3 (English, English abbreviation, or Roman alphabet) or 6 (Katakana), the clause is one in which KEARM fixed form conversion can be performed. As explained in paragraph number 0129 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "man" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Let n1Auto = 2. Proceed to the next "Character type" 17, and since "Man" is a kana, enter OR input to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR input from X6 at the top and enter "Conversion section" 9 to go into.

In FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. Perform KEARM conversion in the language. Since the output language is multilingual, it is not related to the term attribute value of the katakana word "man", and the conversion is performed as specified in the first row of the table (c) in Figure 3, where the output language is multilingual, where the input string is kana. The 1st candidate is English, the 2nd candidate is Katakana, the 3rd to 11th are words in 9 languages, and the 12th candidate is a simple Japanese translation, and the converted output is "man, man, human, husband, lover". become. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this time, only a search is performed in advance to check whether a plurality of terms are applicable. In the case of "man", there is only one term to be converted, so set the variable MultiSel = 0. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It exits from the ARP of the compound clause of Kana-Kanji conversion in "Conversion section" 9, exits from Y based on the judgment of "Success?" 10, and enters "Output selection" 14a with OR input. Here, szBufa becomes the converted output szBufz of the body clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, "man", which is the first conversion candidate, is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the first candidate for conversion is English, the second candidate is Katakana, and the third to 11th are words in nine languages, as in the ADP mode. The 12th candidate is the simple Japanese translation, and the converted output is ``man, man, human, husband, lover''. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0070, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. ss5[11] is displayed as "English. man Japanese. Man...translation. Man, human being, husband, lover" 86 on the conversion candidate list screen (multilingual) in FIG. 16 (2). In the case of multiple languages, put the abbreviation of each language at the beginning of each candidate. Also, since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The first conversion candidate becomes the selection candidate, and the background color of "English.man" 86a with the language abbreviation becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a simple clause, in the "character string output selection" 35b, man of ss5[0], which is the first conversion candidate, is stored in the variable ss1Cand as a selection candidate. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the selection candidate man of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, display the selected candidate man on the screen as a conversion result with a thick underline like "man" 87 on the conversion candidate list screen (multilingual) in Figure 16 (2). . Next, an example of the operation of KEARM standard conversion in the seventh embodiment when the output language is multilingual and there are multiple terms to be converted will be shown.

The (1) successive conversion screen (multilingual) in FIG. 17 of Embodiment 7 is not related to the output language because it is a kana-kanji conversion, although the output language is different. The operation is explained in paragraph numbers 0131 to 0133 of Non-Patent Document 2. In paragraph number 0133, a check is performed on whether or not the katakana word "Ran", which is the second candidate for conversion, can be converted into katakana language. As a result, ``Ran'' is crossed out because KEARM conversion of Katakana is possible. The same screen is shown in "Run" 81b of (1) Successive conversion screen (multilingual) in FIG. 17 of this book. This shows that the (1) successive conversion screen (multilingual) in Figure 17 is a screen on which KEARM fixed conversion can be executed.

As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (multilingual) in FIG. 17, which is the execution screen of the seventh embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1, enter "Next string detection" 16 with OR input from the bottom X1, and in the clause determined by AutoLevel (nArray = 0) , if the clause information ArrayAuto[0][3] is 3 (English, English abbreviation, or Roman alphabet) or 6 (Katakana), the clause is one that can be subjected to KEARM fixed form conversion. As explained in paragraph number 0133 of Non-Patent Document 2, ArrayAuto[0][3] = 6, so the character string "man" in the input buffer ss11[0] is stored in the character variable ss1Auto as a conversion character string, and the character length is Let n1Auto = 2. Proceed to the next "Character type" 17, and since "Man" is a kana, input OR to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR from X6 at the top to "Conversion part" 9 to go into.

In the table of FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, output language performs KEARM conversion in multiple languages. Since the output language is multilingual, it is not related to the term attribute value of the katakana word "Ran", and as specified in the first row of the "Output language is multilingual" table in Figure 3 (c) where the input character string is kana. , the first candidate for conversion is English, the second candidate is Katakana, the third to 11th are words in nine languages, and the 12th candidate is a simplified Japanese translation. Place the control character \0 at the end of each candidate for conversion output. At this time, only a search is performed in advance to check whether multiple terms are included. In the case of "Ran", we can see that there are multiple terms to be converted, so we set the variable MultiSel = 1. If there are multiple target terms, the conversion is done in alphabetical order, so the first KEARM conversion is a multilingual KEARM conversion targeting "LAN" and the conversion output is "local area network LAN... a computer network within one facility". become. Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out of the ARP of the complex clause of Kana-Kanji conversion in "Conversion section" 9, comes out from Y with the judgment of "Success?" 10, and enters "Output selection" 14a with OR input. Here, szBufa becomes the converted output szBufz of the body clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, the first conversion candidate "local area network" is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the conversion output is "local area network run...computer network within one facility" as in the ADP mode. Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0077, nKEARMStartArray = 0, so the phrase for which conversion candidates are displayed is the first phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. ss5[11] is displayed as "English. local area network Japanese. Ran... computer network within one facility" 86 on the conversion candidate list screen (multilingual) in FIG. 17 (2). In the case of multiple languages, put the abbreviation of each language at the beginning of each candidate. Also, since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. As described in paragraph number 0076, there are multiple terms to be converted and the variable MultiSel = 1, so "Tab(1)..." 91 is displayed at the left end of the bottom line of the screen. The first conversion candidate becomes the selection candidate, and the background color of "English. local area network" 86a with the language abbreviation becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a single phrase, the "local area network" of ss5[0], which is the first conversion candidate, is stored in the variable ss1Cand as a selection candidate in the "character string output selection" 35b. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the selection candidate "local area network" of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, select the selection candidate "local area network" on the screen with a thick underline like "local area network" 87 on the conversion candidate list screen (multilingual) in Figure 17 (2). to display the conversion result.

When you execute KEARM detailed conversion from (2) Conversion candidate list screen (multilingual) in Figure 17, the conversion candidate list screen (multilingual) for "Ran" (corresponding to English run, the second term in Katakana) ) can be displayed. Next, an example of the operation of KEARM fixed form conversion in the case where the successive conversion screen of the eighth embodiment is a complex phrase will be shown.

The (1) successive conversion screen (English) in FIG. 18 of Example 8 is the same as the (1) successive conversion screen (English) in FIG. 0135 to 0136, and checking whether the katakana word "Ran", which is the second candidate for conversion of the second clause, can be converted into katakana is explained in paragraph number 0133 of Non-Patent Document 2, which is another operation example. As a result, KEARM conversion of the Katakana word "Ran" is possible, but since "Ran" is not the first candidate for conversion of the second phrase, "column", which is the first candidate for conversion of the second phrase, is crossed out instead. is being drawn. This is as shown in "Literary column" 81 of (1) Successive conversion screen (English) in FIG. 18 of this book, which is the same diagram. You can now see that the (1) successive conversion screen (English) in Figure 18 is the screen on which you can execute the KEARM fixed conversion.

As shown in "Conditions for KEARM conversion target screen" 70a in FIG. 4, the (1) successive conversion screen (English) in FIG. 18, which is the execution screen of the eighth embodiment, is a screen that satisfies condition (1). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1, enter "Next string detection" 16 with OR input from the bottom X1, and in the clause determined by AutoLevel (nArray = 0) , check whether the clause information ArrayAuto[0][3] is 3 (English or English abbreviation/Romanization) or 6 (Katakana). Since there is no corresponding katakana word for the first clause "bungei", ArrayAuto[0][3] = 0 and we proceed to the second clause. As described in paragraph number 0133, the second clause is the conversion output of "column ran ran ran egg..." and the second conversion candidate "ran" in the conversion output is katakana, so it is difficult to determine whether or not it can be converted to katakana using KEARM conversion. A check is performed and it is confirmed that "Run" can be converted to KEARM, and a line is crossed out in "Column" which is the first candidate for conversion instead of "Run". As a result, ArrayAuto[1][3] = 6 and KEARM standard conversion is possible, so store the string "Ran" in input buffer ss11[1] as a conversion string in character variable ss1Auto, and set character length n1Auto = 2. do. Proceed to the next "Character type" 17, and since "Ran" is a kana, input OR to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR from X6 at the top and enter "Conversion part" 9 to go into.

In the table of FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. Convert. The Katakana word "Ran" in the KEARM conversion dictionary has two terms to be converted, so this is a simple display. Since the output language is English, the character string ``local area network'' (run, monkey, dot) of ``English + simple Japanese translation'' is the converted output. Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It exits from the ARP of the compound clause of Kana-Kanji conversion in "Conversion section" 9, exits from Y based on the judgment of "Success?" 10, and enters "Output selection" 14a with OR input. Here, szBufa becomes the converted output szBufz of the body clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, "local area network", which is the first part of the conversion first candidate, is stored in the output buffer ss12[1] of the second clause. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. In this embodiment, nKEARMStartArray = 1, and the AD conversion is the conversion of the second clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion section" 9, as in the ADP mode, there are two terms to be converted, so the table is simply displayed, and the output language is English, so "English + Simple Japanese" is displayed. The character string ``local area network'' (a computer network within one facility) is the converted output. Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item 4, the conversion output is saved in the character variable szBufa. When the conversion is completed, the process returns to FIG. 5 and exits the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. As described in paragraph number 0085, nKEARMStartArray = 1, so the phrase for which conversion candidates are displayed is the second phrase. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. Display ss5[1] as ``local area network (run, monkey, dot)'' 86 on the conversion candidate simple display screen (English) in Figure 18 (2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The background color of the leading portion "local area network" 86a of the first conversion candidate, which is a selection candidate, becomes light red.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a compound clause, the string output in the "character string output selection" 35b becomes a "literary local area network" that is a combination of output buffers ss12[0] to ss12[1], and is stored in the variable ss1Cand. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the character string output "literary local area network" to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, convert the character string output of ss12[0] to ss12[1] on the screen as shown in "Literary local area network" 87 on the conversion candidate simple display screen in Figure 18 (2). Display it as a result. As for the display attribute, "Literature" has been converted and is underlined with a solid thin line, and "local area network" is the notable clause and is underlined with a solid thick line. Next, as examples 9 and 10, we will show an example of executing the KEARM regular conversion in the case of (2) "When the term attribute is an initial value, the KEARM conversion becomes a forward conversion", which is another constraint of the KEARM regular conversion. show. Embodiment 9 shows an example of the operation of multiple KEARM fixed form conversions when the input character string and output language are changed in a single clause.

The successive conversion screen (French) in FIG. 19 (1) of Example 9 is the same screen as the successive conversion screen (French) in FIG. It's explained. This screen is a screen for successive conversion when "Black" is input in kana, the output language is French, and the term attribute value of Katakana "Black" is the initial value -1. The screen obtained by executing KEARM standard conversion from this screen is the conversion candidate list screen (French) shown in FIG. 19 (1a). The katakana word "black" 85a, which is the first conversion candidate on the successive conversion screen (French) in FIG. 19(1), is the French word "noir" 86a, which is the first conversion candidate on the conversion candidate list screen (French) in FIG. 19(1a). At the same time, the conversion result also changes to "noir" 87. The operation will be explained with reference to FIG.

The condition of "KEARM standard conversion target screen condition" 70a in Figure 4 is the condition (2) term attribute that corresponds to the constraint (2) in Figure 1: "KEARM conversion is a forward conversion when the term attribute is the initial value" is the initial value successive conversion screen. Next, when you press the KEARM standard conversion key (logical key; the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b in Figure 4, the process advances to ``Setting variables required for KEARM standard conversion'' 70c. The variables AutoReconv, MpxHenkan and KEARMHenkan are set to 1. Since the integer AutoLevel = nArray+1 and nArray = 0, AutoLevel is 1 and the KEARM fixed conversion operation starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution unit" 4 to 33 will be explained with reference to FIGS. 5 and 7.

The variable AutoReconv starts the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in ARP mode, which operates in parallel with ADP mode. In ARP mode in Figure 5, from "Start conversion", jump to the bottom with X1, enter OR input from X1 on the bottom to enter "Detect next string" 16, and select the clause determined by AutoLevel (nArray = 0 ), check whether the clause information ArrayAuto[0][3] is 3 (English or English abbreviation/Romanization) or 1 (Katakana). As described in paragraph number 0086 of Non-Patent Document 2, ArrayAuto[0][3] = 1, so store the character string "black" in the input buffer ss11[0] in the conversion character variable ss1Auto, and set the character length n1Auto = 4. shall be. Proceed to the next "Character type" 17, and since "Black" is a kana, enter OR input to enter "Kana character feed" 18, exit from ARP and jump to the top with X6, enter OR from X6 at the top and enter "Conversion section" 9 to go into.

In the table of FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. 5, line number 1, operation mode ARP, item number 4, conversion character string is Katakana, no ending, dictionary is KEARM conversion dictionary, output language performs the KEARM conversion in French. Since the initial value of the term attribute value of katakana "black" is -1, KEARM conversion is a translation conversion, and the output order of conversion candidates is the input character string in the "Output language is a language other than English" table in Figure 3 (b). As specified in the first line where is a kana, the first candidate for conversion is French, the second candidate is Katakana, the third candidate is English, the fourth candidate is Roman letters, the fifth candidate is a simplified Japanese translation, and the last is the term attribute. The converted output is ``noir black, kuro, kuroi, man, human, husband, lover ///''. Place the control character \0 at the end of each candidate for conversion output. Since the conversion is performed in step 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. Exit "conversion section" 9.

It comes out from the ARP of the compound clause of the kana-kanji conversion in the "conversion section" 9 in FIG. Here, szBufa becomes the converted output szBufz of the body clause. Next, "Kana?" 12 is entered, but this is not applicable in ARP mode, and then "End?" 11 is entered. At the same time, the first conversion candidate "noir" is stored in the output buffer ss12[0]. "End?" Go to X5 from 11 Y. The operating mode also changes from ADP mode to AD mode. ARP mode is maintained until the end of conversion.

Next, exit from Y in ``End?'' 11 in Figure 5, jump to the top with X5, and enter AD conversion in ``conversion section'' 9 with OR input from X5 at the top. Since this embodiment converts a single clause, nKEARMStartArray = 0, and AD conversion is a conversion of the first clause. In the table of FIG. 7, which is a detailed explanatory diagram of the "conversion unit" 9, the first candidate for conversion is French, the second candidate is Katakana, the third candidate is English, and the fourth candidate is Roman. , the fifth candidate is the simple Japanese translation, and the last is the term attribute, and the converted output is "noir black, kuro, kuroi, man, human, husband, lover ///". Place the control character \0 at the end of each candidate for conversion output. As in ADP mode, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. It comes out from AD of AD conversion in "conversion section" 9 and enters "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, the result of successive conversion is a single clause, so the conversion information szBufz is saved as is as output information szBufCan, and the process ends with "conversion successful". Next, the output information szBufCan enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, which is an interface section with the application program.

It enters the "conversion candidate display section/character output section" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first section "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. Since the screen for successive conversion is a simple clause, nKEARMStartArray = 0, and the clause for which conversion candidates are displayed is the first clause. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. Send "request" 34c to the computer, use "function etc. to draw conversion candidate list display" 48 to determine the size and position of the application program screen "conversion candidate list display" 50, and display conversion candidate display information ss5[0]~ on the screen. ss5[5] is displayed as "noir black, kuro, kuroi, man, human, husband, lover ///" 86 on the conversion candidate list screen (English) in FIG. 19 (1a). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. The background color of the first conversion candidate "noir" 86a, which is a selection candidate, becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of the successive conversion is a simple clause, the noir of ss5[0], which is the first conversion candidate, is stored in the variable ss1Cand as a selection candidate in the "character string output selection" 35b. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the selection candidate noir of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, the selection candidate noir is displayed on the screen as a conversion result with a thick underline as "noir" 87 on the conversion candidate list display screen in FIG. 19(1a). The following operation examples will be explained in the same way, so what happens if you execute the KEARM standard conversion from the KEARM conversion successive conversion screen where the term attribute value of the KEARM conversion dictionary corresponding to the input string is the initial value -1. I will mainly explain what the results will be.

The successive conversion screen (Chinese) in FIG. 19(2) of Example 9 is the same screen as the successive conversion screen (Chinese) in FIG. 25(1) of Non-Patent Document 2, and is The operation is explained in 0105. This screen is a screen for successive conversion when "black" is input in half-width alphanumeric characters, the output language is Chinese, and the term attribute value of English "black" is the initial value -1. The screen obtained by executing the KEARM standard conversion from this screen is the conversion candidate list screen (Chinese) shown in FIG. 19 (2a). The English word "black" 85a, which is the first conversion candidate on the successive conversion screen (Chinese) in Figure 19 (2), is the Chinese word "black" 85a, which is the first conversion candidate in the conversion candidate list screen (Chinese) in Figure 19 (2a). ” 86a, and at the same time, the conversion result also changes to “black” 87.

The successive conversion screen (French) in FIG. 19(3) of Example 9 is the same screen as the successive conversion screen (French) in FIG. 27(1) of Non-Patent Document 2, and is The operation is explained. This screen is a screen for successive conversion when "ALS" is input in half-width alphanumeric characters, the output language is French, and the term attribute value of the English abbreviation "ALS" is the initial value -1. The screen obtained by executing KEARM standard conversion from this screen is the conversion candidate list screen (French) shown in FIG. 19 (3a). The English abbreviation "ALS" 85a, which is the first candidate for conversion on the sequential conversion screen (French) in FIG. "86a, and at the same time the conversion result also changes to "sclerose laterale amyotrophique"87.

The successive conversion screen (Spanish) in FIG. 19(4) of Example 9 is the same screen as the successive conversion screen (Spanish) in FIG. 28(1) of Non-Patent Document 2, and is The operation is explained in 0124. This screen is a screen for successive conversion when "kuro" is input in half-width alphanumeric characters, the output language is Spanish, and the term attribute value of the Roman alphabet "kuro" is -1, which is the initial value. The screen obtained by executing the KEARM standard conversion from this screen is the conversion candidate list screen (Spanish) shown in FIG. 19 (4a). The Roman character "kuro" 85a, which is the first candidate for conversion on the successive conversion screen (Spanish) in Figure 19 (4), is the first candidate for conversion on the conversion candidate list screen (Spanish), which is the first candidate for conversion in Figure 19 (4a) (Spanish), "negro". ” 86a, and at the same time the conversion result also changes to “negro” 87.

The successive conversion screen (multilingual) shown in FIG. 19 (5) of Example 9 is the same screen as the successive conversion screen (multilingual) shown in FIG. The operation is explained in 0139. This screen is a screen for successive conversion when the kana ``telebi'' is input, the output language is multilingual, and the term attribute value of ``television'' in katakana is the initial value -1. The screen obtained by executing KEARM standard conversion from this screen is the conversion candidate list screen (multilingual) shown in FIG. 19 (5a). "Japanese TV" 85a, which is the first candidate for conversion on the sequential conversion screen (multilingual) in Figure 19 (5), which is the Katakana word "TV" with a language-specific abbreviation, is shown in Figure 19 (5a) Conversion candidate list screen (multilingual). ) is changed to "English.television" 86a, which is the first candidate for conversion, English "television", with language-specific abbreviations added. On the other hand, the conversion result changes to "television" 87 without the language-specific abbreviation. Next, as Example 10, an example of KEARM fixed form conversion is shown which is executed from the successive conversion screen of KEARM conversion of a sentence including words in which the attribute values of all terms to be KEARM converted are initial value -1.

Similarly to the ninth embodiment, the tenth embodiment is also a screen of condition (2) of the "conditions for the KEARM standard conversion target screen" 70a in FIG. The successive conversion screen (German) shown in FIG. 20(1) is the same screen as the successive conversion screen (German) shown in FIG. This screen is a screen for successive conversion of a compound clause containing two English words and a katakana word whose term attribute is the initial value of -1. From this screen, press the KEARM standard conversion key to perform KEARM standard conversion, translate as shown in Figure 20 (2) Conversion candidate list screen (German), and show an example of converting two English words and Katakana to German. .

As shown in "Conditions for KEARM Conversion Target Screen" 70a in FIG. 4, the (1) successive conversion screen (German) in FIG. 20, which is the execution screen of Example 10, is a screen that satisfies condition (2). Next, when you press the KEARM standard conversion key (logical key, the physical key is the Tab key) in ``KEARM standard conversion key operation'' 70b, the process advances to ``Setting variables required for KEARM standard conversion'' 70c, and the variable AutoReconv, MpxHenkan and KEARMHenkan are set to 1. With the integer AutoLevel = nArray+1, the start clause for KEARM regular conversion is nArray = 0, so AutoLevel is 1 and the KEARM regular conversion starts. Finally, perform AD conversion in AD mode with the clause numbered in nKEARMStartArray. First, the function ConvPhrase, which constitutes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33, is started in ARP mode. The operations of the "kana-kanji conversion/KEARM conversion execution unit" 4 to 33 will be explained with reference to FIGS. 5 to 8.

The variable AutoReconv causes the "kana-kanji conversion/KEARM conversion execution units" 4 to 33 in FIG. 4 to start operating in ARP mode, which is a parallel operation with ADP mode. From "Start conversion" in ARP mode in Figure 5, jump to the bottom with X1, enter "Next string detection" 16 with OR input from the bottom X1, and in the clause determined by AutoLevel (nArray = 0) , check whether the clause information ArrayAuto[0][3] is 3 (English, English abbreviation or Roman alphabet) or 1 (Katakana). As stated in paragraph number 0199 of Non-Patent Document 2, ArrayAuto[0][3] is 3, so the character string "desktop" in the input buffer ss11[0] of the first clause is stored in the conversion character variable ss1Auto, and the character string Let length n1Auto = 7. Proceed to the next "character type" 17, and since "desktop" is English, it starts from alphanumeric symbols and enters the judgment of "full-width/half-width" 17a or 17b, and starts from half-width. This will be explained below with reference to FIG. Next, the process enters ``English combination information acquisition'' 29, where no information is obtained, and the process enters ``English word sending'' 30 by OR input. It exits from the ARP side as it is, jumps to the top via X7, and enters the KEARM/ANS conversion from ARP in "conversion section" 9 by OR input from X7 at the top.

In the table in Figure 8, which is a detailed diagram of the "conversion unit" 9 in Figure 6, line number 1, operation mode ARP, item number 4, conversion character string is half-width alphanumeric characters, no ending, KEARM conversion using KEARM conversion dictionary. I do. Since the term attribute value of "computer" registered in the KEARM conversion dictionary is the initial value of -1, KEARM conversion is a translation conversion, and the output order of conversion candidates is as shown in Figure 3 (b) "The output language is a language other than English". This is the second row in which the input character string in the table is in English. Therefore, the first candidate for KEARM conversion of "desktop" is German, the second candidate is English, and the third candidate is Katakana to obtain the conversion output "Desktop desktop...". Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 4, save the conversion output to szBufa. This is the end, and returning to FIG. 6, the process exits from the ARP of the compound clause of the KEARM/ANS conversion in the "conversion unit" 9 and enters the "output selection" 14a with OR input. Here, szBufa becomes the converted output szBufz of the main clause. Next, the judgment of "Kana?" 12 is entered, but this is not applicable in ARP mode, and then the judgment of "End?" 11 is entered. At the same time, the first conversion candidate "Desktop" is saved in the output buffer ss12[0] of the first clause, exits from N of "End?", and enters "prevCode judgment" 15. The clause that underwent KEARM fixed form conversion becomes prevCode = 126.

Next, enter "Next character string detection" 16 by inputting OR. Next, in the second clause nArray = 1, check whether ArrayAuto[1][3] is 3 or 1. Since the next clause is a No-break space, ArrayAuto[1][3] = 0, and we proceed to the next third clause, checking whether ArrayAuto[2][3] is 3 or 1 with nArray = 2. As stated in paragraph number 0201 of Non-Patent Document 2, ArrayAuto[2][3] is 3, so "computer" of the input buffer ss11[2] of the third clause is stored in ss1Auto, and the character length n1Auto = 9. do. Next, the process enters the judgment of ``character type'' 17, exits from alphanumeric symbols, enters the judgment of ``full-width/half-width'' 17b, exits from half-width, and enters ``obtain English combination information'' 29. No information is obtained here, so enter "English word sending" 30 with OR input, exit from ARP and jump to X7 at the top via X7, and enter OR from X7 at the top from ARP to KEARM /Enter ANS conversion.

In the table of FIG. 8, which is a detailed diagram of the "conversion unit" 9 in FIG. Perform the conversion. Since the initial value of the term attribute value of "computer" registered in the KEARM conversion dictionary is -1, KEARM conversion is a translation conversion, and the output order of conversion candidates is as shown in Figure 3 (b) "The output language is a language other than English". This is the second row in which the input character string in the table is in English. Therefore, the first candidate for KEARM conversion of "computer" is German, the second candidate is English, and the third candidate is Katakana, and the conversion output is "Computer's computer, computer, computer...". Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item number 5, the conversion output is saved in the character variable szBufb. At this point, the conversion is completed and the process returns to Figure 6. Exit from the ARP of the complex clause of KEARM/ANS conversion in "conversion section" 9 and enter "output selection" 14a with OR input, where szBufb becomes the converted output szBufz of the main clause. . Next, the judgment of "Kana?" 12 is entered, but this is not applicable in ARP mode, and then the judgment of "End?" 11 is entered. At the same time, "Computer's" is saved in the output buffer ss12[3] of the third clause, and since it is not the end, it exits from N and enters "prevCode judgment" 15. If KEARM fixed form conversion is executed, prevCode = 126.

Next, enter "Next character string detection" 16 by inputting OR. Since ArrayAuto[nArray][3] is not 3 or 1 in both the fourth clause nArray = 3 and the fifth clause nArray = 4, move to the sixth clause nArray = 5 and read in paragraph number 0216 of Non-Patent Document 2. As described, ArrayAuto[5][3] = 1, so store the character string "Catalog wo" from the input buffer ss11[5] of the 6th clause in the character variable ss1Auto, and set the character length n1Auto = 5. Next, we move on to the determination of “character type” 17. Since the half-width alphanumeric character string processing has been completed, return to FIG. 5, which is an explanatory diagram of kana input support. Exit from kana in "Character type" 17, input OR input to enter "Kana character sending" 18, exit from ARP as it is, jump to the top via X6, enter OR input from X6 at the top, from ARP to Kana-kanji in "Conversion part" 9 Enter conversion.

In the table of FIG. 7, which is a detailed diagram of the "conversion unit" 9 in FIG. conduct. As in Sections 1 and 3, the attribute value of the Katakana word "Catalog" registered in the KEARM conversion dictionary is -1, so KEARM conversion is a translation conversion, and as shown in (b) in Figure 3, the output language is English. The input character string in the "Other Languages" table is a kana.The first row of conversion candidates is German, the second is Katakana, and the third is English. ” is the converted output. Place the control character \0 at the end of each candidate for conversion output. Since the conversion was performed in step 5, save the conversion output to szBufb. At this point, the conversion ends, and the process returns to FIG. 5 and exits the "conversion unit" 9. It exits from the ARP of the compound clause for kana-kanji conversion in the "conversion section" 9, enters the judgment "Success?" 10, exits from Y and enters the "output selection" 14a with OR input. Here, szBufb becomes conversion information szBufz. Next, "Kana?" 18 is judged, but it is not applicable in ARP mode, and "End?" 11 Y to X5 is entered. At the same time, the first conversion candidate "Broschure" is stored in the output buffer ss12[5] of the sixth clause. It is checked whether ArrayAuto[6][3] of the final seventh clause is 3 or 1, and since it is not a clause to be converted to the KEARM standard format, the process ends here.

Next, it exits from Y in "End?" 11 in FIG. 5, jumps to the top via X5, and enters AD to AD conversion in "conversion section" 9 by OR input from X5 at the top. The first clause that undergoes KEARM fixed form conversion becomes nKEARMStartArray. In this embodiment, since nKEARMStartArray = 0 and it is the first clause, AD conversion is performed using "desktop" of ss11[0] as the conversion character string. Since it is a half-width alphanumeric input, perform KEARM conversion for row number 1, operation mode AD, and item number 4 in the table in Figure 8, which is a detailed diagram of the conversion part of "conversion part" 9, and perform KEARM conversion in the same way as conversion in ADP mode. is a translation conversion, and the input character string of "Output language is a language other than English" in Figure 3 (b) is specified in the second line as English, the first candidate for conversion is German, the second candidate is English, and the third The candidate is katakana, and the converted output is ``Desktop desktop ///''. Place the control character \0 at the end of each candidate for conversion output. Since this is the conversion in item 4, the conversion output is saved in the character variable szBufa. At this point, the conversion is completed and the process returns to FIG. 5 to exit the "conversion section" 9. Exit from AD of AD conversion and enter "output selection" 14b with OR input. Here, szBufa becomes conversion information szBufz. In the next "single/multiple output selection" 21, since the conversion is in AD mode, the output information szBufCan of the first clause becomes "Desktop desktop ///" and "conversion successful" is output.

Next, the output information szBufCan enters the "conversion candidate display section/character output" 34 to 35 in FIG. 4, and enters the "conversion candidate display execution section" 34a of the first category "conversion candidate display section" 34. The "conversion candidate display execution unit" 34a executes the function ConvCandidate and sends output information to a computer-managed conversion candidate structure. Based on the conversion candidate display information ss5[0] to ss5[n] (n is the number of candidates - 1) obtained by the “conversion candidate display execution unit” 34a, the “conversion candidate display unit” 34 displays a “conversion candidate list display”. After determining the size and position of the application program screen ``Conversion candidate list display'' 50 by sending the request 34c to the computer and using the functions 48 ``Function to draw conversion candidate list display, etc.'', the conversion candidate display information is displayed on the screen. Display ss5[0] to ss5[4] as "Desktop ///" 86 on the conversion candidate list screen (German) in Figure 20 (2). Since there is a control character \0 at the end of the conversion candidate, each conversion candidate is displayed on a new line. "Desktop" 86a becomes the first candidate for conversion and the background color becomes light blue.

Next, the "character string output selection" 35b of the second section "character output section" 35 in FIG. 4 is entered. Since the result of successive conversion is a compound clause, the string output in ``Select string output'' 35b becomes ``I read three types of Desktop Computer brochures'' from ss12[0] to ss12[6] and is stored in the variable ss1Cand. Next, the "output character display execution unit" 35c executes the function AddCharN and sends the character string output of ss1Cand to the computer-managed editing structure. Based on the above results, the ``character output unit'' 35 sends an ``output character display request'' 35d to the computer, and uses the various functions of the ``functions, etc. to draw input/output character display'' 47 to display the ``input/output character display'' screen of the application program. After determining the size and position of 49, output the character strings ss12[0] to ss12[6] on the relevant screen and select "3 types of Desktop Computer Broschure" on the conversion candidate list screen (German) in Figure 20 (2). The conversion result is displayed as "I read" 87. The display attribute of "Desktop" is "noted phrase" with a solid thick line and underline, and the display attributes of other phrases are converted attributes with solid thin line and underline.

1 to 62 are configuration numbers 1 to 3. Input sections 4 to 33 Kana-kanji conversion/KEARM conversion execution sections 34 to 35 Conversion candidate display section/character output section 34 Conversion candidate display section 34a Conversion candidate display execution section 34b Up and down arrow key operations ( Conversion candidate selection)
34c Conversion candidate list display request 35 Character output section 35a Not used in the present invention
35b Character string output selection 35c Output character display execution unit 35d Output character display request 36 Kana-Kanji conversion dictionary 37 User dictionary 38 KEARM conversion dictionary 39 Output language selection switch 40 KEARM conversion audio output unit 41 to 46 Not used in the present invention 47 Functions etc. that draw input/output character display 48 Functions etc. draw conversion candidate list display 49 Input/output character display 50 Conversion candidate list display 51 to 54 Not used in the present invention 55 KEARM standard conversion execution unit 56 KEARM priority conversion execution unit (this invention (not used)
57-62 Not used in the present invention 63-69 Empty numbers 70-79 Numbers for operation explanation/movement explanation 70a Conditions for screens to be converted to KEARM standard format 70b KEARM standard conversion key operations 70c Setting of variables required for KEARM standard conversion 71-79 Vacant numbers 80-91 Screen explanation numbers 80-83 Kana-kanji conversion screen number 80 Display string 81 Conversion candidate list (successive conversion screen)
81b Second conversion candidate 81c Third conversion candidate 82-83 Not used in the present invention 84-91 KEARM conversion screen number 84 Display character string 85 List of conversion candidates (successive conversion screen)
85a First conversion candidate 85b Second conversion candidate 85c Third conversion candidate 86 List of conversion candidates (conversion candidate list screen)
86a Selection candidate (conversion first candidate)
87 Conversion result 88 Simple Japanese translation 89 Term attribute 90 Pronunciation language abbreviation display (not used in this invention)
91 Display of multiple conversion target terms

Claims (1)

KEARM standard conversion is used in the "Kana-Kanji conversion/KEARM conversion type Japanese input system" (exact match search type sequential conversion type Japanese input system of patent application 2022-017542) that inputs Japanese into application programs running on a computer. In a Japanese input system that incorporates the "KEARM standard conversion execution unit" to add functionality, and also adds the "KEARM standard conversion key" which is a logical key necessary for operation,
KEARM conversion is ``Katakana (K) by kana input, English (E) by half-width alphanumeric input, English abbreviation (A) or Romaji (R), 3 categories (K, E, A or R), 4 inputs. It is a conversion method that can perform multilingual processing, with a unique name taken from the acronym "Conversion that can mutually convert (K, E, A, and R) and can also output multilingual (M)".
In order to give priority to kana-kanji conversion in KEARM conversion, there are two constraints: (1) ``Katakana words that have the same reading as kanji are not converted to KEARM'' and constraint (2) ``When the term attribute is the initial value, KEARM conversion is performed in forward order. (Conversion where the input character string and conversion result are the same character type)" is provided.
In the present invention, the "KEARM standard conversion" key can be pressed while the successive conversion screen obtained by inputting under the above-mentioned constraints (1) and (2) is displayed on the screen of the application program. In this method, the "KEARM standard conversion execution unit" mainly executes the following process for segments that have already undergone KEARM conversion or clauses that can be converted to KEARM, and then transitions from the sequential conversion screen to the conversion candidate list screen or conversion candidate simple display screen. And,
For constraint (1), instead of kana-kanji conversion, Katakana KEARM conversion (regular KEARM conversion performed according to the term attributes of the KEARM conversion dictionary in Figure 9) is executed for each clause, and In the case of a screen, the conversion candidate list screen or conversion candidate simple display screen for KEARM conversion is displayed, and in the case of a compound clause screen, the conversion candidate list screen or conversion candidate simple display screen for the first clause that has been subjected to KEARM conversion is displayed. , for other phrases, the first conversion candidate for each phrase is displayed as the conversion result,
For constraint (2), a new KEARM conversion translation conversion (KEARM conversion between two languages) is performed for each clause, where Japanese words are replaced with English or words in the selected language, and English words are replaced with words in English or the selected language. , replace words in Japanese or the selected language, and replace English abbreviations with strings in English or the selected language), and in the case of a single phrase screen, display the KEARM conversion conversion candidate list screen or conversion candidate simple display screen. In the case of a compound clause screen, a conversion candidate list screen or a conversion candidate simple display screen for the first clause for which KEARM conversion has been newly executed will be displayed, and for other clauses, the first conversion candidate for each clause will be converted. displayed as a result,
Method.