Intro  SetUp  WEFT   OE5  FAQs


Outlook Express 5
Tutorial for making Email EOTs with Microsoft WEFT3
 
Email comments to: Cheryl Soshnik

Last Update: July 9, 2001

A link for help with WEFT in Outlook Express 6
(added January 24, 2004)

 
spacer
Introduction
spacer
 
Microsoft WEFT is a program designed to allow users to see web pages and email in the font that the author used to create them, even if the user does not have that particular font installed on their computer.  "WEFT" stands for Web Embedding Fonts Tool, and the embedded font created is called an "EOT", which stands for Embedded Object Type.
 
The EOTs are viewable within the Microsoft environment, which includes Internet Explorer and Outlook/Outlook Express.  Netscape uses a different process for font embedding.
 
WEFT was designed for web pages.  The process to make an EOT for a web page differs from that to make an EOT for email.  There are tutorials at Microsoft for making EOTs for the WWW.  They currently do not have a tutorial for making EOTs for email.  With this document I hope to fill that gap.
 
This tutorial is has 4 sections: Setting up your computer for WEFT/EOT; Creating EOTs with Microsoft WEFT, Using EOTs in Outlook Express email, and FAQ's.
 
I am no expert at this, I have just been doing it for a while.  The process has gotten much easier with the latest release of Microsoft WEFT.  If you tried to make EOTs in the past and gave up in frustration, I don't blame you.  I did too.  But it's a lot easier now, and I think you'll enjoy the journey.  Let's begin:
 
 

Intro  SetUp  WEFT   OE5  FAQs
 
spacer
Section 1:
Getting Set Up 
spacer
 
FONT PROPERTIES EXTENSION:
Some font designers don't allow their fonts to be embedded. To make EOTs, you will need to check a font's properties to see if the author has allowed embedding of his font. You may do so within Windows Explorer by right clicking on any font file to check it's properties, through a third party font utility, or within WEFT itself .   This tutorial uses the WEFT program to check your fonts,  but if you would like to also install Microsoft's Font Properties Extension, do so now.
 
DIRECTORY TO STORE YOUR EOTS:
 
Make a subdirectory to story your EOTs.  It is a good idea to keep your email EOTs separate from those made for the WWW as web page EOTs may not work in email.  In this tutorial, I use a C:\WEFT subdirectory. 
 
'DUMMY' WEB PAGE:
 
WEFT will be looking for a web page to analyze when it makes EOTs.  Although this is a critical step in making EOTs for the WWW, for email EOTs we just need a 'dummy' web page to reference.  Open notepad or other text editor, copy and paste this basic HTML code:
 
<HTML>
<HEAD></HEAD>
<BODY>
Testing</BODY>
</HTML>
 
Note there is NO reference to any fonts in this dummy file.  .  Save the file as DUMMY.HTM in your C:\WEFT directory, or whatever directory that will contain your email EOTs.   Once you make this file, you will not have to alter it each time you create new EOTs, and you won't have to deal with WEFT's issues of using font-families vs. font-faces...all choices will be made within WEFT itself. 
 
 
" NEW " ADVANCED EOT FONT VIEWER:
 
Thanks to Charlie Ruland, we now have an Advanced EOT viewer, you can download a copy of it here. Once you have some EOTs, you will be able to preview the fonts created with the EOTs. This enhanced viewer offers full support for many languages, styles and font size selection. You can now choose to have the Unicode 'scalar values' displayed as well. This is useful when you want to write non-ASCII characters in HTML. It's a very useful tool and a 'must have' I might add!
 
WEFT:
You will need Microsoft's Web Embedding Font Tool (WEFT).  Earlier versions of WEFT will NOT work with this tutorial. If you don't have the WEFT RC1, released October 2, 2000, get it now.
 
Once WEFT has been installed, begin the program.
 
