Cross-platform architecture to handle international text in internet

• US 6,754,694 B1
• Filed: 02/28/2000
• Issued: 06/22/2004
• Est. Priority Date: 02/28/2000
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Hiura, Hideki, Hegde, Prabhat
• Primary Examiner(s): Wiley, David
• Assistant Examiner(s): Neurauter, George C
• Application Number:
  US09/514,537
• Time in Patent Office: 1,576 Days
• Field of Search: 341/90, 345/467, 709/206, 709/207, 707/10, 707/513, 704/8, 704/7, 710/100-104
• US Class Current: 709/206
• CPC Class Codes: G06F 40/126 Character encoding
• CPC Class Codes: G06F 40/40 Processing or translation of natural language natural language analysis G06F40/20; semantic analysis G06F40/30
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression

Abstract

Methodology that enables an email sender to view and send a message in substantially any desired character set, and apparatus to perform the methodology. The methodology and apparatus taught herein also enable email software to automatically display a message utilizing the proper character set or sets. This methodology and apparatus further enables mail software to automatically include in the mail message sufficient information to meet the previously defined needs utilizing standard MIME conventions.

According to one aspect of the present invention, there is provided a flexible flat file syntax that holds per-locale information about mail, based on MIME conventions. The information in the file is used to build a database that may be used by mail clients through a new API. The contents of the file can also be configured by users to fit their individual and specific mail needs.

Claims

1. Utilizing standard MIME conventions, a methodology for enabling an e-mail sender to view and send an email message in any desired standardized character set, the method comprising the steps of:

composing the email message;

providing a library including a plurality of conversion library definition files;

accessing the library to define the character set definition and an identifier of a code converter required for converting the email message from a first standardized character set to a second standardized character set;

including in the email message a flat file further defining a mail body, the character set definition, and the identifier of the code converter required for converting the email message, the mail body including the email message.

3. A methodology as recited in claim 1, wherein at least one of the plurality of conversion library definition files is in plain ASCII text format.

4. A methodology as recited in claim 1, wherein the character set definition is one of:

ASCII, IANA, ISO, or JIS.

5. A methodology as recited in claim 1, wherein composing the email includes:

using a Posix compliant email program to compose the email.

6. A methodology as recited in claims 5, wherein the Posix compliant email program is dtmail.

7. A methodology as recited in claim 5, wherein the code converter required for converting the email message is operating system dependent.

2. Apparatus for enabling an e-mail sender to view and send an email message in any desired standardized character set, the apparatus comprising;

an email composition program implemented on a computer;

a library including a plurality of conversion library definition files; and

a utility for generating a flat file including a mail body further including the email message, a character set definition, and an identifier of a code converter required for converting the email messa from a first standardized character set to a second standardized character set, the flat file implementing standard MIME conventions.

8. An apparatus as recited in claim 2, wherein the converter specification is used to define preferences with respect to the conversion.

9. An apparatus as recited in claim 2, wherein the apparatus further includes a library and a conversion library definition file.

10. An apparatus as recited in claim 2, wherein at least one of the plurality of conversion library definition files is in plain ASCII text format.

11. An apparatus as recited in claim 2, wherein the character set definition is one of:

ASCII, IANA, ISO, or JIS.

12. An apparatus as recited in claim 2, wherein the email composition program is a Posix compliant email program.

13. An apparatus as recited in claim 12, wherein the Posix compliant email program is dtmail.

14. An apparatus as recited in claim 2, wherein the converter specification is operating system dependent.

15. Utilizing standard MIME conventions, a method of automatic exchange of email messages between email users, the method comprising:

providing an email Application Programming Interface;

providing an email database which includes information pertaining to an e-mail in a MIME form, information pertaining to each of supported MIME character sets, and information pertaining to code conversion between each of the supported MIME character sets;

composing an email message;

accessing the email database using the email Application Programming Interface to obtain information needed to compose an email message that is to be sent from a first client using a first standardized character set to a second client using a second standardized character set which is different from the first standardized character set used by the first client;

generating a flat file based on the information obtained from the email database, the flat file defining a mail body, a character set definition, and an identifier of a code converter required for converting the email message from the first standardized character set to the second standardized character set, whereby the flat file provides information that can be used to convert the message in accordance with requirements of the second client; and

sending the flat file to the second client.

16. A method as recited in claim 15, wherein the method further comprises:

using the flat file to convert the email to the second standardized character set.

17. A method as recited in claim 15, wherein the method further comprises:

accessing another email database to convert the email to the second standardized character set.

18. A method as recited in claim 15, wherein the email database further includes user preferences with respect to character set conversion.

19. A method as recited in claim 15, further comprising:

using a dtmail client to access the email Application Propramming Interface.