Windows Mobile 6.5
A version of this page is also available for

The IMLangFontLink2 interface implements a set of services that enable an application to use font linking. It inherits from the IMLangCodePages interface and subsumes the IMlangFontLink interface. This interface is not supported on all Windows Mobile operating systems. See the SDK documentation specific to your target device to see whether this functionality is supported.

The following table shows the methods for this interface. Like all COM interfaces, this interface inherits the methods of the IUnknown interface.

Method Description


Retrieves the script identifier associated with a code page.


Retrieves the set of code pages whose characters can be output by the given font on the given device context.


Retrieves information about which Unicode characters are supported by a font.


Retrieves the font information for the specified script.


Creates a font to output the characters from the given set of code pages or to output a character not found in a code page.


Releases a font object created by the IMLangFontLink2::MapFont method.


Clears the font cache that is used to store fonts created by the IMLangFontLink2::MapFont method.

This interface enables an application to use 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 provided by this interface would allow a client to switch between a Hebrew font and a Japanese font to output a string containing characters from both languages. The IMLangFontLink2 interface does this by creating custom fonts and providing an underlying font cache in the implementation.

Headermlang.h, mlang.idl
Windows Embedded CEWindows CE .NET 4.0 and later
Windows MobileWindows Mobile Version 5.0 and later

Community Additions