WEFT is configured to run the 'Wizard' on startup for new font projects.  We need do a few things before making our EOTs, so after it asks for your name and email address, stop the wizard for now.  You can always click on the Wizard button to begin making your EOTs.
 
When you first install WEFT, and when you subsequently remove or install additional fonts, WEFT recognizes that you need to update the font database.  
 
Build Font Database Dialog
 
I recommend closing all other programs while the font database is being created, or all fonts may not be included in the font database.  This process may take 15 minutes or longer if you have a large collection of fonts.
 
I have also noticed that WEFT works best recognizing fonts that were installed via the Control Panel Font installation menu.  Fonts that were just dragged and dropped into the C:\WINDOWS\FONTS folder are not always recognized as installed fonts.
 
WEFT can also create EOTs from uninstalled fonts.  If you would like to include fonts from a Zip-disk on Drive E, for example, add them to the font database via the Tools Menu.  You can actually have fonts on several removable media disks, and the WEFT database will keep track of where each off-line font is stored, as long as you have LABELED each Zip Disk differently.
 
Add Offline Fonts Menu
 
 
Once your font database has been set up, configure WEFT to remember your settings each session so you don't have to enter new information each time you begin a new WEFT session.  From the Tools>>Options Menu shown above, set your Settings as follows:
 
WEFT Settings Dialog
Finally, let's take a look at the font database and decide which font(s) to make into EOTs:
 
From the VIEW menu, choose Fonts to Embed.
 
Available Fonts Screen
 
There is a lot of information contained in this screen:
 
1.  Note the red-x's on two fonts. These fonts cannot be embedded either because the author has declared the font 'no embedding allowed' or because the font may be broken or illegally named.
 
2. Windows core fonts are in Yellow. There would be no reason to make an EOT out of a font that everyone has already.  Some other fonts may appear in Yellow if WEFT can't determine some properties of the font. Fonts in yellow are embeddable.
 
3.  If you want to see the actual font, double-click on the font.  Check closely the file size, as a large size font file will probably also yield a large EOT file as well.  Also look to see how many characters are in the font set.  Some fonts do not contain numbers, some are capital letters only, some lack punctuation.  If a character is not available for this font, a square box appears.
 
4.  The information on the right of the screen identifies whether the font is installed or not, and the location/volume name where the actual font file resides.
 
Go through the list of fonts and decide which one(s) you would like to turn into EOTs.
 
Close it now, we're ready to begin WEFTing.  
 

Top  SetUp  WEFT   OE5  FAQs
 
spacer
Section 2:  WEFT 
Making and Checking EOTs
spacer
 
1.  Begin the WEFT Wizard:
 
 
Wizard Step 1.  If you had not done so earlier, enter your name and email address.
 
Wizard Step 2:  Add Web Pages:
 
Select the dummy web page
 
Add Web Page Dialog
 
Wizard Step 3: Analyze Web Pages.
 
Make sure the 'skip analysis' box is checked and click 'Next'. 
Our 'dummy' web page doesn't have anything to analyze anyway, right?
 
Analyze Web Pages Dialog
 
 
Wizard Step 4: Choose which fonts to embed.
 
ALWAYS select Option 7, no subsetting, so that all characters in the font are available for use in your emails.
 
Fonts To Embed Dialog
 
 
Click the 'Add' button and select the font for your first EOT.  First time WEFTers, I recommend just making one EOT.  Once you are comfortable with WEFT, you can make any number of EOTs during the same session by clicking 'Add' each time and selecting another font.
 
If you select a font that has 'no embedding' properties, it will appear on your list but the 'Embed' column will be empty.
 
Note:  If you had allowed WEFT to analyze your dummy.HTM, your default windows font, such as the Times New Roman, may appear in this window.  Or you may select a font, and then decide not to use it for an EOT after all.  In either of these cases, un-select the font by highlighting it and clicking  the 'Don't Embed' button, which is located next to 'Add'. 
 
