JP5079259B2 - Language input system, processing method thereof, recording medium, and program - Google Patents

Description

  The present invention relates to a language input system, a processing method, a recording medium, and a program capable of displaying one or more notations for an input reading in a notation list and selecting and confirming one notation from the displayed notations.

  2. Description of the Related Art Conventionally, there is a language input system that operates a Japanese input program that converts an input language, for example, Japanese reading into desired Japanese notation (Hiragana, Katakana, Kanji, symbols, etc.). Examples of Japanese input programs include the applicant's MS-IME (Input Method Editor) (trademark), Justsystem's ATOK (trademark), and others (see, for example, Patent Document 1).

  For example, MS-IME operates on a personal computer (PC) that operates in an OS (operating system) environment such as Windows (registered trademark). MS-IME refers to dictionary data (system dictionary) that MS-IME has in advance or dictionary data (user dictionary) defined by a user, and acquires one or more expressions for input readings from the dictionary. . MS-IME displays the notation as a notation list on the display screen of the PC, and converts the reading into one notation selected and fixed by the user.

  MS-IME is a program for inputting Japanese characters. MS-IME uses a lexicon database (DB) and a Japanese language model (LM) to generate appropriate ideograms (notation) from phonetic characters (reading). Lexicon is a glossary and a so-called dictionary of MS-IME. The LM is a grammar DB that defines rules for performing statistical language processing. The MS-IME extracts one or more notations corresponding to the input reading from the lexicon DB, and determines the optimum one notation by language processing using LM therefrom.

JP 2002-123510 A

  However, for example, if you want to obtain the notation "Kagoshima" corresponding to the reading "Kagoshima", but the language input system dictionary (lexicon) does not have "Kagoshima" data, the notation "Kagoshima" Is not displayed. In this case, the user needs to try to obtain the notation “Kagoshima” corresponding to the reading “Shikakoshima” instead. As described above, when the conventional language input system cannot obtain the desired notation for the input reading from the dictionary even when referring to the dictionary in advance, the user can obtain the desired notation by using the next best solution. There are times when it is necessary to take.

  Also, for example, when it is desired to obtain a notation corresponding to the reading “Adachi”, if the language input system dictionary has data such as “Adachi”, “Adachi”, “Adachi”, etc., these plural notations Is displayed. In this case, prior to inputting the reading, the user needs to consider which information is the desired notation corresponding to the reading “Adachi” with reference to other information. As described above, the conventional language input system may not be able to efficiently obtain the desired notation for the input reading from the dictionary if there is a homonym even if it refers to the dictionary that it has in advance.

  In the conventional language input system as described above, since the vocabulary of Japanese handled in the world is varied, the default DB of the Japanese input program does not cover all Japanese. Therefore, the Japanese input program is required not only to correspond to a predetermined database but also to a user related DB that supports various words handled by the world.

  The present invention has been made in view of such problems, and an object of the present invention is to provide a language input system, a processing method thereof, a recording medium, and a program that improve the ease of handling user-related data. It is in.

  In order to achieve such an object, the language input system (FIG. 1) of the present invention is a language input system that converts a reading into a desired notation, and includes first contact information ( 130) and information management means (101, 124) for managing second contact information (131) different from the first contact information, and one or more of the input readings in a predetermined language A client system (100) having language input means (101, 114) for displaying a notation and selecting one notation from the displayed notations is connected to the client system, Shared contact information that is further connectable with one or more other client systems and is accessed and shared by the client system and the one or more other clients (182), and the information management means periodically acquires the shared contact information from the server system, and uses the acquired shared contact information as the second contact information. The information is updated, and the language input means acquires the first contact information and the second contact information from the information management means, and the acquired first contact information and the second contact information. A dictionary creating means (FIG. 6) for creating dictionary data (203a, 203b) from the contact information, and referring to the dictionary data created by the dictionary creating means, converting the input reading into a notation and displaying the notation The converted display means (S812), and when the display is performed by the conversion display means, the input and the input read and converted included in the first contact information and the second contact information Get serial corresponding to the additional information (307) from said information management means (S813), and having an information display means for displaying together with the corresponding converted the acquired additional information notation (S814).

  In order to achieve the above object, a processing method of a language input system according to the present invention is a processing method of a language input system that converts a reading into a desired notation, and the language input system relates to a communication partner. An information management means for managing the first contact information and the second contact information different from the first contact information, and one or more notations for the input reading in a predetermined language are displayed. A client system having language input means for selecting one notation from the displayed notations, and connected to the client system and further connectable to one or a plurality of other client systems And a server system having shared contact information accessed and shared by the client system and the one or more other clients. In the processing method, the information management means periodically acquires the shared contact information from the server system, and updates the second contact information with the acquired shared contact information. The language input means obtains the first contact information and the second contact information from the information management means, and a dictionary from the obtained first contact information and the second contact information. A dictionary creating step for creating data, a conversion display step for referring to the dictionary data created in the dictionary creating step, converting the input reading into a notation and displaying the notation, and the language When the input means displays in the conversion display step, the inputted reading and the converted table included in the first contact information and the second contact information are displayed. Additional information corresponding to the obtained from the information management means, characterized in that it comprises an information display step of displaying together with the converted the notation the acquired additional information.

  In addition, the code | symbol etc. in the figure in embodiment corresponding to the component of a claim are shown by (). However, the constituent elements described in the claims are not limited to the constituent elements in the embodiment of the above () part.

  With the configuration described above, the language input system and the processing method thereof according to the present invention have the first contact information (130) in which contact information for personal use is stored and the contact information in which the contact information to be shared is stored. The dictionary data automatically extracted from the contact information included in each of the second contact information (131) which is a local cache in the client system (100) of the contact information (182) is used. Thereby, the Japanese input system of this embodiment can acquire the desired notation with respect to the input reading from a dictionary, and a user is not forced to take the next best measure in order to obtain a desired notation.

  Furthermore, the language input system and the processing method thereof according to the present invention include the first contact information (130) in which contact information for personal use is stored and the shared contact information in which contact information to be shared is stored. The second contact information (131), which is a local cache in the client system (100) of (182), is input using the additional information (307) data dynamically extracted from the contact information included in each. Additional information (307) is displayed along with a plurality of notations for reading. Thereby, the user who uses the Japanese input system of this embodiment can acquire efficiently the desired notation with respect to the reading input with reference to the comment even if there is a homonym.

  ADVANTAGE OF THE INVENTION According to this invention, in a language input system, there exists an effect which improves the ease of handling of a user related data.

  Embodiments to which the present invention can be applied will be described below in detail with reference to the drawings. In addition, the same code | symbol is attached | subjected to the location which has the same function in each drawing, and duplication of description is abbreviate | omitted.

