Embodiments of the present invention relate to the field of date conversion. More particularly, embodiments of the invention relate to the field of converting dates between languages and calendars based upon semantically labeled strings.
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 express dates in more than one language and possibly in more than one calendar type. For instance, a user may refer to a date expressed in the English language and the Gregorian calendar. Similarly, a user may express a date in the That language and the Buddhist calendar.
When creating electronic documents having dates expressed in different languages and calendar types, users may need to convert dates between languages and calendars. For instance, a user may want to convert the English Gregorian date to a That Buddhist date. However, converting between languages and calendars in this manner has heretofore been difficult for a user to accomplish easily. Previously, if a user wanted to convert a date between calendars and/or languages, the user would have to copy the date to be converted to a clipboard and then paste the date into an external program or World Wide Web (“Web”) site capable of converting the date.
Once the external program or Web site had completed the conversion, the user would copy the converted date to the clipboard and then paste the converted date back into their document. Although systems such as these permit a user to convert a date between calendars and/or languages, these systems can be difficult for a user to use because of the large number of steps required to complete the conversion. Moreover, these previous solutions require the user to perform the conversion using the user interface language of the conversion program or Web site. This can be extremely frustrating for a user that does not understand the language of the conversion program or Web site.
Therefore, in light of the above, there is a need for a method, system, and apparatus for easily converting dates between calendars and languages that do not require a user to utilize an external application or Web site to convert dates between calendars and languages. Moreover, there is a need for a method, system, and apparatus for converting dates between calendars and languages that can present conversion options to the user in a user-selected user interface language.
Embodiments of the present invention solve the above-described problems by providing a method, system, and apparatus for easily converting dates between calendars and languages that do not require the use of an external application or Web site to convert dates. Moreover, embodiments of the present invention provide a method, system, and apparatus for converting dates between calendars and languages that can present conversion options to the user in a user-selected interface language. Moreover, embodiments of the invention only present conversion options to the user for languages for which a host operating system or a host application provides support.
According to one actual embodiment of the present invention, a method is provided for converting a date between calendars and languages 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 dates between calendars and languages. 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 date. If the string of text includes a date, the date is semantically labeled with schema information that identifies the calendar and language used to express the date. For instance, if a date is expressed using the Gregorian calendar and the English language, schema information will be associated with the string indicating the language and calendar type.
Once a date has been identified within a string of text, such as a paragraph, the application may display an indication to the user that the date has been semantically labeled. This indication also identifies to the user that actions may be performed on the date. When a selection is received of the date or the indication, a list of actions may be provided to the user identifying conversion options available for the date. For instance, if the identified date is expressed in the English language and the Gregorian calendar, an action menu item may be displayed to the user for converting the date into a Hebrew Lunar date. Other types of conversion options may also be presented to the user for converting the date between languages and calendars.
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 between language and calendar types corresponding to enabled languages. In this manner, a user is never presented with conversion options for converting to languages unsupported by the current configuration of their 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 date may be generated by converting the selected date to the calendar and language identified by the selected action. Once the conversion has been completed, the converted date may be inserted into the string of text to replace the selected date. According to various embodiments of the present invention, a document object model supported by the host application may be utilized to insert the converted date into the string of text.
According to another embodiment of the present invention, a system is provided for converting a date between calendars and languages. 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 date. If the string of text includes a date, the recognizer plug-in semantically labels the date with schema information identifying the calendar and language used to express the date. 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 date has been semantically labeled by the recognizer plug-in. This indication may comprise a user interface object for indicating to a user that the date has been semantically labeled and that conversion actions may be performed on the date.
The application program may also be operative to receive a selection of the date or the indication and to provide a list of actions that may be performed on the date to convert the date to another language or calendar. The application may then receive the selection of one of the list of actions and provide the selection and the date to an action plug-in.
The system also includes an action plug-in that is capable of generating a converted date by converting the selected date to the calendar or language identified by the selected action from the list of actions. The action plug-in is also operative to replace the selected date with the converted date in the string of text. According to one actual embodiment of the invention, the action plug-in may replace the date with the converted date 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 date to convert the date to another calendar or language to the application program. 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 between language and calendar types 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 dates between calendars and languages 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 dates between languages and calendar types. 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 dates contained within the electronic document 24 between calendar types and 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 dates in an electronic document 24 and labels the dates with semantic information identifying the language and calendar that the dates are expressed in. 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 dates for converting between calendars and languages.
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 date. 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. Additionally, the action plug-in 225 may also query the date format settings 28 for the operating system 16 and use the date format settings 28 to format converted dates. The date format settings 28 are specified by the user and define the format in which dates should be displayed by default. For instance, a user may specify that dates be expressed using numbers only, such as “04/02/02”, or using names and numbers, such as “Apr. 2, 2002.” Other possible formats may also be specified. 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 and the date format settings 28, 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 or unplugged from a program at runtime without having to recompile the 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 dates. According to this embodiment of the invention, the semantic category comprises schema information that identifies the calendar and language used to express the date. 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 date, and parameters describing the various parts of the date such as the month, year, date, calendar type, day of week, and language that the month name is express in. Additionally, the recognizer plug-in 220 may return information identifying the location of the date within the text string, including the length of the text string and the character number of the first letter of the date. 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 dates will be described below with reference to
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.
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 dates between various calendars and languages. Addition details regarding the operation of the action plug-in 225 and the schema information utilized to identify different calendar and language types will be described in greater detail below with reference to
Referring now to
When the date 32 or the indication 34 is selected by a user, a list of actions is displayed that may be performed on the date to convert the date to another language or calendar. This list of actions may comprise a dropdown menu 36 having one or more menu items corresponding to the list of actions that may be performed on the date. According to one embodiment of the invention, the contents of the dropdown menu may be displayed in one of many different languages. The language in which the dropdown menu 36 is displayed is based on a current user interface language for the application program module 205 or the operating system 16. In this manner, international users throughout the world will be displayed a dropdown menu 36 in their currently installed and active user interface language.
As shown in
As shown in
As described briefly above, when a date 32 is recognized by the recognizer plug-in 220, the date 32 is labeled with schema information identifying the calendar and language used to express the date 32. 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 the type of calendar and language used to express the date 32 are provided to the user via the dropdown menu 36.
The date 32 shown in
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
The recognizer plug-in 220 is also capable of recognizing dates expressed in different languages and utilizing different digit shapes. For instance, as shown in
As shown in
The recognizer plug 220 may also recognize dates expressed in the Hebrew Lunar calendar. As known to those skilled in the art, the length of a Hebrew Lunar month is more closely associated with the lunar cycle than a Gregorian month is, but does not have as tight an association with the moon as the Hijri calendar uses. The first day of the Hebrew Lunar year is tied to a certain season, but varies by a few weeks within the solar year. A thirteenth-month is also added at intervals in order to keep the season and months together in the Hebrew Lunar calendar. The numbers in a Hebrew Lunar date, including the year, are usually written not with digits, but instead with Hebrew letters. The recognizer plug-in 220 is capable of recognizing such letters. The dropdown menu 36 displayed when a Hebrew Lunar date 32 is recognized is shown in
As known to those skilled in the art, the Hijri calendar is also different from the Gregorian calendar. Hijri months are tied to the cycle of the moon and a number of days in a Hijri year is different from the Gregorian calendar. The recognizer plug-in 220 is also capable of converting dates between the Hijri calendar and other calendars. As shown in
The schema name “urn:schemas-microsoft-com:office:cs:smarttags#date1hi” is utilized when a recognized Gregorian date string uses a Hindi language name for the month, such as the date 32 shown in
Although embodiments of the invention have been described as capable of recognizing dates in the Gregorian, Hijri, and Lunar calendars and the Arabic, English, Hebrew, Hindi, Thai, and Vietnamese languages, other calendars and languages may also be recognized and converted similarly.
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 date 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 dates is executed on the string. An illustrative routine describing the operation of the recognizer plug-in for date 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 digits were found in the string of text. If no digits were found, the routine 600 branches from block 606 to block 628, where it returns to block 510, shown in
At block 608, a determination is made as to whether the identified digits in the string of text may represent a year or a day of week. For example, extremely large numbers or extremely low numbers may be ruled out as possible candidates to represent a year. Similarly, extremely large numbers may also be ruled out as being candidates to represent a day. These determinations may be made on a per calendar basis. Other types of determinations may also be made for determining whether the digits may possibly represent a day or a year.
From block 608 the routine 600 continues to block 610 where a determination is made as to whether the digits located in the string of text may possibly represent a day or year. If the digits may not represent a day or year, the routine 610 branches to block 628, where it returns to block 510, shown in
At block 612, text located before and after the located digits is scanned to identify additional text portions of the date or additional number portions of the date. For instance, if the digits located within the string of text comprise a year, the text before the number may be scanned to locate the date portion and, for instance, a month portion. Similarly, if the digits located are the date portion, the text after the date may be scanned to locate the year portion of the date. In this manner, the string of text representing the entire date, such as “Friday, Feb. 28, 1992,” may be identified.
According to one embodiment of the invention, text prior to and after the digits located in the string of text may be searched only for dates expressed in languages currently supported by the personal computer 2. To perform this function, a list of month names and day names may be consulted for each language to identify text corresponding to dates expressed in the installed languages. In this manner, processing time is not expended on identifying dates that are expressed in languages not supported by the personal computer 2.
From block 612, the routine 600 continues to block 618, where a determination is made as to whether the portion of the string of text identified, including text before and after the digits, is a date candidate. A date candidate is an all numeric date expressed in a certain format, or date and year digits expressed along with words indicating that the digits represent a date, such as a month name, or a day name. If the digits and the surrounding text are not a date candidate, the routine 600 branches to block 628, where it returns to block 510 shown in
At block 620, the date format for the candidate date is identified. For instance, the separator characters used to separate a date and a year may be identified to properly locate the digits used to express the day, month and year. According to one embodiment of the invention, a preferred date format as specified by the user in the date format settings 28 may be utilized to determined the correct date format for the date candidate.
From block 620, the routine 600 continues to block 622 where a determination is made as to whether the identified date format is recognized. If the date format is not a recognized date format, the routine 600 branches to block 628, where it returns to block 510, shown in
At block 626, the schema name associated with the language and calendar type used to express the date is 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 date that may be utilized by the action plug-in 225. In particular, the property bag includes properties that identify the year, month number, and day of month for the recognized date. The property bag may also include a format number indicating generally which format the recognized date was written in. This number is utilized according to one embodiment of the invention so that the format for a converted date may be matched to the format of the recognized date. For example, if the weekday name was in the recognized date, then the action plug-in 225 would attempt to include the equivalent weekday name in the converted date.
A calendar type number may also be utilized in the property bag to distinguish Gregorian, Hijri, and Hebrew Lunar calendars. A language number may also be included in the property bag to indicate which language the month name was written in. Additionally, an index to the recognized date within the string of text may also be returned to the recognizer DLL 210. All of the information returned from the recognizer plug-in 220 to the recognizer DLL 210 may be subsequently passed to the action plug-in 225 and used in the conversion process. This is described in greater detail below with respect to
Referring now to
At block 704, the application program 205 displays the list of actions associated with the schema corresponding to the selected date. 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 date, 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
From block 804, the routine 800 continues to block 806, where a determination is made as to whether the received year is represented utilizing only two digits. If the received year is represented utilizing four digits, the routine 800 branches from block 806 to block 810. If, however, the received year is expressed utilizing only two digits, the routine 800 continues to block 808. At block 808, the century corresponding to the digit year is generated. This may include making an assumption regarding the century digits based on the value of the year digits. For instance, if the year digits are “99”, it may be assumed that the century digits are “19”. Other types of assumptions may also be made to generate the century digits corresponding to the year digits.
From block 808, the routine 800 continues to block 810, where a determination is made as to whether the date is being represented in the Gregorian calendar. If the date is being represented in the Gregorian calendar, the routine 800 continues to block 814, where the Gregorian date is converted by the action plug-in 225 to the calendar and language types indicated by the selected action item menu. Accordingly to one embodiment of the invention, the action plug-in 225 is configured for use within an environment provided by the MICROSOFT OFFICE (“MSO”) productivity suite provided by MICROSOFT Corporation of Redmond, Wash. According to this embodiment of the invention, the conversion that occurs at block 811 is performed by calling the routine INTLDATE, which is a part of the MSO shared program code. As known to those skilled in the art, the INTLDATE routine can convert between calendars and languages. From block 811, the routine 800 then continues to block 824, discussed below. If, at block 810, it is determined that the recognized date is not expressed in a Gregorian calendar, the routine 800 continues to block 816.
At block 816, a Gregorian date is estimated from the received date. The routine then continues to block 818, where the estimated Gregorian date is converted to a date in the calendar type of the received date. For instance, if the received date is expressed in the Hijri calendar, the estimated Gregorian date is then converted to its equivalent in the Hijri calendar. This conversion may also be performed by calling the MSO shared code described above.
From block 818, the routine 800 continues to block 820, where a determination is made as to whether the converted date is equal to the received date. If the converted date is equivalent to the received date, this means that the estimated Gregorian date is the actual equivalent of the received date. Therefore, if the converted date does not equal the received date, the routine 800 branches to block 822, where parameters are adjusted for estimating the Gregorian date from the received date. The routine then continues from block 822 to block 816, where the Gregorian date is again estimated and the above procedure repeated.
If, however, at block 820 it is determined that the converted date is equal to the received date, then the routine 800 continues to block 824. At block 824, the converted Gregorian date is converted to the format and language specified by the selected action menu item. This conversion is performed by a call to the INTLDATE function in the MSO shared code.
From block 824, the routine 800 then continues to block 826 where the day of the week is determined if necessary to expressing the converted day in a particular format. For instance, if the received date only includes the date and year number, the day of week, such as “Wednesday”, may be identified. The routine 800 then continues to block 828, where the date in the string of text is replaced with the converted date. 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 828, the routine 800 continues to block 830, 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 dates between calendars and languages 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 |
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 | 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 | Angiulo et al. | Sep 2002 | B1 |
6470091 | Koga et al. | Oct 2002 | B2 |
6473069 | Gerpheide | Oct 2002 | B1 |
6493006 | Gourdol et al. | Oct 2002 | B1 |
6477510 | Johnson | Nov 2002 | B1 |
6480860 | Monday | Nov 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 |
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 |
6766326 | Cena | Jul 2004 | B1 |
6795808 | Strubbe et al. | Sep 2004 | B1 |
6802061 | Parthasarathy et al. | Oct 2004 | B1 |
6829631 | Forman et al. | Dec 2004 | B1 |
6845499 | Srivastava et al. | Jan 2005 | B2 |
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 |
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 |
7237190 | Rollins et al. | Jun 2007 | B2 |
7281245 | Reynar et al. | Oct 2007 | B2 |
7302634 | Lucovsky et al. | Nov 2007 | B2 |
7305354 | Rodriguez et al. | Dec 2007 | B2 |
7392479 | Jones et al. | Jun 2008 | 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 |
20020023113 | Hsing et al. | Feb 2002 | A1 |
20020023136 | Silver et al. | Feb 2002 | A1 |
20020026450 | Kuramochi | Feb 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 |
20020175955 | Gourdol 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 |
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 |
2002-041353 | Feb 2002 | JP |
2002163250 | Jun 2002 | JP |
2002-222181 | Aug 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 |