The following screen shot contains all of the above examples.  Note that two fonts will have EOTs made, I have deselected Times New Roman, and the program will not allow 4YEO IN.
 
Fonts to Embed Dialog 2
 
 
Click 'Next' to continue.
 
Wizard Step 5: Create Font Objects
First field:  "Enter the location where the font objects will be created:"  
Type in the directory you made for your email EOTs.
 
Second field:  "Font objects may only be used from pages under this root"  field: 
Click on 'Mirror Sites'.
Make sure to select MHTML as one of the choices (nothing in the field to the right), then click 'Add'
It's also a good idea to select 'File' and then type in C:\  then 'Add' so that the EOT is viewable on your C:\ drive.  Also select D:\ and E:\ if appropriate.  You don't have to have an http: entry for email EOTs.  The MHTML is critical for email EOTs.  Without this Mirror site, your EOTs will not be visible in email.
 
MHTML view
 
 
When you click 'OK' in Mirror sites, the Wizard should look something like this:
 
Create Font Objects Dialog
Make sure the "Create font declarations with relative URLs" box is checked, and the other two boxes are unchecked.
 
Click 'Next' to continue. 
 
Creating Font Objects Message
 
Possible Error Messages:
 
Sometimes WEFT will pop up a dialog box asking for your Web address.  This should no longer happen in WEFT3, but if you do get that message, enter "MHTML".
 
Sometimes WEFT will not be able to create the EOT, even though embedding was allowed.  This occurs with illegally named fonts and some complicated fonts such as dingbats.  If unable to create the EOT, the following messages may appear:
Unknown Error Message  Error Creating Font Message
If you are making more than one EOT during this session, click 'Yes' to continue.  The error messages are very general and don't tell you exactly why it could not create the EOT.   WEFT can't make EOTs out of complicated fonts such as many dingbat fonts.  Either of these error messages might appear with a complicated font or with an font containing illegal characters in its name.  There is nothing you can do to make your EOT if WEFT decides 'No'.
 
 
Wizard Step 7:  Publish Web Pages
 
This step is not critical for email EOTs so just put a check mark next to "Do not upload modified pages to my server" and click 'Next'
 
Wizard Step 8: Finished
 
Finished Dialog
 
The wizard has finished.  Click 'Finish'
 
I recommend that you DO follow the advice of the above message box and save the project as Email
FILE>>Save As -- type in "Email" and click 'Save'.  Your settings will be saved as Email.fep, and the next time you begin WEFT, the correct dummy web page and Mirror site settings will come in as your default project.
 
The Wizard has finished, and we now need to see what we made!
 
An empty  'Used Font' screen is in front of you, because our 'dummy' web page had no fonts in it.  Just click the lower of the two black-x boxes in the upper right corner to close this screen.
 
You should now see the Project Log.
The top of the log shows the date the project was started.  In the body, look under the words 'Creating EOT files'.
If there is nothing there, the EOT was not created.  An unsuccessful session would look like:
 
    -- Log Created by WEFT III (V5.3.0) on 9/12/00 at 11:09 AM
    Creating EOT files.   
 
 
In a successful EOT session, the following information will appear:
 
-- Log Created by WEFT III (V5.3.0) on 9/12/00 at 11:09 AM
 

