US 7,099,876 B1Grant

Method, system and computer program product for storing transliteration and/or phonetic spelling information in a text string class

Issue Date:2006-08-29

•19 Claims

•7 Drawing Sheets

Abstract

A multi-field text string data structure is employed to encapsulating identification, meaning, and pronunciation information for a text string. A first field contains the Unicode characters for the text string in a language in which the text string is entered, which may be latin characters, characters which sound-map to latin characters, or one or more ideographs. A second field contains either the same characters or an intermediate representation of the text string, such as syllabary characters for a phonetic spelling of the characters within the first field. A third field contains either the same characters as the first field or a latin character phonetic spelling of the characters in the first field. The first field thus contains the text string in the language in which the text string was entered, while the second and third field contains information about the meaning and pronunciation of the text string. When the characters in the first field are unrecognizable to a user, or when the characters in the first field have more than one meaning or more than one pronunciation, the contents of the second and third fields allow the user to recognize the text string and/or perceive the correct meaning and pronunciation of the text string.

Metadata

Assignee

International Business Machines Corporation

Inventors

David James Hetherington
David Bruce Kumhyr

Application Information

Application Number:US 09/211,803

Filing Date:1998-12-15

Priority Date:1998-12-15

Art Unit:2161

Classifications

IPC:

G06F17/30

Patent Drawings (7 sheets)

Description

Related Applications

[0001] The present invention is related to the subject matter of the following commonly assigned, copending United States patent applications: Ser. No. 09/211,810 entitled “METHOD, SYSTEM, AND COMPUTER PROGRAM PRODUCT FOR PROVIDING A USER INTERFACE WITH ALTERNATIVE DISPLAY LANGUAGE CHOICES” and filed Dec. 15, 1998; Ser. No. 09/211,809 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR CAPTURING LANGUAGE TRANSLATION AND SORTING INFORMATION INTO A TEXT STRING CLASS” and filed Dec. 15, 1998; Ser. No. 09/211,808 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR SORTING TEXT STRINGS” and filed Dec. 15, 1998; Ser. No. 09/211,799 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR ROTATING THROUGH A SEQUENCE OF DISPLAY STATES IN A MULTI-FIELD TEXT CLASS IN A GRAPHICAL USER INTERFACE” and filed Dec. 15, 1998; Ser. No. 09/211,802 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR CONTROLLING THE GRAPHICAL DISPLAY OF MULTI-FIELD TEXT STRING OBJECTS” and filed Dec. 15, 1998; Ser. No. 09/211,813 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR DISPLAYING THE CONTENTS OF ALL FIELDS IN A MULTI-FIELD TEXT STRING OBJECT” and filed Dec. 15, 1998; Ser. No. 09/211,801 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR DYNAMIC LANGUAGE SWITCHING IN A MULTI-FIELD TEXT STRING OBJECT VIA MESSAGING” and filed Dec. 15, 1998; and Ser. No. 09/211,812 entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR AUTOMATIC CHARACTER TRANSLITERATION IN A TEXT STRING OBJECT” and filed Dec. 15, 1998. The content of the above-referenced applications is incorporated herein by reference.

Background of the Invention

[0002] 1. Technical Field

[0003] The present invention relates in general to text strings in data processing systems and in particular to encapsulation of identification, meaning or pronuciation information in text strings. Still more particularly, the present invention relates to a multi-field text string encapsulating identification, meaning, and pronunciation information utilizing different character sets.

[0004] 2. Description of the Related Art

[0005] Multinational companies often run information system (IS) networks which span multiple countries spread around the globe. To maximize the usefulness of such networks, operations within each locale tend to run in the local language of the region. Where possible, names of abstract objects in user applications are in the local language and match the local language organization, city, or human names which the abstract objects represent. In the case of system management software, often abstract objects would represent each of a global enterprise's local offices.

[0006] Central management of such a global network may be difficult or impossible when abstract object names utilize the local language and the local language's underlying character set. For offices located in Egypt, abstract objects would most naturally be named in Arabic; offices in Russia would name objects utilizing the Cyrillic character set; and for offices in Japan, objects would be named in Japanese. A problem arises, however, when a enterprise's headquarters IS staff attempts to examine these objects. The IS staff at the multinational headquarters located in the United States is unlikely to be able to read Arabic or Japanese, or even recognize Cyrillic characters.

[0007] Japanese, for example, is a logosyllabic or ideographic language which does not have an alphabet representing simple sounds, but instead has a very large character set with symbols (“ideographs”) corresponding to concepts and objects rather than simple sounds. For instance, the Joyo Kanji List (Kanji for Daily Use) adopted for the Japanese language in 1981 includes 1945 symbols. Users unfamiliar with the Kanji characters will have difficulty identifying a particular abstract object named in Japanese, as well as difficulty even discussing such abstract objects over the telephone with an English- and Japanese-speaking counterpart.

[0008] Additionally, merely seeing an ideograph may provide no clue as to the correct meaning or pronunciation since, in Japanese, the same character may have multiple meanings or pronunciations. For instance, the character depicted in FIG. 7A may mean either “West” or “Spain”; the symbol depicted in FIG. 7B may be pronounced either “hayashi” or “rin” (or “lin”); and the characters depicted in FIG. 7C may be pronounced “suga no,” “suga ya,” “kan no,” or “kan ya.” This circumstance is based in part on the history of the Japanese language, in which the Kanji characters were adopted from the Chinese language in several waves. Thus, for example, the “rin” symbol depicted in FIG. 7B is On-Yomi, basically a simulation of the Chinese pronunciation when the character was imported to Japan, while “hayashi” is Kun-Yomi, a Japanese word assigned to the character which has the same meaning.

[0009] It would be desirable, therefore, to provide a data processing system text string encapsulating identification, meaning, and pronunciation information utilizing different character sets.

Summary of the Invention

[0010] It is therefore one object of the present invention to provide improved method, system and computer program product for storing text strings in data processing systems.

[0011] It is another object of the present invention to provide a method, system and computer program product for encapsulation of identification, meaning or pronuciation information in text strings employed by data processing systems.

[0012] It is yet another object of the present invention to provide a method, system and computer program product for implementing a multi-field text string encapsulating identification, meaning, and pronunciation information utilizing different character sets.