(Device configuration)
FIG. 1 is a system block diagram of a Japanese input system for converting Japanese readings into desired Japanese notation in this embodiment. The Japanese input system of this embodiment has a PC 100 in which a Japanese input program for realizing Japanese notation conversion is installed. In the present embodiment, a Japanese language input system using a general-purpose PC equipped with Windows (registered trademark) as an OS will be described.

  In the PC 100 of FIG. 1, reference numeral 101 in the figure denotes a CPU (central processing unit), which executes a program loaded in a random access memory (RAM) of the system memory 102. A system memory 102 is a RAM (Read Only Memory) that stores various data such as input data necessary for a program executed by the CPU 101, execution results of the program, and a BIOS (Basic Input / Output System). Etc. The RAM of the system memory 102 temporarily stores data to be displayed on the display 107 and data input from the keyboard 106, modem 103, microphone 117, and the like.

  Reference numeral 103 denotes a modem, which may be an internal modem or an external modem, and is connected to the system bus 116 via an interface to establish communication on the wide area network 120 such as the Internet. Reference numeral 104 denotes a CD (compact disc) -ROM drive, which reads data from a mounted CD-ROM 105. In this embodiment, a program and data read from a CD-ROM 105 in which a Japanese input program and related data (system dictionary file or the like) are recorded are installed in a hard disk storage device (HD) 108 to be described later.

  Reference numeral 106 denotes a keyboard, and a character is input by pressing a key corresponding to the character. Reference numeral 117 denotes a microphone, which inputs the voice uttered by the user to the PC 100. Reference numeral 107 denotes a display that visually displays characters input from the keyboard 106 and the like and the calculation result of the CPU 101. The pointing device 115 can move a pointer (cursor figure) displayed on the display screen of the display 107 and can instruct the position for confirmation. In this embodiment, a mouse is used. . The pointer is moved by the user with the mouse 115 itself, and the position of the pointer is determined by the left and right click buttons. Reference numeral 116 denotes a system bus that connects the above-described elements of the PC 100.

  The HD 108 stores the following programs and data for the purpose of storage. Reference numeral 109 denotes an OS for controlling the PC 100 and peripheral devices. In the present embodiment, the above-described Windows (registered trademark) is used. Reference numeral 110 denotes various application programs other than the Japanese input program 114 of the present embodiment. For example, a browser for browsing a WEB page of WEB content, Explorer (trademark), word processor software, database software, spreadsheet Software, voice recognition software, etc.

  Reference numeral 111 denotes various program modules other than application programs, such as various device drivers and DLL (dynamic-link library) files that provide various APIs (Application Programming Interface). The program data 112 is various data used or generated by the OS and various other programs. The program data 112 includes various system dictionary files and user dictionary files associated with the Japanese input program of the present embodiment, and GUI (graphical user interface) data required for the Japanese input program to display a notation list. The system dictionary file supplied by the vendor includes system dictionary data, and the user dictionary file includes user dictionary data defined by the user.

  The communication program 124 is e-mail software for sending and receiving e-mails with other PCs. In this embodiment, Outlook (trademark) is assumed as the communication program 124, and this implements a function of exchanging messages mainly using electronic mail. The communication program 124 is installed in the HD 108 from a recording medium such as a CD-ROM or a floppy (registered trademark) disk (not shown) or via a communication medium.

  Information such as name, organization name, and telephone number related to the e-mail is hereinafter referred to as contact information. The Contacts file 130 is one of local files managed by Outlook (trademark) of the communication program 124. In the Contacts file 130, contact information personally used by the user of the PC 100, which is information for managing sent and received emails and various information related to the emails, is stored.

  The communication program 124 transmits and receives electronic mail via the mail server 160. The communication program 124 stores or reads out the contact information of the email related to transmission / reception in the storage (Contacts file 130 and DB server 170) of the communication program 124 as necessary.

  An OAB (Offline Address Book) file 131 is one of local files managed by Outlook (trademark) of the communication program 124. The OAB file 131 is a local cache in the PC 100 of a GAL (Global Address List) file 182 to be described later. The GAL file 182 is one of the shared files of the entire organization managed by the DB (database) server 170. The Outlook (trademark) of the communication program 124 periodically inquires the DB server 170 by a known protocol such as RPC (remote procedure call) or HTTP (HyperText Transport Protocol), and the OAB created by the DB server 170 from the GAL file 182. The file is downloaded and the OAB file 131 is updated with the data. This download functionality of Outlook ™ is well known to those skilled in the art.