Creating EOT files.
PAGE: {Stand alone fonts}
MIRROR SITES: file:///c|/;file:///C|/WEFT/;file:///d|/;file:///e|/;mhtml:
    --> url(file:///C:\WEFT\ACADIAN0.eot)  (Acadian™)
Saving log file at C:\My Documents\WebFontProjects\EMAIL.log


Note that I was attempting to make two EOTs.  I got an error message when processing this request, and I see that only one EOT was created.  WEFT was not able to make an EOT out of Amphibiprint, even though it was previewable and had a green check mark by it when I selected it from the font list.
 
WEFT cannot create EOTs out of complicated fonts such as Dingbat fonts.  You won't know until you try.  Sometimes it can make an EOT from  a dingbat, sometimes it can't.  There is no way to know ahead of time if WEFT can make the EOT.
 
Exit WEFT, and if you get the message below
 
No save
 
click 'No' once you have saved Email.fep once and you are happy with the settings.
 
We're done with WEFT, but we're not done with our EOT.  We need to check it and use it in a test email:
 
2. Check with Notepad and Rename your EOT.
Checking your EOT is not necessary, but is sometimes a good idea, especially if you are new to WEFT and want to make sure you created your EOT correctly CHECK your EOT, in this step make sure to MAKE NO CHANGES, JUST LOOK AND THEN EXIT.  Open notepad, then open your EOT file.  Make sure you see, very close to the top, the word MHTML. 
 
Edit EOT
 
 
 
You can also use this method to check previously made EOTs to see if they have the MHTML for emails.
 
You can also look to see what the full font name is...in this case, it's "Calligrapher".  You will want this information should you use the font family name as well as the EOT in your email.   Close notepad, making sure you DON'T save any changes if asked.  Once you close notepad, you may want to rename your EOT to the font's name
 
There are several reasons I rename my email EOTs.  First, it distinguishes email EOTs from those made for the WWW.    They are not interchangeable, so this way I don't get confused about which EOTs work in each location.  Secondly,  it's easier to figure out which font the EOT represents by just looking at the name if it is renamed.  For example, renaming CALLIGRO.EOT to Calligrapher.EOT tells me that the underlying font is Calligrapher.   Other example: SFPLANE0.EOT doesn't tell me much, but SFPlanetaryOrbiterOutline.EOT tells me exactly what the font is.  As we shall se below, there are several ways to embed EOTs in email.  Some require you use the font name as well as the EOT name.  it's simpler to just name them the same.  Again, this is a personal preference step. 
 
3. Viewer the Font created with the EOT:
 
We can also check the EOT with the Advanced EOT Font Viewer, which we have also saved in the folder that stores our EOTs.  Open the font viewer by double-clicking on it while in Windows Explorer.  Browse to the path and EOT you just created and click on 'Show Font'. 
 
Congratulations!  (I hope).  You should see your font in the test message.  Again, thanks to Charlie Ruland for creating this tool for us.  It is great!  Close the font viewer.  The EOT has been made, verified and renamed.  Let's go on to actually embedding it in an email.
 
 

Intro  SetUp  WEFT   OE5  FAQs  

 
spacer
Section 3: OE5
Using EOTs in Email
spacer
 
To use EOTs in Outlook Express, we must embedded it in an <OBJECT> tag, then used a small <SCRIPT> to show the embedded font.  As a minimum, these are the two tags that must be present in all emails that contain EOTs. 
 
We will cover several ways to use an EOT font in your OE5 stationery:
1.  Using an EOT as a default font in your stationery.
2.  Using an EOT in your stationery where it is NOT the default font.
3.  Using multiple EOTs in one stationery.  
 
In all examples, we start with the same <OBJECT> and <SCRIPT> code, but make slight modifications each time.
 
 
<OBJECT>
 
The <OBJECT> is what we use to embed the EOT in the stationery.  It was not an object made for EOTs, it is actually just a media player object that we are using as a tool to get the EOT file to embed.  The standard <OBJECT> code to use is:
 
<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A id=eot1 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="file://C:\WEFT\Calligrapher.eot">
</OBJECT>
 
Things to note in the above code:
 
~Both the opening <OBJECT> and the closing </OBJECT> tags are required.
 
~Within the <OBJECT> tag, never alter the "classid=" section.
 
~Within the <OBJECT> tag, "id=eot1" identifies this EOT as the variable "eot1".  Later on, when we embed a second EOT in the same email,  change this to  "id=eot2" in a second media player object.
 
~Within the <OBJECT> tag, the "style=" section positions the media player -800 px off  the left side of the screen so that it does not interfere with the composition of the rest of your email message.
 
~The "<PARAM NAME=" section includes both the path and the filename to the EOT file on your hard drive.  You MUST include the path as well as the filename, or the EOT will not embed.
 
~Although only the filename  "<PARAM" is shown now, once you preview or save your email, about 20 other "<PARAM" tags get added to your object code.  Don't worry about any of them, they are added by OE as the remaining default parameters for the media player object, none of which are a concern when using this object to embed the EOT.
 
 
<SCRIPT>
 
The <SCRIPT> tag contains the code to use the embedded font.  The basic <SCRIPT> code is:
 
<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: embedded; src: url("&eot1.filename&"); }</STYLE>")
</SCRIPT>
 
