The font usage screen

		All Products \| Support \| Search \| microsoft.com Home

Microsoft Typography | ...on the Web | ...embedding | WEFT | The font usage screen

The font usage screen
Once the pages have been analyzed the font usage screen is displayed.

The WEFT wizard start page
Figure 1. The WEFT font usage screen.

Each font used by your pages will be listed in the table on this screen. The fonts are flagged using the same traffic light system used by the font check feature.
okay to embed. These fonts have their embedding permissions set to allow embedding, and have passed error checks.
Windows core font. These fonts have been identified as common core fonts. Embedding these fonts is not recommended.
'no embedding' font. These fonts have their embedding permissions set to 'no embedding'.
font may be broken! These fonts can not be embedded because they have failed error tests.
Occasionally a font that is marked as 'okay to embed' by the font check feature will be listed as broken at this stage. This is because more rigorous tests are performed on the font at this stage of the operation.
status unknown. WEFT is unable to examine the font file because it isn't properly listed in the Windows registry.
If you decide not to include a common core font or any other font, highlight it and click the 'Don't Embed' button.
The Subset column lists the total number of different characters from each font that are used by the pages analyzed. By default when WEFT creates font objects it will only include the characters actually used by your pages. However, with various types of pages, such as those that contain dynamic content, the characters used may change through user input or other events. To ensure that an adequate number of characters are included, WEFT features seven different levels of automatic subsetting. You can also manually edit the individual font subsets generated by clicking the 'Subset' button.

Subsetting
There are seven different levels of font subsetting supported by Microsoft WEFT. The 'Font Subsetting' drop down box lets you alter the type of subsetting used by the tool.

'Per Page' Subsetting
The tool analyzes font usage on a page by page basis. For each page, font objects are created for each font used. Each font object will only contain the characters used by a particular page, and will only be linked to that page.

Minimal subsetting
Example: If you have five pages that use Garamond Italic, five different Garamond Italic font objects will be created and linked to the corresponding pages. If visitors are only going to access an individual page, then this level of subsetting will be the most efficient.
If you expect visitors to access a number of pages on your site, then Normal Subsetting will probably be more efficient.

'Per Site' Subsetting
The tool analyzes font usage across your pages on a per font basis. Only one font object will be created for each font used. This object will contain all the characters used by all the pages that use the font.

Minimal subsetting
Example: If you have five pages that use Garamond Italic, only one font object will be created. This object will contain all the Garamond Italic characters used by these five pages. This font object will be linked to all the pages that use the font.

Family based Subsetting (default)
The tool analyzes font usage across your pages on a per font family basis. All font objects created from a given font family will contain the same characters.
Example: If you have a page that uses 'a', 'b' and 'c' from Garamond, and characters 'd' and 'e' from Garamond Italic, font objects for both Garamond and Garamond Italic will be created that contain 'a', 'b', 'c', 'd' and 'e'.
Family based subsetting should be the typical setting for dynamic HTML pages where scripts may dynamically alter the style of elements in the document. For example, visited links may be displayed in a bold face while non-visited links are in the regular font.

Union subsetting
The tool analyzes font usage across your pages on a character use basis. All font objects created will contain the same glyphs.
Example: If you have a page that uses 'a', 'b' and 'c' from Garamond, and characters 'd' and 'e' from Gill Sans, font objects for both Garamond and Gill Sans will be created that contain 'a', 'b', 'c', 'd' and 'e'.
This level will handle more complex Dynamic HTML scenarios where not only the style but the font usage can be changed on the fly.

Raw subsetting
The tool analyzes font usage across your pages on a font basis, however font objects will contain all of the characters used by the page regardless of their visibility. This is similar to union subsetting, the difference being that the raw HTML pages are used to compute the character usage. These font objects will include characters used in scripts and comments as well as those displayed within the browser window when the page is loaded.

Language subsetting
This option will result in font objects being created based on language usage rather than statistical information about character usage. You can specify any one of the 96 Unicode code point ranges as defined by ISO 10646.
Warning! We do not recommend the use of 'Language subsetting' when creating font objects based on Far East fonts, as the file size of the font object will be very large.

No subsetting
The font object will contain all the characters contained in each font used.
Warning! We do not recommend the use of 'No subsetting' when creating font objects based on Far East fonts, as the file size of the font object will be very large.

this page was last updated 16 January 1998
© 1998 Microsoft Corporation. All rights reserved. Legal Notices.
please e-mail comments to us via the e-mail address listed here.

