Embodiments of the present invention relate to the field of number conversion. More particularly, embodiments of the invention relate to the field of converting numbers expressed using digits to text and to converting digit characters to different digit characters.
Modern desktop operating systems are provided with various localization features for improving usability for users throughout the world. For instance, some desktop operating systems provide support for multiple user interface languages. Through this type of support for multiple user interface languages, users can configure the user interface of the operating system to operate in any of a number languages supported by the host operating system.
In addition to operating system support, many application programs also support the use of multiple languages for international users. For instance, a word processing program may allow a user to create documents in English, Thai, Vietnamese, or any other language installed in the operating system and enabled by the user. Documents may also be created that contain text or other information in a combination of languages. In fact, international users of such applications frequently create documents that include text in more than one language.
When creating foreign language documents, users may wish to express numbers using text (e.g. “one-hundred twenty three”) in the language of their target audience. However, if the user does not speak the language of their target audience, it may be difficult for the user to translate the number (e.g. “123”) into the target language. (e.g. “cent vingt-trois”). Moreover, when a user receives a foreign language document, the document may contain numbers expressed using digit shapes unfamiliar to the user. In this situation, it may also be very difficult for the user to convert the foreign language digit shapes to digit shapes that the user understands.
Therefore, in light of the above, there is a need for a method, system, and apparatus for easily converting numbers expressed using digit shapes to text in any of a number of languages. Moreover, there is a need for a method, system, and apparatus for converting numbers expressed using digit shapes to different digit shapes.
Embodiments of the present invention solve the above-described problems by providing a method, system, and apparatus for easily converting numbers expressed as digit shapes to text in a user-selected language. Moreover, embodiments of the present invention provide a method, system, and apparatus for converting numbers expressed using digit shapes to different digit shapes. Moreover, embodiments of the invention present conversion options to the user in a user-selected language and only present options for converting to text or digit shapes in languages that are enabled within a host application.
According to one actual embodiment of the present invention, a method is provided for converting a number expressed as digit shapes to text in a system for creating and editing an electronic document. According to this embodiment of the invention, software modules are executed in conjunction with a software application for creating and editing an electronic document that allow the convenient conversion of numbers expressed using digits to text. When a user types a string of text, such as a paragraph, the string is analyzed to determine whether the string of text includes a number expressed using digits (e.g. “123”). If the string of text includes a number expressed using digit shapes, the number is semantically labeled with schema information that indicates that the number may be converted to text.
Once a number expressed using digit shapes has been identified within a string of text, such as a paragraph, the application may display an indication to the user that the number has been semantically labeled. This indication also identifies to the user that actions may be performed on the number. When a selection is received of the number or the indication, a list of actions may be provided to the user identifying conversion options available for the number. For instance, a list of actions may be presented to the user for converting the number to text in any of a number of languages. Additionally, conversion options may also be presented to the user for converting the digit shapes of the number to digit shapes in another language.
According to one embodiment of the invention, a current user interface language setting for the application program is determined prior to providing the list of actions to the user. When the user selects the list of actions, the available actions are displayed to the user in a language specified by the current user interface language setting. In this manner, the user is always presented the conversion options in the current user interface language.
According to another actual embodiment of the invention, each of the enabled languages for the application program may also be identified prior to displaying the list of actions. Once the enabled languages have been identified, actions may be included in the list of actions only for converting the number to text in languages that are enabled. In this manner, a user is never presented with conversion options for converting to text in languages not enabled for use with the application program.
After the list of actions has been displayed to the user, a selection of one of the actions may be received. In response to receiving the selection of a conversion action, a converted number may be generated by converting the selected number to the text in the language identified by the selected action. Alternatively, a selection of a conversion action for converting the selected number to different digit shapes may be received. In response to such a selection, a converted number is generated by replacing each of the digit shapes in the selected number with a corresponding different digit shape. Once the conversion has been completed, the converted number may be inserted into the string of text to replace the selected number. According to various embodiments of the present invention, a document object model supported by the host application may be utilized to insert the converted number into the string of text.
According to another embodiment of the present invention, a system is provided for converting a number expressed as digits to text or to different digits. According to this embodiment of the invention, the system includes a recognizer plug-in capable of receiving a portion of an electronic document as a string of text from an application program. For instance, the recognizer plug-in may receive a paragraph of text from an application program as it is typed by the user. Once the recognizer plug-in has received the string of text, the recognizer plug-in analyzes the string of text to determine whether the string of text includes a number expressed using digits. If the string of text includes a number expressed using digits, the recognizer plug-in semantically labels the number with schema information identifying the number as being capable of conversion to text. This information is then passed by the recognizer plug-in back to the application program.
According to one embodiment of the invention, the system also includes an application program for creating and editing an electronic document. For instance, the application program may comprise a word processor, a spreadsheet application program, an e-mail application which includes editing functions, or other types of application programs for creating and editing electronic documents. According to this embodiment of the invention, the application program is capable of displaying the string of text along with an indication that the number has been semantically labeled by the recognizer plug-in. This indication may comprise a user interface object for indicating to a user that the number has been semantically labeled and that conversion actions may be performed on the number.
The application program may also be operative to receive a selection of the number or the indication and to provide a list of actions that may be performed on the number to convert the number to text or to different digit shapes. The application may then receive the selection of one of the list of actions and provide the selection and the number to an action plug-in.
The system also includes an action plug-in that is capable of generating a converted number by converting the selected number to text in the language identified by the selected action from the list of actions. The action plug-in may also generate a converted number by converting the selected number to digit shapes identified by the selected action from the list of actions. The action plug-in is also operative to replace the selected number with the converted number in the string of text. According to one actual embodiment of the invention, the action plug-in may replace the number with the converted number in the string of text by accessing a document object model provided by the application program.
According to various embodiments of the present invention, the system provided herein may also include an action plug-in that is operative to register with the application program prior to performing any conversion functions. As a part of the registration procedure, the action plug-in may provide the list of actions that may be performed on the number to convert the number to text or digit shapes. Moreover, when creating the list of actions, the action plug-in may determine a current user interface language setting for the application program and generate the action menu items in a language specified by the current user interface language setting. Additionally, the action plug-in may also identify one or more enabled languages for the application program and generate each of the action menu items only for conversion to text and digit shapes corresponding to the enabled languages. In this manner, the action plug-in ensures that users will be presented lists of actions in the current user interface language and only for conversions supported by the currently enabled languages of the application program.
Other embodiments of the present invention also provide a computer-controlled apparatus and a computer-readable medium for converting numbers to text and digit shapes in a user-selected language based on semantically labeled strings. These and other details regarding the various embodiments of the invention will become more apparent from the detailed description that follows.
As described briefly above, embodiments of the present invention provide a method, system, apparatus, and computer-readable medium for converting numbers to text and digit shapes in a user-selected language. In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments or examples. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit and scope of the present invention. The following detailed description is, therefore, not be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of the present invention and the exemplary operating environment will be described.
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Turning now to
The mass storage device 14 is connected to the CPU 4 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media, provide non-volatile storage for the personal computer 2. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the personal computer 2.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.
According to various embodiments of the invention, the personal computer 2 may operate in a networked environment using logical connections to remote computers through a TCP/IP network 18, such as the Internet. The personal computer 2 may connect to the TCP/IP network 18 through a network interface unit 20 connected to the bus 12. It should be appreciated that the network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The personal computer 2 may also include an input/output controller 22 for receiving and processing input from a number of devices, including a keyboard or mouse (not shown). Similarly, an input/output controller 22 may provide output to a display screen, a printer, or other type of output device.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 8 of the personal computer 2, including an operating system 16 suitable for controlling the operation of a networked personal computer, such as the WINDOWS XP operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 8 may also store one or more application programs. In particular, the mass storage device 14 and RAM 8 may store an application program 205 for creating and editing an electronic document 24. For instance, the application program 205 may comprise a word processing application program and the electronic document 24 may comprise a word processing document. The application program 205 may also comprise a spreadsheet application program and the electronic document 24 comprise a spreadsheet. Similarly, the application program 205 may comprise an electronic mail application program and the electronic document 24 may comprise an electronic mail message. Application programs for creating and editing other types of electronic documents may also be used with the various embodiments of the present invention.
Embodiments of the present invention provide program modules for use in conjunction with the application program 205 that convert numbers expressed using digit shapes contained within the electronic document 24 to text or to digit shapes in other languages. In particular, embodiments of the invention provide a recognizer plug-in 220 and an action plug-in 225. As will be described in greater detail below, the recognizer plug-in 220 recognizes numbers in an electronic document 24 and labels the numbers with semantic information. The recognizer plug-in 220 then passes this information to the application program 205 for use by the action plug-in 225. The action plug-in 225 performs actions on the recognized numbers for converting numbers expressed using digit shapes to text or to digit shapes in a user-selected language.
According to various embodiments of the present invention, the action plug-in 225 may also generate a list of actions that may be performed on a given number. As a part of this process, the action plug-in 225 may query language settings 26 of the application program 205 or operating system 16. The language settings 26 specify the current user interface language and the currently installed and enabled languages for the application program 205 and the operating system 16. The list of actions may then be customized based on the current user interface language and the installed languages. Additional details regarding the operation of the recognizer plug-in 220 and the action plug-in 225, including the use of the language settings 25 will be described in greater detail below.
Referring now to
The application program 205 is able to communicate with a recognizer dynamically linked library (“DLL”) 210 and an action DLL 215. As will be described in greater detail below, the recognizer DLL 210 controls one or more recognizer plug-ins 220A-220N and the action DLL 215 controls one or more action plug-ins 225A-225N.
According to one embodiment of the invention, the recognizer plug-ins 220A-220N and the action plug-ins 225A-225N are automation servers. Automation servers are well-known software components that are assembled into programs or add functionality to existing programs running on the WINDOWS XP operating system from MICROSOFT CORPORATION of Redmond, Wash. Automation servers may be written in a variety of computing languages and can be plugged and unplugged at runtime without having to recompile the host program.
The recognizer DLL 210 handles the distribution of text strings from an electronic document being edited by the application program 205 to the individual recognizer plug-ins 220A-220N. The recognizer plug-ins 220A-220N recognize particular strings in an electronic document, such as a word processing document or a spreadsheet document. The recognizer plug-ins 220A-220N may be packaged with the application program module 205 or they may be written by third parties to recognize particular strings of interest. Typically, the recognizer DLL 210 passes strings to the recognizer plug-ins 220A-220N in single paragraphs or cell value increments. However, strings may be passed to the recognizer plug-ins 220A-220N in other sizes and formats.
As part of recognizing certain strings as including semantic information, the recognizer plug-ins 220A-220N determine which strings are to be labeled and how they are to be labeled. After receiving these results from the various recognizer plug-ins 220, the recognizer DLL 210 sends semantic categories to the application program module 205. According to one actual embodiment of the invention, a recognizer plug-in 220 is provided for recognizing strings as containing numbers expressed using digit shapes. According to this embodiment of the invention, the semantic category comprises schema information that identifies the number and whether it is to be handled as a decimal number, an integer number, or both. This information is returned to the recognizer DLL 210 by the recognizer plug-in 220 along with other information that may be utilized by a corresponding action plug-in 225, such as a copy of the number. Additionally, the recognizer plug-in 220 may return information identifying the location of the number within the text string, including the length of the text string and the character number of the first digit of the number.
Semantic categories are stored as part of the electronic document along with other document information and are available when a document is transmitted from one computer to another computer. According to one embodiment, storing semantic categories in an electronic document is controlled by an “Embed semantic categories” checkbox. The checkbox is on by default. Turning it off will prevent semantic categories in the document from being saved. The state of the checkbox is per document. The same checkbox controls saving for both .htm and .doc documents. Checking a “Save semantic categories as eXtensible Markup Language (XML) properties” checkbox (off by default) will write out the text of all of the semantic categories in the document and their labels in the header of the Hypertext Markup Language (HTML) file in XML (that is using the same tags as are used inline, but surrounded by <xml> And </xml>) for easy identification and parsing by search engines and knowledge management systems.
It should be appreciated that each of the recognizer plug-ins 220A-220N are executed separately. The recognizer DLL 210 is responsible for handling the asynchronicity that results from different recognizer plug-ins 220A-220N returning results at different times. In this manner, various types of data may be recognized within a text string and different actions provided for each semantically labeled string. Additional details regarding the operation of the recognizer plug-in 220 for recognizing numbers will be described below with reference to
After a string is labeled by a recognizer plug-in 220A-220N, schema information is sent to the application program module 205. A user of the application program module 205 may then execute actions that are associated with the schema information on the recognized string. The action DLL 215 manages the action plug-ins 225A-225N that are executed in order to perform the actions. As with the recognizer plug-ins 220A-22N, the action plug-ins 225A-225N may be packaged with the application program module 205 or written by third parties to perform particular actions that are of interest. The action plug-ins 225A-225N provide possible actions to be presented to the user based upon the schema information, or type label, associated with the string. As will be described in greater detail below, the list of actions provided to the user is dynamically generated for each schema type. This information is then provided to the application program 205 which displays the list of actions to the user when the string is selected.
After an action has been chosen from the list of actions, the action DLL 215 manages the appropriate action plug-in 225A-225N and passes the necessary information between the action plug-in and the application program module 205 so that the action plug-in may execute the desired action. Typically, the application program module 205 sends the action DLL 215 an automation request to invoke the action the user has selected. As will be described in greater detail below, according to one embodiment of the invention, an action plug-in 225 is provided that converts recognized numbers to text or digit shapes in a user-selected language. Addition details regarding the operation of the action plug-in 225 will be described in greater detail below with reference to
Turning now to
Referring now to
As shown in
As also shown in
As further shown in
As described briefly above, when a number 32 is recognized by the recognizer plug-in 220, the number 32 is labeled with schema information indicating that the number may be converted to text or digits in different languages. The schema information is then returned to the application program module 205 and is utilized by the action plug-in 225 to determine the appropriate list of actions 38 that should be included in the dropdown menu 36. In this manner, only conversion operations consistent with numbers that are expressed as digits are provided to the user via the dropdown menu 36. For instance, no conversion operations would be displayed if the number was originally expressed as text.
As will be discussed in greater detail below, the application program 205 receives most of the text shown in the dropdown menu 36 from the action plug-in 225. This process occurs when the application program 205 is initially executed and the action plug-in 225 registers itself with the application program 205. Additional details regarding this registration process will be described below with reference to
As shown in
To account for the situation where the decimal or thousands separator characters are ambiguous, embodiments of the invention allow the user to indicate the proper usage. For instance, as shown in
Referring now to
The routine 400 begins at block 402, where the current user interface language is identified. As discussed briefly above, the current user interface language may be stored in the language settings 26 maintained by the operating system 16 or the application program 205. Once the current user interface language has been identified, the routine 400 continues to block 404. At block 404, the currently enabled languages are also identified. In particular, the language settings 26 may again be consulted to determine the languages that are enabled and installed for use with the operating system 16 or with the application program 205.
Once the currently enabled languages have been identified, the routine 400 continues to block 406, where action menu items are generated for each schema type for the enabled languages. In this manner, action items are generated for each schema type and for the currently enabled languages. No action items are generated for conversion options corresponding to languages that are not installed or enabled.
From block 406, the routine 400 continues to block 408, where the action menu items are created in the current user interface language. In this manner, the dropdown menu 36 displayed to the user is provided in the current user interface language. From block 408, the routine continues to block 410, where the action menus for each schema are returned to the application program 205. According to one embodiment of the invention, the application program 205 displays the dropdown menu 36 in response to the selection of a number 32 or an indicator 34. However, it should be appreciated that the action plug-in 225 or other software component may be responsible for the display of the dropdown menu 36. The routine 400 continues from block 410 to block 412, where it ends.
Turning now to
From block 504, the routine 500 continues to block 506, where the recognizer DLL 210 passes the string to the recognizer plug-ins 220A-220N. The routine 500 then continues to block 508 where the recognizer plug-ins are executed on the paragraph to recognize key words within the string. In particular, the recognizer plug-in for converting numbers to text and digit shapes in user-selected languages is executed on the string. An illustrative routine describing the operation of the recognizer plug-in for number conversion is described below with reference to
At block 510, the results from the recognizer plug-in 220 are received at the recognizer DLL 210. The routine 500 then continues to block 512, where a determination is made by the recognizer DLL 210 as to whether the paragraph has been edited since the string was transmitted to the recognizer plug-ins 220A-220N. If the paragraph has been edited, the routine 500 returns to block 504, where the edited string is passed to the recognizer DLL 210. If the paragraph has not been edited, the routine 500 continues to block 514, where the recognizer DLL 210 sends the results received from the recognizer plug-in 220 to the application program 205. The routine 500 then continues to block 516, where it ends.
Referring now to
From block 604, the routine 600 continues to block 606, where a determination is made as to whether a number expressed using digits was found in the string of text. If no digits were found, the routine 600 branches from block 606 to block 620, where it returns to block 510, shown in
At block 608, a determination is made as to whether the recognized number includes separator characters that may be ambiguous. As described above, certain decimal and thousands separator characters are used inconsistently around the world. Therefore, it may be impossible to determine the actual value of a particular number. Accordingly, if a recognized number includes ambiguous separator characters, the routine 600 branches to block 610, where the number is tagged with schema information for both decimal and integer numbers. In this manner, a dropdown menu will be provided to the user for the number with options for converting both decimal and integer numbers and the user can make the determination as to the appropriate use of the ambiguous separator characters. From block 610, the routine 600 continues to block 618.
If, however, at block 608, it is determined that the recognized number does not contain any ambiguous separator characters, the routine 600 continues to block 612, where a determination is made as to whether the number is a decimal number. If the number is a decimal number, the routine 600 branches to block 614, where the number is tagged with schema information corresponding to decimal numbers. The routine 600 then continues from block 614 to block 618.
If, at block 612, it is determined that the number is not a decimal number, the routine continues to block 616, where the number is tagged with schema information corresponding to integer numbers. The routine 600 then continues from block 616 to block 618, where the schema names are returned to the recognizer DLL 210. Additionally, a “property bag” is also returned to the recognizer DLL 210. The property bag is an object which stores information about the recognized number that may be utilized by the action plug-in 225. In particular, the property bag includes a copy of the recognized number and the schema associated with the number. The property bag may also include other types of data about the number. The data stored in the property bag may be utilized by the action plug-in. From block 618, the routine 600 continues to block 620, where it returns to block 510, shown in
Referring now to
At block 704, the application program 205 displays the list of actions associated with the schema corresponding to the selected number. In this manner, the dropdown menu 36 described above with reference to
At block 708, the application program 205 calls the action plug-in 225 corresponding to the appropriate schema type and indicates that an action item has been selected. The call from the application program 225 to the action plug-in 225 includes the schema name corresponding to the recognized number, the item number of the selected menu item, the name of the calling application program 205, a pointer into an object model provided by the application program 205 for accessing the document 24, the property bag described above with reference to
Referring now to
If, at block 804, it is determined that the user has not selected a menu item for converting the recognized number to text, the routine 800 continues to block 808. At block 808, a determination is made as to whether the user has selected a menu item for converting the recognized number to digit shapes. If the user has requested that the recognized number be converted to different digit shapes, the routine 800 branches to block 810, where the recognized number is converted to digit shapes in the character set identified by the user. The routine 800 then continues from block 810 to block 812.
At block 812, the number in the string of text is replaced with the converted number. According to one embodiment of the present invention, the replacement is made by accessing a document object model provided by the application program 205. Through the document object model, the action plug-in 225 can directly access the document 24 and make changes therein. Details regarding the use of such a document object model are well known to those skilled in the art. From block 812, the routine 800 continues to block 814, where it returns to block 714, described above with reference to
Based on the foregoing, those skilled in the art should appreciate that various embodiments of the present invention provide a method, system, apparatus, and computer-readable medium for converting numbers expressed as digit shapes to text or digits in a user-selected language based upon semantically labeled strings. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Number | Name | Date | Kind |
---|---|---|---|
4674065 | Lange et al. | Jun 1987 | A |
4868750 | Kucera et al. | Sep 1989 | A |
5020019 | Ogawa | May 1991 | A |
5128865 | Sadler | Jul 1992 | A |
5159552 | van Gasteren et al. | Oct 1992 | A |
5267155 | Buchanan et al. | Nov 1993 | A |
5287448 | Nicol et al. | Feb 1994 | A |
5297039 | Kanaegami et al. | Mar 1994 | A |
5317546 | Balch et al. | May 1994 | A |
5337233 | Hofert et al. | Aug 1994 | A |
5341293 | Vertelney et al. | Aug 1994 | A |
5351190 | Kondo | Sep 1994 | A |
5386564 | Shearer et al. | Jan 1995 | A |
5392386 | Chalas | Feb 1995 | A |
5418902 | West et al. | May 1995 | A |
5446891 | Kaplan et al. | Aug 1995 | A |
5522089 | Kikinis et al. | May 1996 | A |
5535323 | Miller et al. | Jul 1996 | A |
5541836 | Church et al. | Jul 1996 | A |
5546521 | Martinez | Aug 1996 | A |
5581684 | Dudzik et al. | Dec 1996 | A |
5596700 | Darnell et al. | Jan 1997 | A |
5617565 | Augenbraun et al. | Apr 1997 | A |
5625783 | Ezekiel et al. | Apr 1997 | A |
5627567 | Davidson | May 1997 | A |
5627958 | Potts et al. | May 1997 | A |
5634019 | Koppolu et al. | May 1997 | A |
5640560 | Smith | Jun 1997 | A |
5657259 | Davis et al. | Aug 1997 | A |
5685000 | Cox | Nov 1997 | A |
5708825 | Sotomayor | Jan 1998 | A |
5715415 | Dazey et al. | Feb 1998 | A |
5717923 | Dedrick | Feb 1998 | A |
5752022 | Chiu et al. | May 1998 | A |
5761689 | Rayson et al. | Jun 1998 | A |
5764794 | Perlin | Jun 1998 | A |
5765156 | Guzak et al. | Jun 1998 | A |
5781189 | Holleran et al. | Jul 1998 | A |
5781904 | Oren et al. | Jul 1998 | A |
5794257 | Liu et al. | Aug 1998 | A |
5799068 | Kikinis et al. | Aug 1998 | A |
5802253 | Gross et al. | Sep 1998 | A |
5802262 | Van De Vanter | Sep 1998 | A |
5802299 | Logan et al. | Sep 1998 | A |
5802530 | van Hoff | Sep 1998 | A |
5805911 | Miller | Sep 1998 | A |
5809318 | Rivette et al. | Sep 1998 | A |
5815830 | Anthony | Sep 1998 | A |
5818447 | Wolf et al. | Oct 1998 | A |
5821931 | Berquist et al. | Oct 1998 | A |
5822539 | van Hoff | Oct 1998 | A |
5822720 | Bookman et al. | Oct 1998 | A |
5826025 | Gramlich | Oct 1998 | A |
5832100 | Lawton et al. | Nov 1998 | A |
5845077 | Fawcett | Dec 1998 | A |
5855007 | Jovicic et al. | Dec 1998 | A |
5859636 | Pandit | Jan 1999 | A |
5872973 | Mitchell et al. | Feb 1999 | A |
5875443 | Nielsen | Feb 1999 | A |
5877757 | Baldwin et al. | Mar 1999 | A |
5884266 | Dvorak | Mar 1999 | A |
5892919 | Nielsen | Apr 1999 | A |
5893073 | Kasso et al. | Apr 1999 | A |
5893132 | Huffman et al. | Apr 1999 | A |
5895461 | De La Huerga et al. | Apr 1999 | A |
5896321 | Miller et al. | Apr 1999 | A |
5900004 | Gipson | May 1999 | A |
5907852 | Yamada | May 1999 | A |
5913214 | Madnick et al. | Jun 1999 | A |
5920859 | Li | Jul 1999 | A |
5924099 | Guzak et al. | Jul 1999 | A |
5933139 | Feigner et al. | Aug 1999 | A |
5933140 | Strahorn et al. | Aug 1999 | A |
5933498 | Schneck et al. | Aug 1999 | A |
5940614 | Allen et al. | Aug 1999 | A |
5944787 | Zoken | Aug 1999 | A |
5946647 | Miller et al. | Aug 1999 | A |
5948061 | Merriman et al. | Sep 1999 | A |
5956681 | Yamakita | Sep 1999 | A |
5974413 | Beauregard et al. | Oct 1999 | A |
5987480 | Donohue et al. | Nov 1999 | A |
5991719 | Yazaki et al. | Nov 1999 | A |
5995756 | Hermann | Nov 1999 | A |
6006265 | Rangan et al. | Dec 1999 | A |
6006279 | Hayes | Dec 1999 | A |
6014616 | Kim | Jan 2000 | A |
6018761 | Uomini | Jan 2000 | A |
6028605 | Conrad et al. | Feb 2000 | A |
6029135 | Krasle | Feb 2000 | A |
6029171 | Smiga et al. | Feb 2000 | A |
6031525 | Perlin | Feb 2000 | A |
6052531 | Waldin et al. | Apr 2000 | A |
6061516 | Yoshikawa et al. | May 2000 | A |
6067087 | Krauss et al. | May 2000 | A |
6072475 | Van Ketwich | Jun 2000 | A |
6073090 | Fortune et al. | Jun 2000 | A |
6085201 | Tso | Jul 2000 | A |
6088711 | Fein et al. | Jul 2000 | A |
6092074 | Rodkin et al. | Jul 2000 | A |
6108640 | Slotznick | Aug 2000 | A |
6108674 | Murakami et al. | Aug 2000 | A |
6112209 | Gusack | Aug 2000 | A |
6121968 | Arcuri et al. | Sep 2000 | A |
6122647 | Horowitz et al. | Sep 2000 | A |
6126306 | Ando | Oct 2000 | A |
6137911 | Zhilyaev | Oct 2000 | A |
6141005 | Hetherington et al. | Oct 2000 | A |
6151643 | Cheng et al. | Nov 2000 | A |
6154738 | Call | Nov 2000 | A |
6167469 | Safai et al. | Dec 2000 | A |
6167523 | Strong | Dec 2000 | A |
6167568 | Gandel et al. | Dec 2000 | A |
6173316 | De Boor et al. | Jan 2001 | B1 |
6182029 | Friedman | Jan 2001 | B1 |
6185550 | Snow et al. | Feb 2001 | B1 |
6185576 | McIntosh | Feb 2001 | B1 |
6199046 | Heinzle et al. | Mar 2001 | B1 |
6199081 | Meyerzon et al. | Mar 2001 | B1 |
6208338 | Fischer et al. | Mar 2001 | B1 |
6219698 | Iannucci et al. | Apr 2001 | B1 |
6246404 | Feigner et al. | Jun 2001 | B1 |
6262728 | Alexander | Jul 2001 | B1 |
6272074 | Winner | Aug 2001 | B1 |
6272505 | De La Huerga | Aug 2001 | B1 |
6282489 | Bellesfield et al. | Aug 2001 | B1 |
6291785 | Koga et al. | Sep 2001 | B1 |
6292768 | Chan | Sep 2001 | B1 |
6295061 | Park et al. | Sep 2001 | B1 |
6297822 | Feldman | Oct 2001 | B1 |
6300950 | Clark et al. | Oct 2001 | B1 |
6308171 | De La Huerga | Oct 2001 | B1 |
6311152 | Bai et al. | Oct 2001 | B1 |
6311177 | Dauerer et al. | Oct 2001 | B1 |
6311194 | Sheth et al. | Oct 2001 | B1 |
6320496 | Sokoler et al. | Nov 2001 | B1 |
6323853 | Hedloy | Nov 2001 | B1 |
6336125 | Noda et al. | Jan 2002 | B2 |
6336131 | Wolfe et al. | Jan 2002 | B1 |
6338059 | Field et al. | Jan 2002 | B1 |
6339436 | Amro et al. | Jan 2002 | B1 |
6339755 | Hetherington et al. | Jan 2002 | B1 |
6347398 | Parthasarathy et al. | Feb 2002 | B1 |
6349295 | Tedesco et al. | Feb 2002 | B1 |
6353926 | Parthesarathy et al. | Mar 2002 | B1 |
6381742 | Forbes et al. | Apr 2002 | B2 |
6382350 | Jezewski et al. | May 2002 | B1 |
6392668 | Murray | May 2002 | B1 |
6396515 | Hetherington et al. | May 2002 | B1 |
6401067 | Lewis et al. | Jun 2002 | B2 |
6408323 | Kobayashi et al. | Jun 2002 | B1 |
6413100 | Dickmeyer et al. | Jul 2002 | B1 |
6415304 | Horvitz | Jul 2002 | B1 |
6421678 | Smiga et al. | Jul 2002 | B2 |
6424979 | Livingston et al. | Jul 2002 | B1 |
6434567 | De La Huerga | Aug 2002 | B1 |
6438545 | Beauregard et al. | Aug 2002 | B1 |
6441753 | Montgomery | Aug 2002 | B1 |
6442545 | Feldman et al. | Aug 2002 | B1 |
6442591 | Haynes et al. | Aug 2002 | B1 |
6456304 | Anguilo et al. | Sep 2002 | B1 |
6470091 | Koga et al. | Oct 2002 | B2 |
6473069 | Gerpheide | Oct 2002 | B1 |
6477510 | Johnson | Nov 2002 | B1 |
6480860 | Monday | Nov 2002 | B1 |
6493006 | Gourdol et al. | Dec 2002 | B1 |
6498982 | Bellesfield et al. | Dec 2002 | B2 |
6510504 | Satyanarayanan | Jan 2003 | B2 |
6516321 | De La Huerga | Feb 2003 | B1 |
6519557 | Emens et al. | Feb 2003 | B1 |
6519603 | Bays et al. | Feb 2003 | B1 |
6546433 | Matheson | Apr 2003 | B1 |
6553385 | Johnson et al. | Apr 2003 | B2 |
6556972 | Bakis et al. | Apr 2003 | B1 |
6556984 | Zien | Apr 2003 | B1 |
6564264 | Creswell et al. | May 2003 | B1 |
6571241 | Nosohara | May 2003 | B1 |
6571253 | Thompson et al. | May 2003 | B1 |
6591260 | Schwarzhoff et al. | Jul 2003 | B1 |
6595342 | Maritzen et al. | Jul 2003 | B1 |
6601075 | Huang et al. | Jul 2003 | B1 |
6604099 | Chung et al. | Aug 2003 | B1 |
6615131 | Rennard et al. | Sep 2003 | B1 |
6618733 | White et al. | Sep 2003 | B1 |
6622140 | Kantrowitz | Sep 2003 | B1 |
6623527 | Hamzy | Sep 2003 | B1 |
6625581 | Perkowski | Sep 2003 | B1 |
6629079 | Spiegel et al. | Sep 2003 | B1 |
6631519 | Nicholson et al. | Oct 2003 | B1 |
6636880 | Bera | Oct 2003 | B1 |
6643650 | Slaughter et al. | Nov 2003 | B1 |
6654734 | Mani et al. | Nov 2003 | B1 |
6654932 | Bahrs et al. | Nov 2003 | B1 |
6658623 | Schilit et al. | Dec 2003 | B1 |
6687485 | Hopkins et al. | Feb 2004 | B2 |
6694307 | Julien | Feb 2004 | B2 |
6697824 | Bowman-Amuah | Feb 2004 | B1 |
6697837 | Rodov | Feb 2004 | B1 |
6708189 | Fitzsimons et al. | Mar 2004 | B1 |
6715144 | Daynes et al. | Mar 2004 | B2 |
6717593 | Jennings | Apr 2004 | B1 |
6718516 | Claussen et al. | Apr 2004 | B1 |
6728679 | Strubbe et al. | Apr 2004 | B1 |
6732090 | Shanahan et al. | May 2004 | B2 |
6732361 | Andreoli et al. | May 2004 | B1 |
6741994 | Kang et al. | May 2004 | B1 |
6742054 | Upton, IV | May 2004 | B1 |
6745208 | Berg et al. | Jun 2004 | B2 |
6766326 | Cena | Jul 2004 | B1 |
6795808 | Strubbe et al. | Sep 2004 | B1 |
6802061 | Parthasarathy et al. | Oct 2004 | B1 |
6826726 | Hsing et al. | Nov 2004 | B2 |
6829631 | Forman et al. | Dec 2004 | B1 |
6857103 | Wason | Feb 2005 | B1 |
6859908 | Clapper | Feb 2005 | B1 |
6868525 | Szabo | Mar 2005 | B1 |
6874125 | Carroll et al. | Mar 2005 | B1 |
6874143 | Murray et al. | Mar 2005 | B1 |
6880129 | Lee et al. | Apr 2005 | B1 |
6883137 | Girardot et al. | Apr 2005 | B1 |
6898604 | Ballinger et al. | May 2005 | B1 |
6901402 | Corston-Oliver et al. | May 2005 | B1 |
6904560 | Panda | Jun 2005 | B1 |
6925457 | Britton et al. | Aug 2005 | B2 |
6925470 | Sangudi et al. | Aug 2005 | B1 |
6944857 | Glaser et al. | Sep 2005 | B1 |
6948133 | Haley | Sep 2005 | B2 |
6950831 | Haley | Sep 2005 | B2 |
6950982 | Dourish | Sep 2005 | B1 |
6957385 | Chan et al. | Oct 2005 | B2 |
6963867 | Ford et al. | Nov 2005 | B2 |
6964010 | Sharp | Nov 2005 | B1 |
6975983 | Fortescue et al. | Dec 2005 | B1 |
6976090 | Ben-Shaul et al. | Dec 2005 | B2 |
6976209 | Storisteanu et al. | Dec 2005 | B1 |
6981212 | Claussen et al. | Dec 2005 | B1 |
6986104 | Green et al. | Jan 2006 | B2 |
6990654 | Carroll, Jr. | Jan 2006 | B2 |
7003522 | Reynar et al. | Feb 2006 | B1 |
7013289 | Horn et al. | Mar 2006 | B2 |
7024658 | Cohen et al. | Apr 2006 | B1 |
7028312 | Merrick et al. | Apr 2006 | B1 |
7032174 | Montero et al. | Apr 2006 | B2 |
7039859 | Sundaresan | May 2006 | B1 |
7051076 | Tsuchiya | May 2006 | B2 |
7082392 | Butler et al. | Jul 2006 | B1 |
7100115 | Yennaco | Aug 2006 | B1 |
7113976 | Watanabe | Sep 2006 | B2 |
7146564 | Kim et al. | Dec 2006 | B2 |
7216351 | Maes | May 2007 | B1 |
7281245 | Reynar et al. | Oct 2007 | B2 |
7302634 | Lucovsky et al. | Nov 2007 | B2 |
7305354 | Rodriguez et al. | Dec 2007 | B2 |
7421645 | Reynar | Sep 2008 | B2 |
7454459 | Kapoor et al. | Nov 2008 | B1 |
20010029605 | Forbes et al. | Oct 2001 | A1 |
20010041328 | Fisher | Nov 2001 | A1 |
20010042098 | Gupta et al. | Nov 2001 | A1 |
20010049702 | Najmi | Dec 2001 | A1 |
20010056461 | Kampe et al. | Dec 2001 | A1 |
20020002590 | King et al. | Jan 2002 | A1 |
20020003469 | Gupta | Jan 2002 | A1 |
20020003898 | Wu | Jan 2002 | A1 |
20020004803 | Serebrennikov | Jan 2002 | A1 |
20020007309 | Reynar | Jan 2002 | A1 |
20020023113 | Hsing et al. | Feb 2002 | A1 |
20020023136 | Silver et al. | Feb 2002 | A1 |
20020026450 | Kuramochi | Feb 2002 | A1 |
20020029304 | Reynar et al. | Mar 2002 | A1 |
20020035581 | Reynar et al. | Mar 2002 | A1 |
20020038180 | Bellesfield et al. | Mar 2002 | A1 |
20020065110 | Enns et al. | May 2002 | A1 |
20020065891 | Malik | May 2002 | A1 |
20020066073 | Lienhard et al. | May 2002 | A1 |
20020078222 | Compas et al. | Jun 2002 | A1 |
20020091803 | Imamura et al. | Jul 2002 | A1 |
20020099687 | Krishnaprasad et al. | Jul 2002 | A1 |
20020100036 | Moshir et al. | Jul 2002 | A1 |
20020103829 | Manning et al. | Aug 2002 | A1 |
20020104080 | Woodard et al. | Aug 2002 | A1 |
20020110225 | Cullis | Aug 2002 | A1 |
20020111928 | Haddad | Aug 2002 | A1 |
20020120685 | Srivastava et al. | Aug 2002 | A1 |
20020129107 | Loughran et al. | Sep 2002 | A1 |
20020133523 | Ambler et al. | Sep 2002 | A1 |
20020149601 | Rajarajan et al. | Oct 2002 | A1 |
20020156774 | Beauregard et al. | Oct 2002 | A1 |
20020156792 | Gombocz et al. | Oct 2002 | A1 |
20020169802 | Brewer et al. | Nov 2002 | A1 |
20020178008 | Reynar | Nov 2002 | A1 |
20020178182 | Wang et al. | Nov 2002 | A1 |
20020184247 | Jokela et al. | Dec 2002 | A1 |
20020188941 | Cicciarelli et al. | Dec 2002 | A1 |
20020196281 | Audleman et al. | Dec 2002 | A1 |
20020198909 | Huynh et al. | Dec 2002 | A1 |
20030002391 | Biggs | Jan 2003 | A1 |
20030005411 | Gerken | Jan 2003 | A1 |
20030009489 | Griffin | Jan 2003 | A1 |
20030014745 | Mah et al. | Jan 2003 | A1 |
20030025728 | Ebbo et al. | Feb 2003 | A1 |
20030046316 | Gergic et al. | Mar 2003 | A1 |
20030050911 | Lucovsky et al. | Mar 2003 | A1 |
20030051236 | Pace et al. | Mar 2003 | A1 |
20030056207 | Fischer et al. | Mar 2003 | A1 |
20030081791 | Erickson et al. | May 2003 | A1 |
20030083910 | Sayal et al. | May 2003 | A1 |
20030084138 | Tavis et al. | May 2003 | A1 |
20030097318 | Yu et al. | May 2003 | A1 |
20030101190 | Horvitz et al. | May 2003 | A1 |
20030101204 | Watson | May 2003 | A1 |
20030101416 | McInnes et al. | May 2003 | A1 |
20030106040 | Rubin et al. | Jun 2003 | A1 |
20030115039 | Wang | Jun 2003 | A1 |
20030121033 | Peev et al. | Jun 2003 | A1 |
20030126136 | Omoigui | Jul 2003 | A1 |
20030140308 | Murthy et al. | Jul 2003 | A1 |
20030154144 | Pokorny et al. | Aug 2003 | A1 |
20030158841 | Britton et al. | Aug 2003 | A1 |
20030158851 | Britton et al. | Aug 2003 | A1 |
20030167445 | Su et al. | Sep 2003 | A1 |
20030172343 | Leymaster et al. | Sep 2003 | A1 |
20030177341 | Devillers | Sep 2003 | A1 |
20030182391 | Leber et al. | Sep 2003 | A1 |
20030192040 | Vaughan | Oct 2003 | A1 |
20030195937 | Kircher et al. | Oct 2003 | A1 |
20030212527 | Moore et al. | Nov 2003 | A1 |
20030220795 | Araysantiparb et al. | Nov 2003 | A1 |
20030229593 | Raley et al. | Dec 2003 | A1 |
20030233330 | Raley et al. | Dec 2003 | A1 |
20040002939 | Arora et al. | Jan 2004 | A1 |
20040003389 | Reynar et al. | Jan 2004 | A1 |
20040006564 | Lucovsky et al. | Jan 2004 | A1 |
20040006741 | Radja et al. | Jan 2004 | A1 |
20040024875 | Horvitz et al. | Feb 2004 | A1 |
20040039990 | Bakar et al. | Feb 2004 | A1 |
20040044959 | Shanmugasundaram et al. | Mar 2004 | A1 |
20040068694 | Kaler et al. | Apr 2004 | A1 |
20040083218 | Feng | Apr 2004 | A1 |
20040133846 | Khoshatefeh et al. | Jul 2004 | A1 |
20040143581 | Bohannon et al. | Jul 2004 | A1 |
20040165007 | Shafron | Aug 2004 | A1 |
20040199861 | Lucovsky | Oct 2004 | A1 |
20040201867 | Katano | Oct 2004 | A1 |
20040236717 | Demartini et al. | Nov 2004 | A1 |
20050050164 | Burd et al. | Mar 2005 | A1 |
20050055330 | Britton et al. | Mar 2005 | A1 |
20050094850 | Nakao | May 2005 | A1 |
20050108195 | Yalovsky et al. | May 2005 | A1 |
20050120313 | Rudd et al. | Jun 2005 | A1 |
20050187926 | Britton et al. | Aug 2005 | A1 |
20060173674 | Nakajima et al. | Aug 2006 | A1 |
Number | Date | Country |
---|---|---|
2 246 920 | Mar 2000 | CA |
ZL 200410005390.8 | Oct 2008 | CN |
0 364 180 | Apr 1990 | EP |
0481784 | Apr 1992 | EP |
0598511 | May 1994 | EP |
0872827 | Oct 1998 | EP |
0810520 | Dec 1998 | EP |
1093058 | Apr 2001 | EP |
1280068 | Jan 2003 | EP |
1361523 | Nov 2003 | EP |
1376392 | Jan 2004 | EP |
1 447 754 | Aug 2004 | EP |
1 425 966 | Sep 2004 | EP |
64-88771 | Apr 1989 | JP |
05-174013 | Jul 1993 | JP |
08-272662 | Oct 1996 | JP |
09-138636 | May 1997 | JP |
10-171827 | Jun 1998 | JP |
2000-222394 | Aug 2000 | JP |
2000-231566 | Aug 2000 | JP |
2001-014303 | Jan 2001 | JP |
2001-125994 | May 2001 | JP |
2001-522112 | Nov 2001 | JP |
2001-0350464 | Dec 2001 | JP |
2002163250 | Jun 2002 | JP |
2003-141174 | May 2003 | JP |
WO 9507510 | Mar 1995 | WO |
WO 9917240 | Apr 1999 | WO |
WO 0054174 | Sep 2000 | WO |
WO 0067117 | Nov 2000 | WO |
WO 0073949 | Dec 2000 | WO |
WO 0118687 | Mar 2001 | WO |
WO 0137170 | May 2001 | WO |
WO 0186390 | Nov 2001 | WO |
WO 0299627 | Jan 2002 | WO |
WO 0215518 | Feb 2002 | WO |
WO 0242928 | May 2002 | WO |
WO 2004012099 | Feb 2004 | WO |