Reference numeral 114 denotes a Japanese input program, which is a program shown in the flowcharts of FIGS. 6 and 7 that defines the contents of the Japanese input program processing performed by the CPU 101. The Japanese input program 114 according to the present embodiment accesses the Contacts file 130 and the OAB file 131 by inquiring Outlook (trademark) of the communication program 124 using a MAPI (messaging application programming interface) function well known to those skilled in the art.
Details of the Japanese input program 114 will be described later in the following description of the operation.

  MAPI is a standard specification for handling an e-mail function on Windows (registered trademark) announced by the applicant of the present application, and is a specification for making it possible to use an e-mail transmission / reception function from various application software. . MAPI provides a common program interface for applications, and information that has conventionally been provided separately for each application, such as mail address data, is also centrally managed by this MAPI. Mail software that supports MAPI can be used in conjunction with various software / hardware, such as sending mail directly from the menu of other application software, or sending mail written on mobile devices from a personal computer. Outlook (trademark), Netscape Messenger (trademark), etc. of this embodiment are compatible with MAPI.

  Reference numeral 120 denotes a wide area network, and the Internet is assumed in this embodiment. A WWW (World Wide Web) server 121 is connected to the wide area network 120. A web site of the vendor of the Japanese input program 114 that uses the system dictionary file of the present embodiment is published on the WWW server 121. In obtaining a new system dictionary file, it is possible to access the WEB site opened by the vendor of the Japanese input program 114 from the PC 100 via the network 120 and download the file from there.

  A mail server 160 and a DB server 170 are further connected to the wide area network 120. The mail server 160 exchanges electronic mail with other mail servers via the wide area network 120. The DB server 170 is accessible from one or more client machines (such as a PC) via the wide area network 120, and provides a database function for managing various data. When the PC 100 is a company PC, for example, the DB server 170 is a DB server managed and operated by the company.

  The DB server 170 has AD (Active Directory (trademark)) 181 installed therein, and the GAL file 182 is managed by the AD 181. Active Directory ™ is a directory service compliant with X.500 and is well known to those skilled in the art. The GAL file 182 is one of the shared files of the entire organization managed by the AD 181. The GAL file 182 stores contact information used in an organized manner for each user of the DB server 170, which is information for managing sent and received emails and various information related to the emails. The AD 181 creates an OAB file from the GAL file 182 and downloads the OAB file to the PC 100 in accordance with a periodic request from the Outlook (trademark) of the communication program 124.

  Active Directory (trademark) is a directory service implemented by Windows (registered trademark) of the applicant of the present application, and reduces management effort in a large-scale Windows (registered trademark) network system. Server systems and applications use Active Directory (trademark) to acquire necessary information such as user accounts and security. Active Directory (trademark) includes account information such as user name for each user, Windows (registered trademark) execution environment profile (user setting), e-mail address, address, group name, printer, shared resource name, computer Names, security policies, and other resources can be managed in a unified manner in the form of a tree.

  2A and 2B are table configuration diagrams showing examples of contact information according to the present embodiment. The contact information table mainly includes a reading field, a notation field, a comment field, and the like. The contact information including the table structure as shown in FIGS. 2A and 2B is stored in the Contacts file 130, the GAL file 182, the OAB file 131 that is a local cache of the GAL file 182, and the like.

  The example of the contact information shown in FIG. 2A includes a record having a reading field “None”, a notation field “Yamanashi”, and a comment field “A normal story”. The example of contact information shown in FIG. 2B includes a record having a reading field “None”, a notation field “Hanaichi”, and a comment field “xxx office”. Data obtained by combining the reading field and the notation field in the contact information constitutes dictionary data (lexicon) that can be extracted from the contact information. The comment field data in the contact information is comment data that can be extracted from the contact information. FIG. 2A is a diagram showing an example of contact information stored in the OAB file 131. FIG. 2B is a diagram illustrating an example of contact information stored in the Contacts file 130.

  In the contact information of the present embodiment, the last name and first name are managed in separate records. That is, for example, for the name “Taro Hashiri”, the contact information of this embodiment does not include a record having the reading field “Hanataro” and the notation field “Taro Hashiri”. The contact information of this embodiment includes, as separate records, a record having a reading field “None” and a notation field “Yamanashi” and a record having a reading field “Taro” and a notation field “Taro”.

  FIG. 3 is a system configuration diagram showing an outline of the operation of the Japanese input program 114. The Japanese input program 114 has a dictionary search module 114a and an LM module 114b.

  Basically, the dictionary search module 114a extracts one or more notations corresponding to the input reading 201 from the system dictionary file 202 in the vendor-supplied default lexicon DB and the user dictionary file 203 in the user lexicon DB. It is. Further, the dictionary search module 114a manages the update and deletion of data in the user dictionary file 203. The LM module 114b is a module that determines an optimal notation output 205 of one notation from one or more notations extracted by the dictionary search module 114a by language processing using the learning result file 204 in the LM.

  The system dictionary file 202 includes system dictionary data 202a. The learning result file 204 includes learning result data 204a. The user dictionary file 203 includes, for example, proper noun dictionary data not shown, E (electronic) mail response dictionary data, abbreviation dictionary data, document folder dictionary data, new word dictionary data, and the like.

  Further, the user dictionary file 203 of the present embodiment includes OAB dictionary data 203a and Contacts dictionary data 203b. The Japanese input program 114 accesses the Outlook Contacts (trademark) of the communication program 124 and accesses the Contacts file 130 and the OAB file 131 by the MAPI function. Then, dictionary data automatically extracted from the contact information illustrated in FIG. 2A included in the OAB file 131 by the Japanese input program 114 (lexicon; data combining the reading field and the notation field) OAB dictionary data 203a. The dictionary data automatically extracted from the contact information illustrated in FIG. 2B by the Japanese input program 114 included in the Contacts file 130 is the Contacts dictionary data 203b.

  In particular, the present embodiment has a feature in the management method of the OAB dictionary data 203a and the Contacts dictionary data 203b in the user dictionary file 203 by the dictionary search module 114a. The management method of each dictionary data and each of these in FIG. The data is described in detail below.

  The learning result data 204a records the learning result of the kana-kanji conversion process when the LM module determines the notation output 205. As a method of recording a learning result in LM, there are a word bigram method and various other methods. In this embodiment, a learning routine using a well-known flag count is applied.