Things to note in the above code:
 
~Both opening <SCRIPT> and the closing </SCRIPT> tags are required.
 
~The "font-family: embedded" section is the link to the font declared within the script.  You may change the word 'embedded' to the actual font name the EOT represents.  We will be coming back to this piece of code often in the examples below.
 
~The "url()" section tells the script which media player object id and filename to use for this particular font.  Note we see the two pieces of information we included in the <OBJECT> tag -- the "eot1" from the "id=" section and the "filename" from the <PARAM>.  When we use just one embedded font, we don't have to make any changes to this part of the script.  We will be coming back here when we embed more than one EOT in an individual stationery.
 
 
Credits:  This code is not mine.  It was probably first written by Steve Cochran, the Microsoft MVP who has developed a lot of great OE utilities.  Steve's web page at: http://home.highertech.net/~scochran/ .
 
 
OK, now that we know what this code means, let's use it.
 
Start a new email message. 
 
You can put in any address, as we won't be actually sending this one out.  Put "EOT test" as the subject.
 
Make sure you are in Rich Text (HTML) mode.  (Click  Format on the Menu).  Also make sure you have the "Edit/Source/Preview" tabs available at the bottom of your new message. (Click  View on the Menu then click to place a checkmark next to Source/Edit).
 
While in the Edit tab, just type in "This is a test".
Now click on the Source Tab.
 

 
1.  THE EOT AS THE DEFAULT FONT
 
To use the EOT as the default font in your stationery, declare it in the <HEAD><STYLE> section of your email.
Copy and paste the following code somewhere in the <HEAD></HEAD> area.  If there are <STYLE> tags there already, replace them.
 
<STYLE type=text/css>
  BODY {
     font-family: embedded;
     font-size: 18pt;
      }
</STYLE>
 
Make sure a semicolon (;) separates each parameter of the style.  You don't have to have a semicolon after the final parameter and before the closing curly-bracket (}).
 
 
Next, we need to insert code at the end of the <BODY> section.  Change the path and filename in red below to that of your actual path and EOT file name.  Then, just before the closing </BODY> tag, place the following <OBJECT> code and <SCRIPT> code.  :
 
<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A id=eot1 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="file://C:\WEFT\Calligrapher.eot">
</OBJECT>

<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: embedded; src: url("&eot1.filename&"); }</STYLE>")
</SCRIPT>
 
 
With this code in place, the EOT font will be the default font.  It doesn't matter what EOT you used, since you have used the generic "embedded" word as the font in both the script and the style sheet.  The only thing that changes what EOT is used is the path and filename.
 

TESTING:
 
Click on the Preview Tab.  You should see your message first in your default email font, and then a second or two later, the EOT kicks in as the default font.
 
Did it work?  Great!  If it didn't, go back to the Source Tab and check to make sure you have the correct path and filename, and that OE had not placed any <FONT> tags around your "This is a test" section.  (<DIV> tags are OK if found there...Other <FONT face=""> tags are not).
 
Once you can see your EOT at work while in preview mode, we need to see if it will actually embedded in the email:
 
It is very important to test your email to see if the EOT embedded prior to sending it.  We need to do this before sending it anywhere.
 
