Embedding Fonts

WebCompiler uses the IE4 (and above) rendering engine. IE4 supports a capability known as "embedded fonts". Basically, this means you can author your content using any fonts you have on your system, and then "embed" those fonts with your presentation (unless the fonts are marked as not licensed for embedding).

Even if the end user doesn't have those fonts on his system he will still see the presentation using the fonts you intended, because those fonts will be carried with the presentation. The user won't be able to extract the fonts or otherwise use them for other purposes.

For more details about font embedding, visit the Typography pages of the Microsoft Web Site at

http://www.microsoft.com/typography/web/default.htm

where there is a lot of information, and from where you can download WEFT and the other tools you need to embed fonts in your presentation.

There are some simple step you must take, however, to allow WebCompiler to use embedded fonts.

When you build your .eot file using WEFT, you must add as an allowed root the string ic32pp: which will allow the pages in your presentation to access the embedded fonts (this is the "root" that WebCompiler uses). You will probably want to add this in addition to the existing Allowed Root that WEFT will have put there, so you can still view the fonts from disk using IE4. Multiple Allowed Roots can be specified in the Allowed Roots edit box separated by a semicolon, so the entry in the box will look something like -

file://C:\weft\;ic32pp:

	You must ensure that the location you specify to WEFT to create the font objects (the .eot files) is a location that will be "compiled in" to your presentation.
	Don't change any of the code that WEFT embeds in your Web page.
	You must check the Enable Font Embedding checkbox on the Functionality tab of the Compiler Options dialog.