(Description of operation)
In the system configuration described above, the operation of the Japanese input program 114 of the Japanese input system for converting Japanese readings of the present embodiment into a desired Japanese notation will be described below with reference to FIGS. .

  The Japanese input system according to the present embodiment includes an OAB file 131 that is a local cache in the PC 100 of the Contacts file 130 that stores personal contact information and the GAL file 182 that stores shared contact information. It is characterized by using dictionary data automatically extracted from the contact information included in each.

  Further, the Japanese input system of the present embodiment is an OAB that is a local cache in the PC 100 of the Contacts file 130 that stores personally used contact information and the GAL file 182 that stores shared contact information. A feature is that comment data dynamically extracted from contact information included in each of the files 131 is used, and comments are displayed along with a plurality of notations for the input reading.

  FIG. 4 shows a case where the Japanese input program 114 refers to each of the above-mentioned dictionary files and converts the input reading “None” into an appropriate notation acquired from each dictionary while editing a document by word processing software, for example. It is a figure which shows the example of.

  The Japanese input program 114 refers to each dictionary file, and acquires one or more notations for the reading “None” input at the position of the reference numeral 301 in the drawing on the display screen. The Japanese input program 114 displays these notations as a notation list 302 on the display screen on the display 107 of the PC 100. At this time, the fraction “6/6” of the reference numeral 303 displayed in the notation list 302 is 6 out of 6 notations of “Hanaichi” where the focus (highlighted for highlighting) 304 is located. Indicates the second notation.

  The Japanese input program 114 moves the focus when the user depresses the down (down) key or the like of the PC keyboard 106, and closes the notation list 302 when the user presses the enter key (for example, the enter key). Then, the Japanese input program 114 converts the input reading “None” into a single notation “Hanaichi” selected by the user by moving the focus at the position of reference numeral 301.

  The notations “Hashiri” and “Hanaichi” in the notation list 302 have □ marks 305 and 306, respectively. The notation with □ is a notation obtained by referring to the OAB dictionary data 203a or the Contacts dictionary data 203b in the user dictionary file 203. In the example of FIG. 4, the notation “Yashiri” with □ in the notation list 302 is acquired by referring to the OAB dictionary data 203 a extracted from the contact information illustrated in FIG. 2A included in the OAB file 131. It is a notation. The notation “Hanaichi” with □ in the notation list 302 is a notation obtained by referring to the Contacts dictionary data 203b extracted from the contact information illustrated in FIG. 2B included in the Contacts file 130.

  Further, the Japanese input program 114 displays a comment for the notation with □ along with the notation. In the example of FIG. 4, a comment 307 is displayed on the right side of the notation “Hanaichi” with □ where the focus 304 is located. The Japanese input program 114 reads the comment information “ordinary story” extracted from the record corresponding to the reading “None” and the notation “Yaashi” of the contact information included in the OAB file 131 as illustrated in FIG. Refer to and get. At the same time, the Japanese input program 114 reads the comment information “xxx office” extracted from the record corresponding to the reading of “None” and the notation “Hanaichi” as shown in FIG. 2B included in the Contacts file 130. Refer to and get. The Japanese input program 114 merges all the above-mentioned comment data “ordinary story”, “xxx office”, etc. extracted corresponding to the reading “nothing”, and the notation “Harin” and the comment data “ordinary” The pair of “Nanohanasan”, the notation “Hanaichi” and the comment data “xxx office”, and the like are displayed as a comment 307. In the example of FIG. 4, a comment 307 similar to the above is displayed on the right side of the notation “Yashiri” with the □ mark even when the focus 304 is moved to the notation “Yashiri” with the □ mark. That is, the Japanese input program 114 always displays a comment 307 similar to the above on the right side of the same reading “None” with a □ mark.

  As described above, the notation with □ indicates that it is a notation with a comment obtained by referring to the OAB dictionary data 203a or the Contacts dictionary data 203b in the user dictionary file 203.

  It should be noted that by using the comment data described above, the Japanese input system of the present embodiment displays information that can identify a person as illustrated in FIG. A user who uses the Japanese input system of the present embodiment can efficiently obtain a desired personal name notation for a reading input with reference to a comment even if there is a personal name of a homonym.

  FIG. 5 is a diagram showing the structure of the system dictionary file 202, the user dictionary file 203, and the learning result file 204.

  FIG. 5 shows a notation list table 601 having one or more notations for the reading “none”, which is acquired by referring to the learning result file 204 when the Japanese input program 114 displays the above-described notation list 302. The learning result file 204 is a file that stores learning result data 204a including one or more notation list tables corresponding to each reading.

  In FIG. 5, the notation list table 601 includes a plurality of records each having a reading field 602 (data is “none”), a notation field 603, and a flag count field 604. For example, in the record 605, the notation for the reading “None” is “Talk” and the flag count is “4”. The flag count indicates the priority order displayed at the top of the notation list 302 for the notation having the flag count. The notation possessed by the records in the descending order of the flag count of the records in the notation list table 601 is displayed in the notation list 302.

  Here, for example, it is assumed that at the position indicated by reference numeral 301 in FIG. 4, the input reading “NONE” is converted into one notation “spoken” selected and confirmed by the user moving the focus. In this case, the Japanese input program 114 increments (++) the flag count of the record 605 in FIG. 5 to “5” by the LM module, and records the learning result of the kana-kanji conversion process when it is confirmed.

  FIG. 5 also shows a system dictionary table 606 having one or more notations for each reading. The system dictionary file 202 is a file in which system dictionary data 202a including such a system dictionary table 606 and a data name (system dictionary data) is stored.

  In FIG. 5, the system dictionary table 606 includes a plurality of records each having a reading field and a notation field. For example, the record group 607 is read in order from the top, and the notation for “no, no, no, no” is “talk, speak, release, jealousy”. Note that the record group to which the flag count is added to the record group 607 already exists in the notation list table 601 of the reading “None” in the learning result data 204a as the previous learning result.

  FIG. 5 also shows an OAB dictionary table 608 that has one or more notations for each reading. The user dictionary file 203 is a file in which OAB dictionary data 203a including such an OAB dictionary table 608 and a data name (OAB dictionary data) is stored. Further, FIG. 6 shows a Contacts dictionary table 610 having one or more notations for each reading. The user dictionary file 203 is a file in which the Contacts dictionary data 203b including the Contacts dictionary table 610 and the data name (Contacts dictionary data) is stored.

  Here, the case where the dictionary search module 114a creates the OAB dictionary data 203a and stores it in the empty layer in the user dictionary file 203 will be described with reference to FIG. In this case, if the layer 1 is an empty layer, the OAB dictionary data 203a is inserted and stored in the layer 1.

  FIG. 5 shows an OAB dictionary table 608 having one or more notations for each reading when the OAB dictionary data 203a is stored. The user dictionary file 203 is a file in which OAB dictionary data 203a including such an OAB dictionary table 608 and a data name (OAB dictionary data) is stored.

  In FIG. 5, the OAB dictionary table 608 includes a plurality of records having a reading field and a notation field. For example, in the record 609, the notation for the reading “None” is “Yamanashi”. Here, in synchronization with the insertion of the OAB dictionary data 203a into layer 1, a record in which a flag count 0 is added to the record 609 (reading “none”, notation “Yamanashi”) is the reading “none” in the learning result data 204a. Is added to the notation list table 601.

  In synchronism with the insertion of the OAB dictionary data 203a into layer 1, a record other than the record 609 (reading “None”, notation “Yamanashi”) (for example, reading “Tokio”, notation “TOKIO”) has a flag count of 0. Is added to the notation list table of the reading “Tokio” in the learning result data 204a.

  Further, a case where the dictionary search module 114a creates the Contacts dictionary data 203b and stores it in the empty layer in the user dictionary file 203 will be described with reference to FIG. In this case, if the layer 2 is an empty layer, the Contacts dictionary data 203b is inserted and stored in the layer 2.

  FIG. 5 shows a Contacts dictionary table 610 having one or more notations for each reading when the Contacts dictionary data 203b is stored. The user dictionary file 203 is a file in which the Contacts dictionary data 203b including the Contacts dictionary table 610 and the data name (Contacts dictionary data) is stored.

  In FIG. 5, the Contacts dictionary table 610 includes a plurality of records having a reading field and a notation field. For example, in the record 611, the notation for the reading “None” is “Hanaichi”. Here, in synchronization with the insertion of the Contacts dictionary data 203b into Layer 2, the record with the flag count 0 added to the record 611 (reading “None”, notation “Hanaichi”) is the reading “None” in the learning result data 204a. Is added to the notation list table 601.

  In synchronism with the insertion of the Contacts dictionary data 203b into layer 2, records other than the record 611 (reading “None”, notation “Hanaichi”) (for example, reading “Tokio”, notation “Tokio”) are also flag-counted. The record to which 0 is added is added to the notation list table of the reading “Tokio” in the learning result data 204a.