Click on the Edit Tab, and then click the black box in the upper right corner to close your message.  When OE asks if you want to Save your message, click Yes.  It is now saved in your drafts folder.
 
Go to your Drafts folder, and look at the size of the message.  (If  you don't have message size as an option, right click on any of the columns that show up, select Custom, and add Size).  If your test email is only 1 or 3 KB, the font did not embed.  If it is larger, usually about 25 KB, it did embed.
 
While viewing your test message in the Drafts folder, do Ctrl-F2 to view your source code.  Use Search to find the word 'filename'.  Note that instead of C:\WEFT\Calligrapher, you now see a string of characters that begin with 'CIDxxxxxxxx'.  This is the way that Outlook Express embeds images and objects in emails.
 
When done with your test message, you may  delete it from your drafts folder.
 

Before we continue, we need to discuss the  font naming convention:
 
THREE WAYS TO SHOW THE FONT NAME:
 
1. EMBEDDED METHOD:
    'EMBEDDED' USED GENERICALLY
 
In the above example, it didn't matter what the Font was contained inside the EOT.  "Embedded" was used in both the <HEAD> and the <SCRIPT> so whatever EOT file was chosen, it would be used.  Again, the code looks like this:
 
<HTML><HEAD>
<STYLE type=text/css>
  BODY {
     font-family: embedded
;
     font-size: 18pt;
      }
</STYLE></HEAD>
 
<BODY>
text here
<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A id=eot1 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="file://C:\WEFT\Calligrapher.eot">
</OBJECT>

<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: embedded; src: url("&eot1.filename&"); }</STYLE>")
</SCRIPT>
</BODY></HTML>
 
The benefit of doing this is that it's easier.  Less code to change, and you don't have to match any real font names with it. 
 
The drawback is that several second pause for loading the EOT.  If the person who receives your email does not have that particular font on their own machine, that time gap is inevitable.  However, if they have the font, and we modify the code to the font's actual name instead of 'embedded', then their installed font is seen instantly and the EOT is not needed to view the font.
 
 
2. FONT NAME METHOD:
    CHANGE 'EMBEDDED' TO THE FONT'S REAL NAME
 
In this method, we rename the reference in the script from 'embedded' to 'calligrapher' and just use the word 'calligrapher' in the style sheet.   One of the benefits of changing 'embedded' to the actual font name is that if you have the font installed on your machine, it's easier to compose the message without having to go into the 'Source' tab to make changes.  The code for this method would look like this:
 
<HTML><HEAD>
<STYLE type=text/css>
  BODY {
     font-family: calligrapher
;
     font-size: 18pt;
      }
</STYLE></HEAD>
 
<BODY>
text here
<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A id=eot1 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="file://C:\WEFT\Calligrapher.eot">
</OBJECT>

<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: calligrapher; src: url("&eot1.filename&"); }</STYLE>")
</SCRIPT>
</BODY></HTML>
 
 
I have personally come up with more errors when I do it that  way, as I forget to rename 'embedded' or type in the font name incorrectly in the <SCRIPT> tag.  so I have started using a third system lately:
 
 
3. COMBO METHOD: 
    USE BOTH THE FONT NAME AND 'EMBEDDED'
 
To do this, you don't have to change anything in the <OBJECT> or <SCRIPT> tags. 
 
The only change is to add the name of the actual font to the line in the <STYLE> tag. 
 
HTML allows you to declare several fonts, each separated by a comma.  It will look for the first font in the list, and if not found, look for the second font, and so on.  Place the actual font first, the word 'embedded' second.  The example looks like this:
 
<STYLE type=text/css>
  BODY {
     font-family:
calligrapher,embedded
;
     font-size: 18pt;
      }
</STYLE>
<BODY>
text here
<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A id=eot1 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="file://C:\WEFT\Calligrapher.eot">
</OBJECT>

<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: embedded; src: url("&eot1.filename&"); }</STYLE>")
</SCRIPT>
</BODY></HTML>
 
