SUMMARY
This article provides general information about the language features in Exchange 2000. This article contains references to other articles and is not intended to be a complete list of the language features in Exchange 2000.
back to the top
Multiple Character Set Support
Exchange 2000 permits users to send, receive, and store rich sets of data in any country and in any language. Exchange 2000 can do this regardless of the language that is used by the Exchange 2000 server or Microsoft Windows 2000 Server.
Exchange 2000 presents data to the user in the most appropriate format, with consideration for the user's language. Therefore, if the Exchange 2000 store can determine the character set of the message content, the Exchange 2000 store uses that character set to present the data. If the Exchange 2000 store cannot determine the character set, Exchange 2000 uses what seems to be the best character set (for example, Unicode, UTF-8, Shift-JIS, or ISO-8859-1), depending on the message content.
You can configure Exchange 2000 to use one character set for Exchange 2000 and use another character set or language version for Windows 2000 Server.
For additional information about how to change character sets in Exchange 2000, click the article number below
to view the article in the Microsoft Knowledge Base:
325250 XGEN: How to Change Default Character Sets in Exchange 2000 Server
Exchange 2000 also provides multiple language support for its Microsoft Outlook clients. For additional information about multiple language support for Outlook, click the article number below
to view the article in the Microsoft Knowledge Base:
325591 XGEN: Languages Supported by Exchange 2000 Server for Use with Microsoft Outlook Clients
back to the top
Multiple Languages for Organizational Forms
An organizational forms library is a system folder that stores forms that are frequently accessed by the users in an organization. When you create an Organizational Forms Library, Exchange 2000 assigns a language to it. By default, foreign language users search for forms in the library that matches the language that their e-mail client uses. Therefore, you must create individual libraries to hold the forms for foreign language users. If there is no language-specific Organizational Forms Library, the users search the library that is on the server. You can only have one Organizational Forms Library for each language.
For additional information about Organizational Forms Libraries, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
271816 XADM: How to Create an Organizational Forms Library in Exchange 2000
253526 XADM: Organizational Forms Library and Different Languages
back to the top
Full-Text Indexing and Multiple Languages
Exchange 2000 can create and manage full-text indexes for fast searches. Full-text indexes use the language setting of individual messages to determine which
word breaker to use. Word breakers are language utilities that identify words in a document. If a message is a MAPI message, the
Locale ID property is used to determine which word breaker to use. This property value comes from the Microsoft Office Language setting.
For additional information about full-text indexing, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
294821 XADM: Recommendations for Using Content Indexing Utilities (Pstoreutl or Catutil) in a Cluster Environment
325624 XGEN: How Full-Text Indexing Works with Multiple Languages
back to the top
Multiple Language Support for Outlook Web Access
The Microsoft Outlook Web Access (OWA) user interface (UI) uses the Accept-Language header that is sent by the browser. Exchange 2000 contains code pages that have localized UIs for Chinese (Simplified), Chinese (Traditional), English, French, German, Italian, Japanese, Korean, and Spanish.
For additional information about Outlook Web Access, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
310599 HOWTO: Hard Code the Language of OWA Interface
325001 XGEN: Languages Supported by Exchange 2000 Server, Windows 2000 Server, and Outlook Web Access
back to the top