(Program processing explanation)
The process related to Japanese input in the present embodiment is performed according to the processing procedure shown in the flowcharts of FIGS. 6 and 7 show the contents of the Japanese input program processing executed by the CPU 101. The CPU 101 loads the Japanese input program 114 stored in the HD 108 into the RAM of the system memory 102 and executes it. Is done. Hereinafter, the processing procedure of the Japanese input program 114 performed by the CPU 101 will be described with reference to FIGS.

  Here, it is assumed that after the OS 109 is booted, the Japanese input program 114 is automatically resident in the system memory 102 and started by the OS 109.

  In FIG. 6, the CPU 101 determines whether there is an event from the OS (step S700). When detecting an event from the OS, the CPU 101 determines whether or not the event is a document editing start event (activation of an application such as word processing software) by the application program (step S702).

  In the case of starting the editing of the document, in step S716, the CPU 101 accesses the Outlook Contacts ™ of the communication program 124 and accesses the Contacts file 130 and the OAB file 131 by the MAPI function. The CPU 101 automatically extracts the OAB dictionary data 203a from the contact information illustrated in FIG. 2A included in the OAB file 131 and illustrated in FIG. 2B included in the Contacts file 130. The contact dictionary data 203b is automatically extracted from such contact information, and the OAB dictionary data 203a and the contacts dictionary data 203b are stored on the RAM of the system memory 102. Here, as shown in FIG. 5, the OAB dictionary data 203a includes an OAB dictionary table 608 having a data name (OAB dictionary data) to be inserted into the layer 1 of the empty layer and an extracted new word record. Further, as shown in FIG. 5, the Contacts dictionary data 203b includes a Contacts dictionary table 610 having a data name (Contacts dictionary data) to be inserted into the empty layer 2 and an extracted new word record.

  The CPU 101 inserts the OAB dictionary data 203a into the empty layer (layer 1) in the user dictionary file 203 and stores it, and inserts the Contacts dictionary data 203b into the empty layer (layer 2) in the user dictionary file 203 for storage. (Step S718). Further, in synchronization with the insertion of the OAB dictionary data 203a and the Contacts dictionary data 203b into the empty layer, the CPU 101 adds records related to the OAB dictionary data 203a and the Contacts dictionary data 203b to the learning result data 204a (step S720). That is, as shown in FIG. 5, for example, record 609 (reading “None”, notation “Yamanashi”) and other records (eg, reading “Tokio”, notation “TOKIO”) are set with a flag count of 0. Each added record is added to each notation list table such as “None” or “Tokio” in the learning result data 204a. Also, for example, for records 611 (reading “None”, notation “Hanaichi”) and other records (eg, reading “Tokio”, notation “Tokio”), each record with flag count 0 is learned. The readings in the result data 204a are added to each notation list table such as “None”, “Tokio”, and the like. Then, the CPU 101 returns to waiting for an event from the OS (step S720 → S700).

  On the other hand, if the event from the OS is other than the start of document editing, the CPU 101 determines whether the event is a reading input by the keyboard 106 (steps S702 → S790). If the event from the OS is a reading input, the CPU 101 proceeds to the process shown in FIG. 7 (step S790 → FIG. 7). In cases other than reading input from the OS, the CPU 101 determines whether the event is a document editing end event by the application program (steps S790 → S795). If the event from the OS is the end of document editing, the CPU 101 returns to waiting for an event from the OS (steps S795 → S700). If the event from the OS is other than the end of document editing, the CPU 101 performs processing corresponding to the event and returns to waiting for an event from the OS (steps S798 → S700).

  In FIG. 7, when the event from the OS is a reading input, the CPU 101 stores the reading “nothing” information input from the keyboard 106 as described above with reference to FIG. 4, for example, on a buffer on the RAM of the system memory 102. (Step S800). Next, the CPU 101 recognizes the notation list table 601 corresponding to the input reading “None” from the learning result data 204a (step S802). The CPU 101 edits in the buffer the data of the notation list 302 in which the notations of the records are arranged in descending order of the flag counts of the records in the notation list table 601 (step S804).

  Subsequently, when the CPU 101 detects an input event of the conversion key of the user, the first notation (spoken) acquired from the data of the notation list 302 edited on the buffer in step S804 is denoted by reference numeral 301 as the first conversion character string. The input reading “None” is displayed at the position (step S806).

  After the display of the first converted character string, when the CPU 101 detects an input event of the confirmation key, an application program (for example, editing a document with the first converted character string as the confirmed character string in a series of steps S808 → S816 → S818) Word processing software) and post-processing (S816 → S818) is performed. The post-processing will be described later.

  On the other hand, in step S808, after detecting the conversion key input event again after the first conversion character string, the CPU 101 displays the data of the notation list 302 edited on the buffer as the notation list 302 as shown in FIG. It is displayed on the screen (steps S808 → S810).

  Next, as shown in FIG. 4, the CPU 101 moves the focus 304 indicating the notation in the displayed notation list 302 downward to the input event of the conversion key and the down (↓) key, and the up (↑) key. Move upward for an input event. When the focus 304 exceeds the upper and lower limits of the notation list 302, the CPU 101 scrolls and updates the notation list 302. This process is performed by a process that loops between step S811 and step S815.

  Processing in steps S812 to S814 performed during the loop processing between steps S811 and S815 will be described. In step S812, the CPU 101 always displays the notation designated by the focus 304 acquired from the data of the notation list 302 edited on the buffer at the position of the reading “None” to which the reference numeral 301 is input as a converted character string. .

  In step S813, the CPU 101 accesses the inquiry Contacts file 130 and the OAB file 131 to the Outlook (trademark) of the communication program 124 using the MAPI function. Then, the CPU 101 tries to obtain a comment related to all of the same reading “None” that appears in the notation list 302. In other words, the CPU 101 refers to the comment data “ordinary story” extracted from the record corresponding to the reading “None” and the notation “Yaashi” of the contact information illustrated in FIG. 2A included in the OAB file 131. And get. At the same time, the Japanese input program 114 reads the comment information “xxx office” extracted from the record corresponding to the reading of “None” and the notation “Hanaichi” as shown in FIG. 2B included in the Contacts file 130. Refer to and get. In this way, the CPU 101 stores all the above-mentioned comment data “ordinary story”, “xxx office” and the like extracted corresponding to the reading “nothing” on the RAM of the system memory 102. If there is no comment data, the comment data is naturally not acquired from the record. In this way, every time the focus moves, the CPU 101 accesses the Contacts file 130 and the OAB file 131 and dynamically extracts comment data corresponding to the input reading “None”.

  In step S <b> 814, the CPU 101 merges all the above-described comment data “ordinary story” and “xxx office” extracted corresponding to the reading “nothing” on the RAM of the system memory 102, and displays the notation “ A pair of “Hashiri” and the comment data “ordinary story”, a pair of the notation “Hanaichi” and the comment data “xxx office”, and the like are displayed as a comment 307 illustrated in FIG.

  When the CPU 101 detects a determination key input event in step S815, the CPU 101 performs post-processing (steps S816 → S818). As a post-processing, the CPU 101 first closes the notation list 302 in a series of processes from step S816 to S818, and an application program (for example, word processing software) that is currently editing a document with the converted character string (the notation focused) as a confirmed character string. To pass.

  Here, for example, it is assumed that at the position indicated by reference numeral 301 in FIG. 4, the input reading “NONE” is converted into one notation “spoken” selected and confirmed by the user moving the focus. In this case, the CPU 101 increments (++) the flag count of the record 605 in the notation list table 601 of the learning result data 204a in FIG. 5 to “5”, and the learning result of the kana-kanji conversion process when it is confirmed Is recorded (step S820). Thereafter, the CPU 101 returns to waiting for an event from the OS (step S700 in FIG. 6).