If the receiver has calligrapher as an installed font, they will see that font right away.  If calligrapher is not installed, they will see their default email font for a second, then they will see calligrapher coming from the EOT. 
 
I like this method the best, as I don't have to make any changes to the <SCRIPT> tag, and it's pretty obvious to me by looking at the style sheet what the embedded font is.  I suggest you try all three ways and see what works best for you.
 
 

 
2.  THE EOT DECLARED IN A <FONT> TAG
 
Use this method if you just want a specific area of your email to contain the EOT font.   This method requires code changes in the <BODY> section of the email, not the <HEAD>.
 
Start by composing a simple test email.  Make sure it contains several lines of text like in this example:
 
Example 1 Preview
 
 
Add the standard <OBJECT> and <SCRIPT> code to the end, just before the closing </BODY> tag. (Make sure to change the path and filename to that of the EOT you are going to embed).  Don't make any changes in the  <HEAD>.
 
Now, in the part of the message that you want to have the font be the EOT font, add the <FONT> tag that says as a minimum:
 
EMBEDDED method:  <FONT face=embedded>I finally got a job!!<BR>I'll be flipping burgers!</FONT>
FONT NAME method:  <FONT face=calligrapher>I finally got a job!!<BR>I'll be flipping burgers!</FONT> (
                                        Change the <SCRIPT> tag from 'embedded' to 'calligrapher)
COMBO method:          <FONT face=calligrapher,embedded>I finally got a job!!<BR>I'll be flipping burgers!</FONT>
 
 
 
2.  MULTIPLE EOTS IN ONE EMAIL, EACH DECLARED IN A <FONT> TAG
 
 
Here is an example where TWO different EOTs are used in the <BODY> tag. 

<HTML><HEAD>
<STYLE></STYLE>
<HEAD>
<BODY bgColor=#ffffff>
<DIV>
<FONT color=brown face=embedded1 size=8>This is an example of EOT font1 </FONT><BR>
<FONT color=blue face=embedded2 size=8>This is an example of EOT font2  </FONT><BR>
<FONT color=red size=10>This shows your default email font</FONT>
</DIV>

<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A  id=eot1
style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="C:\WEFT\Bassett.EOT">
</OBJECT>

<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A  id=eot2 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="C:\WEFT\Calligrapher.EOT">
</OBJECT>
 
<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: embedded1; src: url("&eot1.filename&"); }</STYLE>")
document.writeln("<STYLE> @font-face { font-family: embedded2; src: url("&eot2.filename&"); }</STYLE>")
</SCRIPT>
 
</BODY></HTML>
 
Things to note in the above code:
 
~Each EOT has it's OWN <OBJECT> tag, with a unique "id=eotn" identifier and a different EOT file.
 
~Each EOT has it's own line of code in the <SCRIPT> tag.  That line of code references the id and filename from the corresponding Object.
 
You can add as many EOTs as you would like to email messages.  Just copy the object tags and change the object id to eot3, eot4, etc,  and add an additional line to the script for each additional font used, making sure to change both the font-family name and src url id.  But remember, each one will increase the overall size of the email.  If your recipient has a slow modem connection, it is not wise to embed too many images and EOTs in one message.
 
Well, that's it.  Happy WEFTing
 
 

Intro  SetUp  WEFT   OE5  FAQs
 
