| Microsoft Typography | ...on the Web | ...embedding | ...WEFT 2 | WEFT issues | |||
|
|
|||
|
We're currently working on fixes to several Windows 2000 related issues. We do not recommend that the current version of WEFT is used on Windows 2000.
Weft has problems locating and analyzing Web pages that have spaces in their URL, such as 'c:/my documents/test.htm'. If test pages work from your hard drive but fail to display when uploaded to the Web, chances are allowed roots do not match. See the Weft tutorial for more details.
Linking font objects to font names longer than 16 characters will crash Microsoft Internet Explorer 4.0pp2. The following stylesheet code demonstrates the problem.
@font-face { font-family: Franklin Gothic Book;
src: url(FRANK0.EOT); }
.caption { font-family: Franklin Gothic Book; }
A solution to this problem is to manually edit the @font-face declaration and any other style declarations that specify the font.
@font-face { font-family: FGBook;
src: url(FRANK0.EOT); }
.caption { font-family: FGBook; }
A bug in Internet Explorer 4.0 causes text on some pages to be printed using a default font instead of the specified embedded font. The cause of the problem was identified and fixed in Internet Explorer 4.01.
We have confirmed that these controls only work with fully installed fonts and not embedded fonts, which are privately installed.
WEFT uses Microsoft Internet Explorer to scan Web sites identifying the font and style attributes of each character displayed on a page. Unfortunately Internet Explorer does not identify the character, style or font used to display bullets or numbers used to prefix HTML list items. These characters need to be added to the subset manually.
WEFT uses Microsoft Internet Explorer to scan Web sites identifying the font and style attributes for each character displayed on a page. A bug in Internet Explorer 4.0pp2 has forced us to implement a workaround which causes the last character displayed in a particular element to be wrongly identified. The fix for this problem is to add a space before any </FONT> or similar tags used on your pages. This problem only affects the preview versions of Internet Explorer 4. If WEFT detects that you are using a recent version it won't use the workaround, and will correctly identify the characters, styles and fonts used. Avoid the use of 'synthesized fonts' as these will cause problems, and may result in the missing glyph (a square) being used to render text. A synthesized font is an italic, bold or bold italic font created by Windows by artificially emboldening or slanting the regular weight of the specified font. This is more common than you might think. For example, you often see Comic Sans MS Italic used on Web sites even though no such font exists. Here text is rendered using the regular Comic Sans MS which has been slanted by Windows. If you can not avoid using synthesized fonts, a possible workaround is to set the subsetting level to 'family subsetting', 'union subsetting', 'language subsetting' or 'no subsetting'. However be aware that the font object file sizes will be larger than is necessary, and the font objects 'containing' the synthesized fonts will be a duplicate of the font object containing the real font.
By default the public preview 2 version of Internet Explorer 4.0 will issue a security warning every time a font object is accessed. By default the release version does not issue such warnings.
Although your security level settings can easily be modified, we recommend you first access Internet Explorer's online help and read the sections discussing security before making the following changes:
|
|||
| Microsoft Typography | ...on the Web | ...embedding | ...WEFT 2 | WEFT issues | |||