(Effect of embodiment)
As described above, according to the present embodiment, as a first aspect, the language input system that converts the reading into a desired notation includes the first contact information (130) related to the communication partner and the first contact information (130). Information management means (101, 124) for managing the second contact information (131) different from the contact information of the one and one or more notations for the input readings in a predetermined language, A client system (100) having language input means (101, 114) for selecting one notation from the displayed notations, and connected to the client system, and one or more other It is further connectable to a client system and has shared contact information (182) accessed and shared by the client system and the one or more other clients. The information management means periodically acquires the shared contact information from the server system, and updates the second contact information with the acquired shared contact information. The language input means acquires the first contact information and the second contact information from the information management means, and from the acquired first contact information and the second contact information. Dictionary creation means (FIG. 6) for creating dictionary data (203a, 203b), and conversion display means for referring to the dictionary data created by the dictionary creation means, converting input readings into notations and displaying the notations (S812) and corresponding to the input reading and the converted notation included in the first contact information and the second contact information when displayed by the conversion display means Pressurized information (307) acquired from the information managing means (S813), and having an information display means for displaying together with the converted the notation the acquired additional information (S814).

  Here, as a second aspect, in the language input system according to the first aspect, the language input means further includes a detection means for detecting activation of an application program for editing a document, and the dictionary creation means The dictionary data can be automatically created when the activation is detected by the detecting means.

  Moreover, as a third aspect, in the language input system according to the first or second aspect, the shared contact information and the first contact information are managed by separating a first name and a last name. can do.

  Further, as a fourth aspect, in the language input system according to any one of the first to third aspects, the predetermined language may be Japanese.

  With the above configuration, the Japanese input system according to the present embodiment has a local cache in the PC 100 of the Contacts file 130 storing contact information for personal use and the GAL file 182 storing contact information used for sharing. The dictionary data automatically extracted from the contact information included in each of the OAB files 131 is used. Thereby, the Japanese input system of this embodiment can acquire the desired notation with respect to the input reading from a dictionary, and a user is not forced to take the next best measure in order to obtain a desired notation.

  Further, the Japanese input system of the present embodiment is an OAB that is a local cache in the PC 100 of the Contacts file 130 that stores personally used contact information and the GAL file 182 that stores shared contact information. Using comment data dynamically extracted from contact information included in each of the files 131, comments are displayed along with a plurality of notations for the input reading. Thereby, the user who uses the Japanese input system of this embodiment can acquire efficiently the desired notation with respect to the reading input with reference to the comment even if there is a homonym.

  In addition, the Japanese input system of the present embodiment caches and uses the GAL file 182 storing contact information to be shared and stored in the local OAB file 131 in the PC 100. Thereby, the Japanese input system of this embodiment does not apply an excessive load to the network during processing.

  Further, the Japanese input system of the present embodiment manages the first name and last name in separate records in the contact information. Thereby, even if the contact information is stolen, only the first name or last name information is recognized, so that it is possible to realize high resistance against personal information leakage.