[0013] The foregoing objects are achieved as is now described. A multi-field text string data structure is employed to encapsulating identification, meaning, and pronunciation and/or sorting information for a text string. A first field contains the characters for the text string in a language in which the text string is entered, which may be latin characters, characters which sound-map to latin characters, or one or more ideographs. A second field contains either the same characters or an intermediate representation of the text string, such as syllabary characters for a phonetic spelling of the characters within the first field. A third field contains either the same characters as the first field or a latin character phonetic spelling of the characters in the first field. The first field thus contains the text string in the language in which the text string was entered, while the second and third field contains information about the meaning and pronunciation of the text string. When the characters in the first field are unrecognizable to a user, or when the characters in the first field have more than one meaning or more than one pronunciation, the contents of the second and third fields allow the user to recognize the text string and/or perceive the correct meaning and pronunciation of the text string.

[0014] The above as well as additional objects, features, and advantages of the present invention will become apparent in the following detailed written description.

Brief Description of the Drawings

[0015] The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

[0016] FIG. 1 depicts a diagram of a data processing system in which a preferred embodiment of the present invention may be implemented;

[0017] FIG. 2 is a diagram of a multi-field text string class employed in encapsulating transliteration and/or phonetic spelling information in accordance with a preferred embodiment of the present invention;

[0018] FIG. 3 depicts a high level flowchart for a process of entering data into a multi-field text string class in accordance with a preferred embodiment of the present invention;

[0019] FIGS. 4A–4B are portions of a user interface showing one application for character-mapped data entry into alternate fields of a multi-field text string class in accordance with a preferred embodiment of the present invention;

[0020] FIG. 5 is a high level flowchart for a process of data entry in a logosyllabic language into a multi-field text string class in accordance with a preferred embodiment of the present invention;

[0021] FIGS. 6A–6G are illustrations of user interface displays for a process of data entry in a logosyllabic language into a multi-field text string class in accordance with a preferred embodiment of the present invention; and

[0022] FIGS. 7A–7C are pictorial representations of known Japanese ideographs which may have multiple meanings or pronunciations.

Detailed Description of the Preferred Embodiment

[0023] With reference now to the figures, and in particular with reference to FIG. 1, a block diagram of a data processing system in which a preferred embodiment of the present invention may be implemented is depicted. Data processing system 100 may be, for example, one of the Aptiva® models of personal computers available from International Business Machines Corporation of Armonk, N.Y. Data processing system 100 includes a processor 102, which in the exemplary embodiment is connected to a level two (L2) cache 104, which is connected in turn to a system bus 106. In the exemplary embodiment, data processing system 100 includes graphics adapter 118 connected to system bus 106, receiving user interface information for display 120.

[0024] Also connected to system bus 106 is system memory 108 and input/output (I/O) bus bridge 110. I/O bus bridge 110 couples I/O bus 112 to system bus 106, relaying and/or transforming data transactions from one bus to the other. Peripheral devices such as nonvolatile storage 114, which may be a hard disk drive, and keyboard/pointing device 116, which may include a conventional mouse, a trackball, or the like, are connected to I/O bus 112.

[0025] The exemplary embodiment shown in FIG. 1 is provided solely for the purposes of explaining the invention and those skilled in the art will recognize that numerous variations are possible, both in form and function. For instance, data processing system 100 might also include a compact disk read-only memory (CD-ROM) or digital video disk (DVD) drive, a sound card and audio speakers, and numerous other optional components. All such variations are believed to be within the spirit and scope of the present invention. Data processing system 100 and the Java implementation examples below are provided solely as examples for the purposes of explanation and are not intended to imply architectural limitations. Those skilled in the art will recognize the numerous programming languages which may be utilized, all of which are believed to be embraced within the spirit and scope of the invention.

[0026] Referring to FIG. 2, a diagram of a multi-field text string class employed in encapsulating transliteration and/or phonetic spelling information in accordance with a preferred embodiment of the present invention is depicted. A fundamental problem in multinational computing environ-ments which need to display data in multiple human languages is that a spoken word generally encapsulates information in multiple aspects or attributes, such as through the word's meaning, from context, and/or from inflection. When reduced to a visual or electronic representation for manipulation or display in a data processing system, the word may lose some attributes and much of the associated meaning. Most importantly for data processing systems, a visual representation of a word may give no clues as to the correct translation or pronunciation of the word or the proper placement of a word within a specified sort order. International String (“IString”) class 202 may be employed to address this problem.

[0027] IString class 202 is preferably a Java class similar to the Java String class, which behaves like the String class by including similar methods. Most of the original behavior of the String class should be preserved, with additional functionality added and utilized only as needed. IString class 202 is a datatype which captures some of the meaning of spoken words which is normally lost when the word is reduced to a visual representation. IString class 202 is preferably utilized for all object names and system messages within a system.

[0028] The IString class 202 structure includes three different strings for each name, message, data, or text object: a baseString 204, a sortString 206, and an altString 208. BaseString 204 is the string within IString class 202 employed by default in the user interface display and may contain any text, usually the original text entered by the user in the local language where the IString object is created. SortString 206 may also be any text and is employed to allow correct sorting of non-phonetic languages and languages which are difficult to sort based only on the binary value of baseString 204. AltString 208 may be any text but should conventionally be filled with a latin character set representation of the pronunciation of the data contained in baseString 204. Thus, IString class 202 includes the original text (baseString 204), a sort key (sortString 206), and a pronunciation key (altString 208) for object names, system messages, and other data.

[0029] When implemented in Java, a constructor for an IString class 202 object may be composed of the following fields:

[0030]


/** The base text String */
protected String baseString;
/** The related text String for proper collation */
protected String sortString;
/** The related alternate text String (pronunciation key) */
protected String altString;
/** The source locale, as an ISO-3166 code; used for collation */
protected String sourceLocale;
/** The source language, as an ISO-639 code */
protected String sourceLanguage;
/** The source variant defined for EBCIDIC and case mapping */
protected String sourceVariant;
/** The target locale, as an ISO-3166 code */
protected String targetLocale;
/** The target language, as an ISO-639 code */
protected String targetLanguage;
/** The target variant defined for EBCIDIC and case mapping */
protected String targetVariant;

Complete listings of the upper-case, two letter ISO Country Codes defined by ISO-3166 and the lower-case, two letter ISO Language Codes defined by ISO-639 are readily available from a variety of sources on the Internet.

[0031] Table I illustrates how data within the IString data type 202 looks when represented as a table:

[0032]

TABLE I

Field	Type	Data

baseString	Java String	The user's text
sortString	Java String	Language/locale dependent
altString	Java String	Language/locale dependent
sourceLocale	Java String	ISO-3166 code, example “US”
sourceLanguage	Java String	ISO-639 code, example “en”
sourceVariant	Java String	Variant code
targetLocale	Java String	ISO-3166 code, example “JP”
targetLanguage	Java String	ISO-639 code, example “ja”
targetVariant	Java String	Variant code

[0033] A Java constructor for a new, empty IString class object 202 where the contents are independent of language or locale may be:

[0034]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Allocate a new IString containing no characters in the default
* locale.</p>
*
***************************************************
public IString( ) {
	this.baseString = new String( );
	this.sortString = new String( );
	this.altString = new String( );
	init( );
	}

[0035] To allow objects of the IString class 202 datatype to be stored in an object Database (ODB), however, and to permit manipulation of IString data by Common Object Request Broker Architecture (CORBA) applications, an Interface Definition Language (IDL) class should be defined:

[0036]


struct IString{
string baseString;	//base test String
string sortString;	//related text String for collation
string altString;	//related alternate text String (pronunciation)
string sourceLocale;	//source locale as an ISO-3166 code
string sourceLanguage;	//source language as an ISO-639 code
string sourceVariant;	//source variant code
string targetLocale;	//target locale as an ISO-3166 code
string targetLanguage;	//target language as an ISO-639 code
string targetVariant;	//target variant code
}

[0037] The contents of baseString 204, sortString 206, and altString 208 are preferably but not necessarily Unicode text entered by data entry methods 210 within IString class 202. Data entry methods 210, and thus the contents of baseString 204, sortString 206, and altString 208, may depend at least in part on language and locale parameters defined by sourceLocale field 212, sourceLanguage field 214, targetLocale field 216, and targetLanguage 218.

[0038] Because data entry methods 210 are dependent on the locale and/or langauge employed by the underlying host system, creation of a new IString object 202 preferably results in the locale and language properties of the host system in which the IString object 202 is created being placed in sourceLocale field 212 and sourceLanguage field 214. A constructor for allocating a new, empty IString for a specified locale and language determined from the host system in which the IString class object 202 is being created may be:

[0039]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Allocate a new IString containing no characters in the
* specified locale.</p>
*
***************************************************
public IString(Locale loc) {
	this.baseString = new String( );
	this.sortString = new String( );
	this.altString = new String( );
	this.sourceLocale = loc.getLocale( );
	this.sourceLanguage = loc.getLanguage( );
	init( );
	}

[0040] Input of data into an IString class 202 object is preferably locale- or language-dependent. The source-Language and targetLanguage properties 214 and 218 control how data is input into an IString class object 202 by data input methods 210. The sourceLanguage property 214 may be set to the language property of the host system on which the IString class object is created. The targetLanguage property 218 may also be set to that language, or may alternatively be set to a common, “universal” language such as English. Data input methods 210 compare sourceLanguage and targetlanguage properties 214 and 218 to determine what is entered into baseString 204, sortString 206, and altString 208 in an IString class object 202.

[0041] Character strings are entered into the baseString 204, sortString 206, and altString 208 fields by data input methods 220 for IString class 202, which may selectively utilize data from either the user's direct entry or specification, from transliteration engine 220, or from the Input Method Editor (IME) 224. Where the targetLanguage property 218 is set to English as a default, data entry methods 210 determine the contents of baseString 204, sortString 206, and altString 208 fields based upon the character set employed by the language in which data is entered by the user (sourceLanguage property 214).

[0042] For languages which employ the latin character set, the user input is placed by data entry methods 220 into all three fields (baseString 204, sortString 206, and altString 208) of the IString class 202 by data entry methods 210. A suitable constructor may be:

[0043]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Allocate a new IString which contains the same sequence of
* characters as the string argument in the specified locale.</p>
*
***************************************************
public IString(String str, Locale loc) {
	this.baseString = new String(str);
	this.sortString = new String(str);
	this.altString = new String(str);
	this.sourceLocale = loc.getLocale( );
	this.sourceLanguage = loc.getLanguage( );
	init( );
	}

For most locales and languages, the entered string will be input into all three fields of the IString object 202. If targetLanguage property 218 were not set to English, data entry methods 224 would input the user-entered text into all three fields whenever the languages identified in source-Language and targetLanguage properties 214 and 218 employ a common character set (e.g., both employ latin characters, as in the case of Spanish and Afrikaans).

[0044] Table II illustrates how data is entered into IString class 202 fields where the host language and locale utilize the latin character set.

[0045]

TABLE II

Field	Type	Data

baseString	Java String	Hetherington
sortString	Java String	Hetherington
altString	Java String	Hetherington
sourceLocale	Java String	US
sourceLanguage	Java String	en
targetLocale	Java String	US
targetLanguage	Java String	en

If desired, the fields may be individually edited and the object artificially promoted for sorting purposes by inserting a string having a lower sort value (e.g., “AAA_Hetherington”) into sortString 206.

[0046] For languages which do not employ the latin character set, but which utilize a character set which may be sound mapped to the latin character set, the user input is entered by data entry methods 210 into baseString 204 and sortString 206, but a transliterated, phonetic representation of the input is placed in altString 208. An internal method within the transliteration engine 220 is employed to sound-map the passed string to a phonetic, latin character representation for altString 208 to transliterate entered characters into other characters understandable to people who are not familiar with the character set of the original language.

[0047] To generate the contents of altString 208, transliteration engine 220 selects an appropriate Java resource file 222 containing a mapping table to create the alternate text to be placed in altString 208. The selection of the particular resource file which is employed based on the combination of source and target languages. Java resource files 222 are named for the combination of languages for which the mapping is being performed. In the example shown in FIG. 2, ru_en.class is for mapping Russian (Cyrillic characters) to English (Latin characters). The structure of resource file 222 is a table with associated entries for foreign language characters and corresponding latin characters.

[0048] A suitable constructor for an IString object in which altString 208 is transliterated from the passed string may be:

[0049]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Allocate a new IString. The baseString and sortString are the
* passed string, the altString is transliterated into the target
* language.</p>
*
***************************************************
public IString(String str) {
	this.baseString = new String(str);
	this.sortString = new String(str);
	if(isSameLanguage(( )
	this.altString = new String(str);
	else
	this.altString = transmogrify(str,
	this.sourceLanguage,
	this.targetLanguage);
	}

The “transmogrify” method is the internal method within transliteration engine 220 which was described above. The character set into which the entered characters are transliterated is determined from the targetLanguage property 218, which in the exemplary embodiment is assumed to be set to English. Given an appropriate resource file 222, however, characters may be transliterated between any two languages for which characters in one language sound-map to one or more characters in the other.

[0050] Table III illustrates how data is entered into IString class 202 by data entry methods 210 where the language utilizes a non-latin character set which maps to the latin character set, such as Russian Cyrillic.

[0051]

TABLE III

Field	Type	Data

baseString	Java String
sortString	Java String
altString	Java String	David Kumhyr
sourceLocale	Java String	RU
sourceLanguage	Java String	ru
targetLocale	Java String	US
targetLanguage	Java String	en

In the example shown, the text entered by the user is inserted into both baseString 204 and sortString 206, but the text entered into altString 208 is selected by transliteration engine 220 utilizing a resource table of Russian Cyrillic to English character sound mappings. The phonetic representation of the baseString 204 is thus entered into altString 208 as a pronunciation key for users unfamiliar with the Cyrillic character set.

[0052] For languages which do not employ the latin character set or a character set which may be sound-mapped to the latin character set, data entry methods 210 input data into the baseString 204, sortString 206, and altString 208 fields which is derived from the input method editor (IME) 224. IME 224 may be either a customized input method editor or the input method editor which is integrated into Asian versions of the Windows NT operating system available from Microsoft Corporation of Redmond Wash. If the Windows NT input method editor is employed, the appropriate data must be extracted from the Windows NT input method editor internal data storage.

[0053] Table IV illustrates how data is entered into IString class 202 by data entry methods 210 for logosyllabic languages, such as Japanese, which employ neither the latin character set nor a character set which may be sound-mapped to the latin character set.

[0054]

TABLE IV

Field	Type	Data

baseString	Java String	<Kanji>
sortString	Java String
altString	Java String	hayashi
sourceLocale	Java String	JP
sourceLanguage	Java String	ja
targetLocale	Java String	US
targetLanguage	Java String	en

@

Logosyllabic languages do not have alphabets, but instead have very large character sets with symbols (“ideographs”) corresponding to concepts and objects rather than simple sounds. For instance, the Joyo Kanji List (Kanji for Daily Use) adopted for the Japanese language in 1981 includes 1945 symbols. Normal computer keyboards cannot contain enough separate keys to have one for each symbol in the language, so input is accomplished phonetically utilizing keystroke combinations to select characters from one of two phonetic syllabaries, hiragana or katakana, and dictionary lookup for Kanji symbol creation. The process is implemented in the Windows NT input method editor identified above.

[0055] For logosyllabic or ideograhic languages, therefore, the data entered into altString 208 is the latin characters typed by the user to compose the desired ideograph. The data entered into sortString 206 are the syllabary characters phonetically spelling the desired ideograph, providing an intermediate representation of the ideograph. The data entered into baseString 204 is the final ideograph selected by the user. As with transliteration of non-latin characters as described above, non-latin characters may be entered into altString 208 if the targetLanguage property is set to a language other than English and IME 224 supports composition of the ideographs by phonetic spelling in a language other than English. For instance, an IString object 202 might contain Japanese Kanji in baseString 204, hiragana in sortString 206, and Cyrillic characters in altString 208 if IME 224 permits composition of Japanese Kanji characters by phonetic spelling in Russian.

[0056] A suitable constructor for receiving baseString 204, sortString 206 and altString 208 from IME 224 via data entry methods 210 for entry into an IString object 202 may be:

[0057]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Allocate a new IString. The baseString, sortString and
* altString are entered from the IME utilizing the default language and
* locale.</p>
*
***************************************************
public IString(String base,
	String sort,
	String alt,
	Locale src,
	Locale tgt) {
	this.baseString = base;
	this.sortString = sort;
	this.altString = alt;
	this.sourceLocale = src.getLocale( );
	this.sourceLanguage = src.getLanguage( );
	this.targetLocale = tgt.getLocale( );
	this.targetLanguage = tgt.getLanguage( );
	init( );
	}

The contents of baseString 204, sortString 206 and altString 208 are entered into the respective fields from data derived from IME 224, while the contents of sourceLocale 212 and sourceLanguage 214 are entered from the default locale and language properties specified by the host system in which data is being entered into IString object 202. The contents of targetLocale 216 and targetLanguage 218 will typically be a locale/language code for a language utilizing the latin character set such as “en_US” (English—United States).

[0058] Regardless of the language in which text is entered into an IString class object 202, the data automatically entered into each of the baseString 204, altString 206, and sortString 208 by data entry methods 210 may be overridden or altered using other methods. The fields of an IString object 202 may preferably be individually and independently edited, allowing artificial promotion within sortString field 206 as described above, replacement of an erroneously selected ideograph in baseString field 204, or correction of a phonetic spelling within altString field 208.

[0059] While the above-described methods assumed that the source and target languages were taken from host system defaults, data may alternatively be entered into baseString 204, sortString 206 and altString 208 for specified source and target languages utilizing the constructor:

[0060]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Allocate a new IString. The baseString, sortString and
* altString are entered from the IME for specified target and source
* language and locale.</p>
*
***************************************************
public IString(String base,
	String sort,
	String alt,
	String srcLanguage,
	String srcLocale,
	String tgtLanguage,
	String tgtLocale) {
	this.baseString = base;
	this.sortString = sort;
	this.altString = alt;
	this.sourceLocale = srcLocale;
	this.sourceLanguage = srcLanguage;
	this.targetLocale = tgtLocale;
	this.targetLanguage = tgtLanguage;
	init( );
	}

In this constructor, the source and target language and locale which are employed to select the characters entered into baseString 204, sortString 206 and altString 208 may be specified. This latter constructor may be employed to create an IString object 202 in other than the host system default language, or in host systems where data for the IString object 202 is received from another system and a local instance is created.

[0061] It should be noted that transliteration engine 220 and messaging methods 226 need not necessarily be implemented within an IString class 202 as depicted in FIG. 2, and that IME method 224 need not be implemented separately. Transliteration engine 220 and messaging methods 226 may instead be implemented within separate subclasses which are appropriately constructed and/or invoked by IString class 202 as necessary, while IME 224 may be implemented as a method within IString class 202.

[0062] Transliteration engine 220 and IME 224 and are only required by data entry methods 210 to gather input data for IString class 202 objects under certain locale and language property settings. Otherwise, data may be programmatically input into baseString 204, sortString 206, and altString 208 by invoking the proper constructor. The methods which may be invoked by programs at runtime to programmatically get and set fields within IString 202 include:

[0063]


	/***************************************************
	*
	* <P> </P>
	*
	* <dt> <b>Description:</b> <dd>
	* <p> Get the IString baseString.</p>
	*
	* @returns str String containing the base string
	*
	***************************************************
	public String getBaseString( ) {
	return this.baseString;
	}

This method returns the contents for baseString 204 for an IString object 202. Similar methods return the contents of sortString 206 and altString 208:

[0064]


	/***************************************************
	*
	* <P> </P>
	*
	* <dt> <b>Description:</b> <dd>
	* <p> Get the IString sortString.</p>
	*
	* @returns str String containing the sort string
	*
	***************************************************
	public String getSortString( ) {
	return this.sortString;
	}
	/***************************************************
	*
	* <P> </P>
	*
	* <dt> <b>Description:</b> <dd>
	* <p> Get the IString altString.</p>
	*
	* @returns str String containing the alt string
	*
	***************************************************
	public String getAltString( ) {
	return this.altString;
	}

The methods also include setting baseString 204:

[0065]


	/***************************************************
	*
	* <P> </P>
	*
	* <dt> <b>Description:</b> <dd>
	* <p> Set the IString baseString.</p>
	*
	* @param str String containing the base string
	*
	***************************************************
	public void setBaseString(String sBase) {
	this.baseString = sBase;
	}

as well as sortString 206 and altString 208:

[0066]


	/***************************************************
	*
	* <P> </P>
	*
	* <dt> <b>Description:</b> <dd>
	* <p> Set the IString sortString.</p>
	*
	* @param str String containing the sort string
	*
	***************************************************
	public void setSortString(String sSrt) {
	this.sortString = sSrt;
	}
	/***************************************************
	*
	* <P> </P>
	*
	* <dt> <b>Description:</b> <dd>
	* <p> Set the IString altString.</p>
	*
	* @param str String containing the alt string
	*
	***************************************************
	public void setAltString(String sAlt) {
	this.altString = sAlt;
	}

[0067] In addition to getting and setting baseString 204, sortString 206, and altString 208 for an IString object 202, programs may need to get or set the display locale or language of an IString object 202. Accordingly, other methods are provided to permit a program to get and/or set the locale or language properties of IString data:

[0068]


/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Get the locale of the IString data.<p>
*
* @returns loc Locale containing the locale of the data
*
***************************************************
public Locale getLocale( ) {
	Locale loc = new Locale(this.sourceLanguage, this.sourceLocale);
	return loc;
	}
/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Set the locale of the IString data.</p>
*
* @param loc Locale of the data
*
***************************************************
public void setLocale(Locale loc) {
	this.sourceLocale = loc.getLocale( );
	this.sourceLanguage = loc.getLanguage( );
	}
/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Get the display language of the IString data.</p>
*
* @returns Display language of the data
*
***************************************************
public String getDisplayLanguage( ) {
	Locale loc = new Locale(this.sourceLanguage, this.sourceLocale);
	return loc.getDisplayLanguage( );
	}
/***************************************************
*
* <P> </P>
*
* <dt> <b>Description:</b> <dd>
* <p> Get the display locale of the IString data.</p>
*
* @returns Display locale of the data
*
***************************************************
public String getDisplayLocale( ) {
	if(this.sourceLanguage = = null&&this.sourceLocale = = null)
	return null;
	else{
	Locale loc = new Locale(this.sourceLanguage, this.sourceLocale);
	return loc.getDisplayLocale( );
	}
	}

While these methods are available, IString class 202 preferably exhibits a “black box” behavior such that the programmer/user need not know anything about the methods implemented for IString class 202. IString class 202 simply appears as a data type which encapsulates extra information about baseString 204 and also includes some methods for transforming characters from one character set to another. For special cases where the sortString field 206 or altString field 208 are to be exposed to the user in addition to or in lieu of baseString 204, either for editing or for display only, a separate set of controls may be provided.

[0069] In the present invention, IString class 202 is employed to effectively transfer human language data across systems employing incongruous languages. The contents of baseString 204 provide a native representation of the text in the default language of the system originating the IString object 202. However, for each system participating in the exchange of data with other systems running in different human languages, the targetLocale property 216 and targetLanguage 218 property of an IString object 202 are preferably set to a common value (e.g., targetLocale=“US”, targetLanguage=“en”). The contents of altString 208 will thus contain a common, cross-language representation of the text string. In systems where the default language of a system receiving an object differs from the language of the contents of baseString 204, IString class object 202 may automatically switch to presenting the contents of altString 208 as the text string to be displayed or processed.

[0070] Referring to FIG. 3, a high level flowchart for a process of entering data into a multi-field text string class in accordance with a preferred embodiment of the present invention is depicted. FIG. 3 is intended to be read in conjunction with FIG. 2. The process shown in FIG. 3 begins at step 302, which depicts initiation of data entry into a multi-field text string class (IString) object 202. The process then passes to step 304, which illustrates a determination of whether the currently selected language, specified by the operating system or application environment language and/or locale properties, employs the latin alphabet character set. Languages supported by a given system may be categorized to facilitate this determination, and the category employing the latin alphabet should include English and the romance languages (Spanish, French, Italian, etc.). If the current language employs the latin alphabet character set, the process proceeds to step 306, which depicts inserting the text entered by the data entry keystrokes into all three fields—baseString 204, sortString 206, and altString 208—of IString object 202. Thus, in most locales and/or languages for a locale, data is input programmatically by invoking the appropriate constructor and the baseString text is inserted into the other two fields by default.

[0071] Referring back to step 304, if the currently-selected language for data entry into the IString object does not utilize the latin alphabet character set, the process proceeds instead to step 308, which illustrates a determination of whether the currently selected language maps to the latin alphabet character set. This category of languages will most likely include, for example, Cyrillic, Greek, Hebrew, and many Germanic and Arabic languages. If so, the process proceeds to step 310, which depicts storing the text of the data entry keystrokes into the baseString and sortString fields 204 and 206, and then to step 212, which illustrates storing the entered text sound-mapped to latin alphabet characters in the altString field 208.

[0072] It should be noted that there may be some overlap between the first an second categories of languages, or—stated differently—some language-dependent variation in the manner in which language entry is handled. For example, for Spanish text, while most characters may be entered directly into all three fields of an IString class object, the “ñ”character may be sound mapped to “ny” in the altString field of an IString object to provide information regarding proper pronunciation. Alternatively, the altString field may be filled with a traditional phonetic pronunciation guide to the data entered into the IString object (e.g., “küm-er” or “koo-mer”) to provide pronunciation information for words in languages employing the latin alphabet character set as well as for ideographs.

[0073] Referring back to step 308, if the current language does not map readily to the latin alphabet character set (e.g., the language employs an ideographic character set), the process proceeds instead to step 314, which depicts storing the data entry keystrokes in the altString field 208 as a pronunciation guide, then to step 316, which illustrates storing intermediate characters (such as hiragana or katakana characters) in the sortString field 206, and finally to step 318, which depicts storing the ideograph in the baseString field 204. Steps 314, 316 and 318 illustrates the operation of the IME in storing data in an IString object.

[0074] From any of steps 306, 312, or 318, the process proceeds to step 320, which illustrates the process becoming idle until data entry to an IString class object is again initiated. The distinct data entry behavior of the IString class based on the locale or language property allows language specific characters to be automatically mapped to recognizable characters and saved as a pronunciation key. A user may thus view the character-mapped representation of an abstract object name to be able to recognize a specific object, despite a lack of familiarity with the character set in which the object name text string was entered.

[0075] Referring to FIGS. 4A and 4B, portions of a user interface showing one application for character-mapped data entry into alternate fields of a multi-field text string class in accordance with a preferred embodiment of the present invention are illustrated. The user interface display an IString object in which entered text was saved in the baseString field and transliterated characters for the entered text was automatically saved in the altString 208 field as described above.

[0076] In FIG. 4A, the baseString field contents (“ custom character

”) is displayed. A user unfamiliar with the Cyrillic character set would not be able to recognize this name. However, by altering the user interface so that the altString field contents (“David Kumhyr”) is displayed as shown in FIG. 4B, the user can recognize the name of an object which they wish to manipulate. The automatically transliterated characters saved in the altString field provide a recognizable representation of the text string, as well as a pronunciation key.

[0077] With reference now to FIG. 5 and FIGS. 6A through 6G, a high level flowchart and corresponding user interface displays for data entry in a logosyllabic language into a multi-field text string class in accordance with a preferred embodiment of the present invention are depicted. FIGS. 5 and 6A–6G are intended to be read in conjunction with each other and with FIG. 2, and depict the process of IME 224 in generating the contents of baseString 204, sortString 206, and altString 208 for an ideographic (or logosyllabic) language as described in connection with steps 314, 316, and 318 of FIG. 3.

[0078] For Japanese and similar logosyllabic languages, IME 224 monitors the keystrokes entered, selecting appropriate hiragana (or katakana) characters, and finally presents a list of possible matching Kanji symbols. The process begins at step 502, which illustrates data entry being initiated with the language selected not mapping to the latin alphabet character set. The process may thus be performed between steps 308 and 314 depicted in FIG. 3. From step 502, the process first passes to step 504, which illustrates a determination of whether a character has been entered by the user. Any character entry should be in latin alphabet characters, even for logosyllabic languages. As noted earlier, data input for such languages is accomplished phonetically utilizing combinations of latin alphabet characters to select symbols from phonetic syllabaries, with a dictionary lookup for the final ideograph.

[0079] If no character was entered, the process proceeds from step 504 back to step 504, to continue polling for character entry. If a character is entered, however, the process proceeds instead to step 506, which depicts adding the entered character into altString 208. The process then passes to step 508, which illustrates a determination of whether the entered character, together with any previously entered characters which have not yet been mapped to a syllabary symbol, corresponds to a syllabary symbol. If not, the process returns to step 504 to await further character input. If so, however, the process proceeds instead to step 510, which depicts adding the syllabary symbol corresponding to the entered character(s) to altString field 206.

[0080] From step 510, the process then passes to step 512, which illustrates a determination of whether the entered character, together with any previously entered characters which have not yet been mapped to an ideograph, corresponds to an ideograph. If not, the process returns to step 504 to await further character input. If so, however, the process proceeds instead to step 514, which depicts presenting the (potentially) matching ideograph or ideographs to the user for selection, then adding the selected ideograph to baseString 204. The process then returns to step 504 to await further input, and continues as described until interrupted by a control indicating the data entry is completed or terminated. Those skilled in the art will recognize that some mechanism should be provided for prevented termination of data entry when latin alphabet characters entered to phonetically compose an ideograph do not correspond to any available ideograph in the dictionary.

[0081] A specific example of data entry utilizing IME 224 is illustrated for the data in Table III by FIGS. 6A through 6G. In composing the word “hayashi,” the user would first enter “h”. This is not a valid hiragana character, so IME 224 will display the “h” as shown in FIG. 6A, add the “h” to the altString filed 208, and wait for the next character to be entered. The user next enters “a”, forming the phoneme “ha”, for which IME 224 may temporarily display “ha”, then select and display “ custom character

” in lieu of “ha”. Alternatively, IME 224 may simply select and display “ custom character

” in lieu of “h” as shown in FIG. 6B. IME 224 also adds the “a” to the altString field 208 and adds “ custom character

” to sortString field 206.

[0082] Similarly, upon entry of “y” by the user, IME 224 displays the “y” as shown in FIG. 6C and adds that character to altString 208; upon entry of “a”, IME 224 selects and displays “ custom character

” in place of the “y” as shown in FIG. 6D, then adds “a” to altString 208 and “ custom character

” to sortString 206. Following user entry of “s”, IME 224 adds the character to altString 208 and displays the character as shown in FIG. 6E; when the user subsequently enters “h”, IME 224 adds the character to altString 208 and displays the character as shown in FIG. 6F.

[0083] Finally, upon user entry of “i”, which causes the entered text to correspond to a phonetic spelling of a Kanji character, IME 224 adds “i” to altString 208 and selects and adds “ custom character

” to sortString 206. As each latin character is entered by the user and added to altString 208, or alternatively as each hiragana/katakana syllabary symbol is selected and added to sortString 206, IME 224 checks the lookup dictionary for possible Kanji symbols corresponding to the phonetic pronunciation entered. Upon determining a match, IME 224 presents a list to the user for selection as shown in FIG. 6G. The user selection is subsequently entered into baseString 204.

[0084] Filtering input to IString object 202 through IME 224, which may form a portion of the operating system, the application environment, or an editor, allows intermediate and alternative representations of a name or word to be captured along with the final form. This is particularly important for logosyllabic languages using ideographs, which are especially difficult to deal with for non-speakers of that language. Describing an ideograph over the telephone for assistance in determining meaning can be extremely challenging, a task further complicated where the same ideograph has multiple meanings or pronunciations. For instance, many Kanji symbols have multiple pronunciations and/or meanings. Therefore, merely seeing the characters does not provide enough information to know how to pronounce the name, which has resulted in the Japanese business card ritual of presented the card and pronouncing the name at the same time. Capturing intermediate representations within IString object 202 allows non-speakers to read and know how to pronounce or match ideographic characters.

[0085] It is important to note that while the present invention has been described in the context of a fully functional data processing system and/or network, those skilled in the art will appreciate that the mechanism of the present invention is capable of being distributed in the form of a computer usable medium of instructions in a variety of forms, and that the present invention applies equally regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of computer usable mediums include: nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), recordable type mediums such as floppy disks, hard disk drives and CD-ROMs, and transmission type mediums such as digital and analog communication links.

[0086] While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.

Claims

What is claimed is:

1. A text string data structure within a computer usable medium, comprising:

a multi-field text string object encapsulating a plurality of discrete fields;

a first field within the multi-field text string object containing a first character string representing a word;

a second field within the multi-field text string object containing a second character string representing the word; and

a third field within the multi-field text string object containing a third character string representing the word; wherein

the first character string contains characters for a first human language; and

the third character string contains the first character string prefixed by at least one character with a low sort value.

2. The text string data structure of claim 1, wherein the second character string is different from the first character string.

3. The text string data structure of claim 1, wherein the first character string contains characters from a first character set employed by a first human language and the second character string contains characters from a second character set employed by a second human language.

4. The text string data structure of claim 1, wherein the first character string contains characters for a first human language and the second character string contains characters for a second human language which sound-map to characters within the first character string.

5. The text string data structure of claim 1, wherein the first character sing contains an ideograph and the second character string contains a phonetic spelling of the ideograph.

6. The text string data structure of claim 1, wherein the third character string is different from the second character string.

7. The text string data structure of claim 6, wherein the third character string is different from the first character string.

8. The text string data structure of claim 1, wherein:

the first character string contains characters for a first human language;

the second character string contain characters for a second human language which sound-map to characters within the first character sting; and

the third character string is identical to the first character string.

9. The text string data structure of claim 1, wherein:

the first character string contains an ideograph;

the second character string contains Latin characters for a phonetic spelling of the ideograph; and

the third character string contains syllabary characters for a phonetic spelling of the ideograph.

10. A method of encapsulating information in a text string data structure, comprising:

creating a multi-field text string object encapsulating a plurality of discrete fields;

storing a first character string representing a word in a first field within the multi-field text string object;

storing a second character string representing the word in a second field within the multi-field text string object;

storing a third character string representing the word in a third field within the multi-field text sting object; and

storing the first character string prefixed by at least one character with a low sort value as the third character string.

11. The method of claim 10, wherein the step of storing a second character string representing the word in a second field within the multi-field text string object further comprises:

if the first character string contains characters from a first character set employed by a first human language, storing characters from a second character set employed by a second human language in the second field, wherein the second character string is different from the first character string.

12. The method of claim 10, further comprising:

storing characters from a first human language as the first character string;

storing characters from a second human language which sound-map to characters within the first character string as the second character string; and

storing characters identical to the first character string as the third character string.

13. The method of claim 10, further comprising:

storing an ideograph as the first character string;

storing a Latin character phonetic spelling of the ideographs as the second character string; and

storing syllabary characters for a phonetic spelling of the ideograph as the third character string.

14. The method of claim 10, further comprising:

storing identical characters as the first, second, and third character strings.

15. A system for encapsulating information in a text string data structure, comprising:

means for creating a multi-field text string object encapsulating a plurality of discrete fields;

means for storing a first character string representing a word in a first field within the multi-field text string object;

means for storing a second charter string representing the word in a second field within the multi-field text string object;

means for storing a third character string representing the word in a third field within the multi-field text string object]; and

means for storing the first character string prefixed by at least one character with a low sort value as the third character string.

16. The system of claim 15, wherein the means for storing a second character string representing the word in a second field within the multi-field text string object further comprises:

means, if the first character string contains characters from a first character set employed by a first human language, for storing characters from a second character set employed by a second human language in the second field, wherein the second character string is different from the first character string.

17. The system of claim 15, further comprising:

means for storing characters from a first human language as the first character string;

means for storing characters from a second human language which sound-map to characters within the first character string as the second character string; and

means for storing characters identical to the first character string as the third character string.

18. The system of claim 15, further comprising:

means for storing an ideograph as the first character string;

means for storing a Latin character phonetic spelling of the ideograph as the second character string; and

means for storing syllabary characters for a phonetic spelling of the ideograph as the third character string.

19. The system of claim 15, further comprising:

means for storing identical characters as the first, second, and third character stings.

Patent Citations (107)

Patent	Date	Inventor	Cited By
US4379288(A)	1983-04-01	Leung et al.	Applicant
US4384329(A)	1983-05-01	Rosenbaum et al.	Applicant
US4544276(A)	1985-10-01	Horodeck	Applicant
US4611280(A)	1986-09-01	Linderman	Applicant
US4615002(A)	1986-09-01	Innes	Applicant
US4641264(A)	1987-02-01	Nitta et al.	Examiner
US4706212(A)	1987-11-01	Toma	Examiner
US4730270(A)	1988-03-01	Okajima et al.	Applicant
US4737040(A)	1988-04-01	Moon	Applicant
US4951202(A)	1990-08-01	Yan	Applicant
US4954984(A)	1990-09-01	Kaijima et al.	Applicant
US4962452(A)	1990-10-01	Nogami et al.	Applicant
US5040218(A)	1991-08-01	Vitale et al.	Applicant
US5056021(A)	1991-10-01	Ausborn	Examiner
US5091878(A)	1992-02-01	Nagasawa et al.	Applicant
US5109352(A)	1992-04-01	O'Dell	Applicant
US5136503(A)	1992-08-01	Takagi et al.	Applicant
US5146587(A)	1992-09-01	Francisco	Applicant
US5164900(A)	1992-11-01	Bernath	Applicant
US5175803(A)	1992-12-01	Yeh	Applicant
US5214583(A)	1993-05-01	Miike et al.	Applicant
US5243519(A)	1993-09-01	Andrews et al.	Applicant
US5251130(A)	1993-10-01	Andrews et al.	Applicant
US5268990(A)	1993-12-01	Cohen et al.	Applicant
US5307267(A)	1994-04-01	Yang	Applicant
US5339433(A)	1994-08-01	Frid-Nielsen	Applicant
US5371844(A)	1994-12-01	Andrew et al.	Applicant
US5377317(A)	1994-12-01	Bates et al.	Applicant
US5384700(A)	1995-01-01	Lim et al.	Applicant
US5390295(A)	1995-02-01	Bates et al.	Applicant
US5416903(A)	1995-05-01	Malcolm	Applicant
US5418718(A)	1995-05-01	Lim et al.	Applicant
US5420976(A)	1995-05-01	Schell et al.	Applicant
US5426583(A)	1995-06-01	Uribe-Echebarria Diaz De Mendibil	Applicant
US5432948(A)	1995-07-01	Davis et al.	Applicant
US5434776(A)	1995-07-01	Jain	Applicant
US5434777(A)	1995-07-01	Luciw	Examiner
US5440482(A)	1995-08-01	Davis	Applicant
US5448474(A)	1995-09-01	Zamora	Applicant
US5485373(A)	1996-01-01	Davis et al.	Applicant
US5490061(A)	1996-02-01	Tolin et al.	Applicant
US5523946(A)	1996-06-01	Kaplan et al.	Examiner
US5546575(A)	1996-08-01	Potter et al.	Applicant
US5550965(A)	1996-08-01	Gabbe et al.	Applicant
US5583761(A)	1996-12-01	Chou	Applicant
US5594642(A)	1997-01-01	Collins et al.	Applicant
US5600779(A)	1997-02-01	Palmer et al.	Applicant
US5613122(A)	1997-03-01	Burnard et al.	Applicant
US5640581(A)	1997-06-01	Saraki	Applicant
US5640587(A)	1997-06-01	Davis et al.	Applicant
US5642490(A)	1997-06-01	Morgan et al.	Applicant
US5644775(A)	1997-07-01	Thompson et al.	Applicant
US5649223(A)	1997-07-01	Freeman	Applicant
US5652884(A)	1997-07-01	Palevich	Applicant
US5675818(A)	1997-10-01	Kennedy	Applicant
US5677835(A)	1997-10-01	Carbonell et al.	Applicant
US5678039(A)	1997-10-01	Hinks et al.	Applicant
US5682158(A)	1997-10-01	Edberg et al.	Applicant
US5721825(A)	1998-02-01	Lawson et al.	Applicant
US5724593(A)	1998-03-01	Hargrave, III et al.	Applicant
US5734887(A)	1998-03-01	Kingberg et al.	Applicant
US5758295(A)	1998-05-01	Ahlberg et al.	Applicant
US5758314(A)	1998-05-01	McKenna	Applicant
US5778356(A)	1998-07-01	Heiny	Applicant
US5784069(A)	1998-07-01	Daniels et al.	Applicant
US5784071(A)	1998-07-01	Tang et al.	Applicant
US5787452(A)	1998-07-01	McKenna	Applicant
US5790116(A)	1998-08-01	Malone et al.	Applicant
US5793381(A)	1998-08-01	Edberg et al.	Applicant
US5799303(A)	1998-08-01	Tsuchimura	Applicant
US5802539(A)	1998-09-01	Daniels et al.	Applicant
US5812122(A)	1998-09-01	Ng	Applicant
US5812964(A)	1998-09-01	Finger	Applicant
US5815148(A)	1998-09-01	Tanaka	Applicant
US5828992(A)	1998-10-01	Kusmierczyk	Applicant
US5832478(A)	1998-11-01	George	Applicant
US5844798(A)	1998-12-01	Uramoto	Examiner
US5870084(A)	1999-02-01	Kanungo et al.	Applicant
US5872973(A)	1999-02-01	Mitchell et al.	Applicant
US5873111(A)	1999-02-01	Edberg	Applicant
US5917484(A)	1999-06-01	Mullaney	Applicant
US5966637(A)	1999-10-01	Kanungo et al.	Applicant
US5974372(A)	1999-10-01	Barnes et al.	Applicant
US5978754(A)	1999-11-01	Kumano	Applicant
US5995101(A)	1999-11-01	Clark et al.	Applicant
US6003049(A)	1999-12-01	Chiang	Applicant
US6024571(A)	2000-02-01	Renegar	Examiner
US6028600(A)	2000-02-01	Rosin et al.	Applicant
US6047252(A)	2000-04-01	Kumano et al.	Applicant
US6078935(A)	2000-06-01	Nielsen	Applicant
US6092037(A)	2000-07-01	Stone et al.	Applicant
US6144377(A)	2000-11-01	Oppermann et al.	Applicant
US6167366(A)	2000-12-01	Johnson	Applicant
US6205418(B1)	2001-03-01	Li et al.	Examiner
US6219632(B1)	2001-04-01	Schumacher et al.	Applicant
US6229622(B1)	2001-05-01	Takeda	Applicant
US6252589(B1)	2001-06-01	Rettig et al.	Applicant
US6321191(B1)	2001-11-01	Kurahashi	Applicant
US6332148(B1)	2001-12-01	Paine et al.	Applicant
EP640913(A2)	1995-03-01		Applicant
JP57-199070	1982-12-01		Applicant
JP5-224687	1993-09-01		Applicant
JP7-261652	1995-10-01		Applicant
JP7-271793	1995-10-01		Applicant
JP9-62679	1997-03-01		Applicant
JP9-237270	1997-09-01		Applicant
WO97/404	1997-10-01		Applicant

Non-Patent Literature (14)

Baldwin, H., Object-Oriented Development: Multicultural C++ Tools Get Internationalization, Thread Safety. Open Systems Today, vol.-, No. 132, pp. 56 (reprinted), Sep. 1993.Applicant
U.S. Appl. No. 09/211,810, filed Dec. 15, 1998, Related Co-Pending Application, David J. Hetherington, et al.Applicant
U.S. Appl. No. 09/211,809, filed Dec. 15, 1998, Related Co-Pending Application, David J. Hetherington, et al.Applicant
U.S. Appl. No. 09/211,808, filed Dec. 15, 1998, Related Co-Pending Application, David J. Hetherington, et al.Applicant
U.S. Appl. No. 09/211,799, filed Dec. 15, 1998, Related Co-Pending Application, David J. Hetherington, et al.Applicant
U.S. Appl. No. 09/211,813, filed Dec. 15, 1998, Related Co-Pending Application, David J. Hetherington, et al.Applicant
U.S. Appl. No. 09/211,801, filed Dec. 15, 1998, Related.Co-Pending Application, David J. Hetherington, et al.Applicant
U.S. Appl. No. 09/211,812, filed Dec. 15, 1998, Related Co-Pending Application, David J. Hetherington, et al.Applicant
New Icons, Oct. 1996, IBM Technical Disclosure Bulletin, vol. 39, No. 10, pp. 25-27.Applicant
Intelligent Computer Keyboard for Entering Texts of Sinhalese and Other Similar Languages, Nov. 1992, IBM Technical Disclosure Bulletin, vol. 35, No. 6, pp. 24-27.Applicant
Enhanced Methods for Spelling Names in Speech Recognition Systems, Nov. 1995, IBM Technical Disclosure Bulletin, vol. 38, No. 11, pp. 45-46.Applicant
Method for Allowing Translation of Operator Input Comparison Strings in an Online Presentation Program, Jan. 1986, IBM Technical Disclosure Bulletin, vol. 28, No. 8, pp. 3682-3683.Applicant
Architecture for Speech Synthesis from Text Recognition Methods, Apr. 1994, IBM Technical Disclosure Bulletin, vol. 37, No. 04A, pp. 287-289.Applicant
Bridging Speech Recognition and Natural Language Processing Subsystems, Jan. 1996, IBM Technical Disclosure Bulletin, vol. 39, No. 01, pp. 229-231.Applicant