spacer
Section 4:
FAQ's
spacer
Q.  Why can't I use my email EOTs in my web pages?
A.  Because any EOTs made for the WWW must contain your web url, made  as you created the EOT.   If you are using EOTs on your web page, you will need to follow a different set of instructions to make your EOTs.  If you want to make EOTs for your web page, I suggest you check out the Microsoft tutorial for WEFT3 itself: http://www.microsoft.com/typography/web/embedding/weft3/tutorial.htm .
 
 
Q.  I have an EOT...it has the MHTML as a mirror site.  But when I use it, only a few characters appear in the EOT font.  Why?
A.  Probably because it was made with the per page 'subsetting' feature, which does not contain the full character set of your font.
 
 
Q. I am using Outlook Express 4.  Will these instructions work for me too?
A.  The instructions on Making the EOT are the same .  OE4 embedded EOTs in the <IMG> tag however, and not in the <OBJECT> tag that is used in OE5.  You might want to check out an old WEFT2 tutorial by Eric Miller.  It is obsolete in many ways with WEFT3 ,but the files he uses to embed the EOTs were made for OE4 stationery:  His site is: http://www.okinfoweb.com/moe/format/format_007.htm
 
 
Q.  How come I don't have to use HACKEOT.EXE any more?
A.  It was not until the 3b7 beta version of WEFT 3 that the ability to select 'MHTML' as a Mirror site was available.  This is the critical Mirror site that is needed for EOTs to be used in Outlook Express email.  Prior to this, email EOTs had to be 'hacked' by hand or via this nice (but now obsolete) little program written by Steve Cochran.  You can check out his site at http://chattanooga.net/~scochran/ .
 
 
Q.  I'm quite a techno-geek.  Where can I get detailed information on this WEFT stuff?
A.  Try the Microsoft Development Networks online workshop:   http://msdn.microsoft.com/workshop/c-frame.htm?/workshop/author/default.asp .  Remember that a lot of this stuff is for web page EOTs, not email EOTs.  Don't let them confuse you! :-)
 
Q.  Can Netscape users see EOT fonts?
A.  No.  Netscape uses a diferent type of embedded font  file called .PFR.  Internet Explorer users would have to download an activeX component to view these fonts.  For more information on Bitstream Fonts, go to http://www.bitstream.com/categories/products/webfonttools/index.html
 
 
Q.  I made an EOT but when I use it, only the letters show up.  The numbers and puncuation marks show up as boxes.  What went wrong?
A.  Nothing.  Go back to the actual font file you used to make the EOT.  Double click on it, and look to see what characters are available with that partcular font.  Some fonts only contain all the characters, some are missing numbers, punctuation marks, and so on.  If the font doesn't have all the characters available in .TTF format, the EOT won't have them either.
 
 
Q. What is the Object and Script code that I have to use to embed EOTs?
A. (text in black is there for positioning reference)  (text in red is changeable..see the tutorial for specific details)
 
<HTML><HEAD>
<STYLE type=text/css>
  body {
     font-family: embedded;
     font-size: 18pt;
      }
</STYLE>
</HEAD>
<BODY>
text here
<OBJECT classid=clsid:05589FA1-C356-11CE-BF01-00AA0055595A id=eot1 style="LEFT: -800px; POSITION: Absolute">
<PARAM NAME="Filename" VALUE="file://C:\WEFT\Calligrapher.eot">
</OBJECT>
<SCRIPT language=VBScript>
document.writeln("<STYLE> @font-face { font-family: embedded; src: url("&eot1.filename&"); }</STYLE>")
</SCRIPT>
</BODY></HTML>
 
 

A note from the author:

"Other will be added when you ask more questions LOL
I hope this tutorial has been helpful to you.  Please email me with feedback, comments, or suggestions on how to make this less confusing.
Thanks, Cheryl"

Feedback

This Tutorial has been provided by Fluttrby Designs ©
as an effort to share with others instruction and information on Embedding Fonts into E-Mail applications.
Full permission for posting this tutorial
from the Author: Cheryl Soshnik has been granted to Fluttrby Designs © .
All Questions & Comments regarding this tutorial need to be directed to her.

Thank You very much Cheryl, this is well written and illustrated! :o)

Special Thanks go to Charlie Ruland for his efforts in creation of the
New "Advanced" EOT Font Viewer and the generosity to pass it along for us all to enjoy! :o)


Intro  SetUp  WEFT   OE5  FAQs

Previous Page

 

Fluttrby Designs © 2000 ~ 04