(Other embodiments)
In addition to the embodiments described above, the following embodiments can be implemented.
1) In the above-described embodiment, for convenience of illustrating one embodiment, the layer structure of a plurality of dictionary data (such as OAB dictionary data 203a and Contacts dictionary data 203b) in one user dictionary file 203 has been described. However, the present embodiment is not limited to this, and each dictionary data (OAB dictionary data 203a, Contacts dictionary data 203b, etc.) constitutes one user dictionary file, and has a layer structure of the plurality of user dictionary files. It will be readily understood by those skilled in the art that variations are possible.

  Furthermore, although the case where one system dictionary file 202 includes one system dictionary data 202a has been described in the above-described embodiment, the present embodiment is not limited to this, and the system dictionary file includes a plurality of embodiments, or Those skilled in the art will readily understand that one system dictionary file can be modified into an embodiment including a plurality of system dictionary data.

2) In the above-described embodiment, an example in which kana-kanji conversion processing is performed on the reading “nothing” input at the position of the reference numeral 301 on the display screen of the display 107 input by the user using the keyboard 106. Explained. However, the present invention is not limited to kana-kanji conversion, but can be applied to all language processing systems. For example, the input of reading is not limited to a keyboard, and the present invention can also be applied to the case where a voice uttered by a user is input to the PC 100 with a microphone and the result of the recognition of the voice by voice recognition software is captured and processed. Will be easily understood by those skilled in the art.

3) In the above-described embodiment, an example of a Japanese input system that processes Japanese is shown, but the present invention is not limited to Japanese. Those skilled in the art will readily understand that the present invention is applicable to various languages having homonyms.

4) In the above-described embodiment, an example in which the Japanese input system is realized by a general-purpose personal computer has been described. The present invention can be applied to other information processing apparatuses capable of executing various programs.

5) The recording medium referred to in the present invention refers to a medium in which a program executed by the CPU is recorded and can be read by the device. As the recording medium, in addition to the CD-ROM, a known recording medium such as an IC (integrated circuits) memory, an HD, a floppy (registered trademark) disk, a magneto-optical disk (MO) can be used.
The program recorded on the recording medium may be any of the program itself, a compressed program, and an encrypted program, and all these data are included in the concept of the program of the present invention.
Further, when transferring (downloading) a program to an information processing apparatus via a network such as the Internet or a LAN (local area network) or a signal line, a recording medium or storage device for storing the program of the transfer source apparatus is provided. This corresponds to the recording medium of the present invention.