Microsoft Typography | ...on the Web | ...embedding | WEFT | The font usage screen



	Microsoft Typography \| ...on the Web \| ...embedding \| WEFT \| The font usage screen

		The font usage screen Once the pages have been analyzed the font usage screen is displayed. Figure 1. The WEFT font usage screen. Each font used by your pages will be listed in the table on this screen. The fonts are flagged using the same traffic light system used by the font check feature. okay to embed. These fonts have their embedding permissions set to allow embedding, and have passed error checks. Windows core font. These fonts have been identified as common core fonts. Embedding these fonts is not recommended. 'no embedding' font. These fonts have their embedding permissions set to 'no embedding'. font may be broken! These fonts can not be embedded because they have failed error tests. Occasionally a font that is marked as 'okay to embed' by the font check feature will be listed as broken at this stage. This is because more rigorous tests are performed on the font at this stage of the operation. status unknown. WEFT is unable to examine the font file because it isn't properly listed in the Windows registry. If you decide not to include a common core font or any other font, highlight it and click the 'Don't Embed' button. The Subset column lists the total number of different characters from each font that are used by the pages analyzed. By default when WEFT creates font objects it will only include the characters actually used by your pages. However, with various types of pages, such as those that contain dynamic content, the characters used may change through user input or other events. To ensure that an adequate number of characters are included, WEFT features seven different levels of automatic subsetting. You can also manually edit the individual font subsets generated by clicking the 'Subset' button. Subsetting There are seven different levels of font subsetting supported by Microsoft WEFT. The 'Font Subsetting' drop down box lets you alter the type of subsetting used by the tool. 'Per Page' Subsetting The tool analyzes font usage on a page by page basis. For each page, font objects are created for each font used. Each font object will only contain the characters used by a particular page, and will only be linked to that page. Example: If you have five pages that use Garamond Italic, five different Garamond Italic font objects will be created and linked to the corresponding pages. If visitors are only going to access an individual page, then this level of subsetting will be the most efficient. If you expect visitors to access a number of pages on your site, then Normal Subsetting will probably be more efficient. 'Per Site' Subsetting The tool analyzes font usage across your pages on a per font basis. Only one font object will be created for each font used. This object will contain all the characters used by all the pages that use the font. Example: If you have five pages that use Garamond Italic, only one font object will be created. This object will contain all the Garamond Italic characters used by these five pages. This font object will be linked to all the pages that use the font. Family based Subsetting (default) The tool analyzes font usage across your pages on a per font family basis. All font objects created from a given font family will contain the same characters. Example: If you have a page that uses 'a', 'b' and 'c' from Garamond, and characters 'd' and 'e' from Garamond Italic, font objects for both Garamond and Garamond Italic will be created that contain 'a', 'b', 'c', 'd' and 'e'. Family based subsetting should be the typical setting for dynamic HTML pages where scripts may dynamically alter the style of elements in the document. For example, visited links may be displayed in a bold face while non-visited links are in the regular font. Union subsetting The tool analyzes font usage across your pages on a character use basis. All font objects created will contain the same glyphs. Example: If you have a page that uses 'a', 'b' and 'c' from Garamond, and characters 'd' and 'e' from Gill Sans, font objects for both Garamond and Gill Sans will be created that contain 'a', 'b', 'c', 'd' and 'e'. This level will handle more complex Dynamic HTML scenarios where not only the style but the font usage can be changed on the fly. Raw subsetting The tool analyzes font usage across your pages on a font basis, however font objects will contain all of the characters used by the page regardless of their visibility. This is similar to union subsetting, the difference being that the raw HTML pages are used to compute the character usage. These font objects will include characters used in scripts and comments as well as those displayed within the browser window when the page is loaded. Language subsetting This option will result in font objects being created based on language usage rather than statistical information about character usage. You can specify any one of the 96 Unicode code point ranges as defined by ISO 10646. Warning! We do not recommend the use of 'Language subsetting' when creating font objects based on Far East fonts, as the file size of the font object will be very large. No subsetting The font object will contain all the characters contained in each font used. Warning! We do not recommend the use of 'No subsetting' when creating font objects based on Far East fonts, as the file size of the font object will be very large. this page was last updated 16 January 1998 © 1998 Microsoft Corporation. All rights reserved. Legal Notices. please e-mail comments to us via the e-mail address listed here.


	Microsoft Typography \| ...on the Web \| ...embedding \| WEFT \| The font usage screen