| IEnumCodePage |
This interface is implemented in the Code Page Enumeration Object, which is used to create a list of all code pages in the MIME database. A client can use this interface to retrieve an array of MIMECPINFO structures, which contain detailed information about a given code page. IEnumCodePage is initialized through a call to IMultiLanguage::EnumCodePages. In this call, the client has the option of setting one or more of the flags defined in the MIMECONTF enumerated type, depending on the client's requirements. For example, a browser client can set MIMECONTF_BROWSER to obtain a list of character sets that are appropriate for its character-set-switching menu. This interface should be used when a client wants information about many code pages at once, or when a client wants to know which code pages fit a certain flag. If information about specific code pages is needed, the client should call IMultiLanguage::GetCodePageInfo. |
| IEnumRfc1766 |
This interface is implemented in the Locale Enumeration Object, which is used to create a list of all locale identifiers (LCIDs) in the MIME database. A client can use this interface to retrieve an array of RFC1766INFO structures, which contain the Windows®-defined name and the RFC1766-conforming name corresponding to an LCID. A client uses this service to enumerate the entire set of LCIDs with human-readable names. This interface is created through a call to IMultiLanguage::EnumRfc1766 and should be used when a client wants a list of all LCIDs the system recognizes. If a client wants information about specific locales, it is faster and easier to call IMultiLanguage::GetRfc1766Info. If the entire RFC1766INFO structure is not needed, a client can call IMultiLanguage::GetRfc1766FromLcid to retrieve only the RFC1766-conforming name. |
| IEnumScript |
This interface enumerates the scripts on the system. |
| IMLangCodePages |
This interface is implemented in the MultiLanguage Object and provides the foundation of the IMLangFontLink interface. It defines a set of code pages and implements a number of methods for working with a set of code pages. In addition, IMLangCodePages provides methods to translate between individual code page identifier values and sets of code pages. This interface also contains methods that determine which code pages contain a given Unicode character or string. Because IMLangFontLink inherits from IMLangCodePages, every IMLangCodePages method is available through the IMLangFontLink interface.Crucial to the IMLangCodePages interface is the concept of a set of code pages. A DWORD is used to represent a set of code pages, and each bit in the DWORD represents a specific code page. When a bit is set to 1, its corresponding code page is considered to be included in the set; if the bit is set to 0, its code page is not considered a member. Thus the DWORD 0x1e0000 would represent the code pages corresponding to the bits 0x100000, 0x80000, 0x40000, and 0x20000. All IMLangCodePages methods use this concept. |
| IMLangConvertCharset |
This interface represents a conversion engine object that is dedicated to specific source and destination code pages. A client can create an instance of the Conversion Object by using IMultiLanguage::CreateConvertCharset or by explicitly calling CoCreateInstance. With IMLangConvertCharset, MLang can perform more efficient character set conversions than with the methods in the IMultiLanguage interface. A caller uses this interface to repeatedly perform character set conversions involving the same combination of source/destination code pages. This interface can also be used to reinitialize the Conversion Object with new source and destination code pages as many times as necessary. This prevents a caller from having to destroy and then re-create the object to change the source or destination code page. |
| IMLangFontLink |
This is a top-level interface that implements a set of services to enable an application to utilize font linking. Font linking is a term used to describe the process of automatic font switching based on the character code values of the text stream to be rendered. For example, characters for Hebrew and Japanese are not likely included in a single font. The services this interface provides would help a client switch between the fonts needed to output a string containing characters from both languages. IMLangFontLink does this by creating custom fonts and providing an underlying font cache in the implementation. This interface is implemented in the MultiLanguage Object and derives from IMLangCodePages, which provides the foundation of the font linking function. |
| IMLangFontLink2 |
This is a top-level interface that implements a set of services to enable an application to utilize font linking. Font linking is a term used to describe the process of automatic font switching based on the character code values of the text stream to be rendered. For example, characters for Hebrew and Japanese are not likely included in a single font. The services this interface provides would help a client switch between the fonts needed to output a string containing characters from both languages. IMLangFontLink2 does this by creating custom fonts and providing an underlying font cache in the implementation. This interface is implemented in the MultiLanguage Object and derives from IMLangCodePages, which provides the foundation of the font linking function. |
| IMLangLineBreakConsole |
This interface is implemented in the MultiLanguage Object and provides a console-based line-breaking service. A client uses this service to utilize a multilingual line-breaking functionality that varies based upon locale. This interface is currently designed only for use in console-based functions, such as a mail client application that needs to format text in a specific column size. |
| IMLangString |
Not currently supported. |
| IMLangStringAStr |
Not currently supported. |
| IMLangStringBuf |
Not currently supported. |
| IMLangStringNotifySink |
Not currently supported. |
| IMLangStringWStr |
Not currently supported. |
| IMLStrAttr |
Not currently supported. |
| IMLStrAttrAStr |
Not currently supported. |
| IMLStrAttrLocale |
Not currently supported. |
| IMLStrAttrLong |
Not currently supported. |
| IMLStrAttrNotifySink |
Not currently supported. |
| IMLStrAttrWStr |
Not currently supported. |
| IMultiLanguage |
This interface contains methods that perform two primary functions: gathering information about charsets, code pages, or locales from the MIME database and converting strings from one charset to another.IMultiLanguage also provides access to three interfaces that can perform the above tasks multiple times in a more efficient way than repeatedly using the IMultiLanguage methods. The enumeration interfaces IEnumCodePage and IEnumRfc1766 can retrieve information about many code pages or locales at once. The conversion engine interface IMLangConvertCharset should be used for multiple conversions between the same source and destination code pages.For Microsoft® Internet Explorer 5 and later, MLang provides the IMultiLanguage2 interface that is derived from IMultiLanguage and should be used in its place. |
| IMultiLanguage2 |
The IMultiLanguage2 interface is an updated version of the IMultiLanguage interface. Introduced in Microsoft® Internet Explorer 5, IMultiLanguage2 provides all the functionality of IMultiLanguage. In addition, it implements three new methods and expands two conversion methods. These changes create a new code page detection functionality and enhance the existing charset conversion functionality that MLang provides. IMultiLanguage2 also supports the original abilities of IMultiLanguage, such as charset conversion and information retrieval from the MIME database. Included in these tasks is the retrieval of the IEnumCodePage, IEnumRfc1766, and IMLangConvertCharset interfaces. IMultiLanguage2 should be used in place of IMultiLanguage. |
Back to top