6) Although the above-described embodiment has been described for the purpose of illustrating the present invention, modifications can be made in addition to the above-described embodiment. As long as the modification is based on the technical idea of the present invention described in the claims, the modification is within the technical scope of the present invention.

It is a system block diagram of the Japanese input system which has PC which installed the Japanese input program of embodiment which can apply this invention. FIG. 3 is a table configuration diagram illustrating an example of contact information according to an embodiment to which the present invention can be applied, where (a) illustrates an example of contact information stored in an OAB file, and (b) illustrates a contact stored in a Contacts file. It is a figure which shows the example of information. It is a system configuration | structure figure which shows the operation | movement outline | summary of the Japanese input program of embodiment which can apply this invention. It is a figure which shows the example in the case of converting into the input appropriate reading notation of embodiment which can apply this invention. It is a figure which shows the structure of the system dictionary file of embodiment which can apply this invention, a user dictionary file, and a learning result file. It is a flowchart which shows the Japanese input program process which CPU of embodiment which can apply this invention performs. It is a flowchart which shows the Japanese input program process which CPU of embodiment which can apply this invention performs.

Explanation of symbols

100 Personal computer 101 CPU
102 System memory 103 Modem 104 CD-ROM drive 105 CD-ROM
106 Keyboard 107 Display 108 HD
109 OS
110 Various application programs 111 Various program modules 112 Program data 114 Japanese input program 115 Mouse 116 System bus 117 Microphone 120 Wide area network 121 WWW server 124 Communication program 130 Contacts file 131 OAB file 160 Mail server 170 DB server 181 AD ( Active Directory (trademark)
182 GAL file

Claims (11)

A language input system that converts readings into desired notation,
Information management means for managing first contact information related to a communication partner and second contact information different from the first contact information;
A client system comprising: language input means for displaying one or more notations for an input reading in a predetermined language and selecting one notation from the displayed notations;
Connected to the client system, further connectable to one or more other client systems, having shared contact information accessed and shared from the client system and the one or more other clients A server system,
The information management means periodically acquires the shared contact information from the server system, updates the second contact information with the acquired shared contact information,
The language input means includes
The learning result file creation means for obtaining the first contact information and the second contact information from the information management means and creating a learning result file having a flag count, When dictionary data is extracted as each record from the contact information and the second contact information, and the extracted record does not exist in the learning result file, the flag count is set to 0 for the record Learning result file creating means for adding a record to the learning result file;
From the learning result file created by the learning result file creating means, obtain a notation list corresponding to the input reading, notation list display means for editing and displaying the data of the notation list in descending order of flag count,
When displaying by the notation list display means, the additional information corresponding to the input notation of the input included in the acquired notation list is acquired from the information management means, and the acquired additional information is acquired from the notation list. Information display means for displaying together with the notation list in association with each notation of
A language which includes flag count increment means for incrementing a flag count corresponding to the confirmed notation in the learning result file in response to the user selecting and confirming the notation from the notation list. Input system. The language input means further includes a detection means for detecting the activation of an application program for editing a document,
The language input system according to claim 1, wherein the learning result file creation unit automatically creates the learning result file when the detection unit detects the activation. The language input system according to claim 1 or 2, wherein the shared contact information and the first contact information are managed by separating a first name and a last name. The language input system according to any one of claims 1 to 3, wherein the predetermined language is Japanese. A client system for a language input system, comprising: the information management unit and the language input unit included in the client system according to claim 1. A method of processing a language input system that converts readings into desired notation,
The language input system includes:
Information management means for managing first contact information related to a communication partner and second contact information different from the first contact information, and one or more for an input reading in a predetermined language or A client system having a language input means for displaying a plurality of notations and selecting one notation from the displayed notations;
Connected to the client system, further connectable to one or more other client systems, having shared contact information accessed and shared from the client system and the one or more other clients Server system,
The processing method is:
An information management step in which the information management means periodically acquires the shared contact information from the server system, and updates the second contact information with the acquired shared contact information;
The language input means obtains the first contact information and the second contact information from the information management means, and creates a learning result file having a flag count. Dictionary data is extracted as each record from the acquired first contact information and second contact information, and if the extracted record does not exist in the learning result file, the flag count for the record A learning result file creation step of setting a record to 0 and adding a record to the learning result file;
The language input means obtains a notation list corresponding to the input reading from the learning result file created in the learning result file creation step, and edits and displays the data of the notation list in descending order of flag count A list display step;
When the language input means displays in the conversion display step, the additional information corresponding to the input reading notation included in the acquired notation list is acquired from the information management means, and the acquired additional An information display step for displaying information together with the notation list in association with each notation of the notation list;
A flag count increment step in which the language input means increments (++) a flag count corresponding to the confirmed notation in the learning result file in response to the user selecting and confirming the notation from the notation list. A method for processing a language input system, comprising: The language input means further comprises a detection step of detecting activation of an application program for editing a document;
7. The language input system according to claim 6, wherein in the learning result file creation step, the language input unit automatically creates the learning result file when the activation is detected in the detection step. 8. Processing method. The processing method of the language input system according to claim 6 or 7, wherein the shared contact information and the first contact information are managed by separating a first name and a last name. The processing method of the language input system according to claim 6, wherein the predetermined language is Japanese.   10. A computer-readable recording medium in which a program for causing a computer to execute each step performed by the language input unit of the processing method of the language input system according to claim 6 is recorded.   A program for causing a computer to execute each step performed by the language input unit of the processing method of the language input system according to any one of claims 6 to 9.

Images