Suitcase Fusion 3 User Guide for Mac OS - Extensis
Suitcase Fusion 3 User Guide for Mac OS - Extensis
Suitcase Fusion 3 User Guide for Mac OS - Extensis
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
A Simple CSS Example<br />
This shows exported WebINK CSS followed by a typical style assignment.<br />
@font-face {<br />
font-family: BigDaddy;<br />
src: url('http://fnt.webink.com/wfs/?drawer=00000000-0000-0000-0000-<br />
00000000&font=FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFF'); }<br />
h1 {<br />
font-family: BigDaddy, "Arial Black", sans-serif;<br />
font-size: 40px; }<br />
By including fallback fonts in the h1 definition, you determine how the website will look if the WebINK font is not<br />
available (<strong>for</strong> example, if the browser visiting your site doesn’t support @font-face).<br />
Why So Many Faces?<br />
The WebINK CSS includes a CSS @font-face entry <strong>for</strong> each font in your Type Drawer. If you include a font<br />
family that has bold, italic, and bold-italic variants on top of a regular typeface, the exported WebINK CSS will<br />
have four @font-face entries.<br />
You might be tempted to manually link them all to the same font-family and add values <strong>for</strong> font-style and<br />
font-weight descriptors. While ideally this would greatly simplify your CSS, the reality of the situation is that<br />
some popular browsers do not correctly support this type of style linking.<br />
For the <strong>for</strong>eseeable future, we recommend that you use the individual @font-face entries in the WebINK CSS<br />
to avoid issues with some browsers.<br />
You can easily modify the tag definitions in your style sheet to accommodate these browser shortcomings.<br />
Example WebINK CSS<br />
The following is CSS from WebINK <strong>for</strong> a font named “Grotesque” that has bold, italic, and bold-italic variants.<br />
@font-face {<br />
font-family: GrotesqueB;<br />
src: url('http://fnt.webink.com/wfs/?drawer=00000000-0000-0000-0000-<br />
00000000&font=FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFF'); }<br />
@font-face {<br />
font-family: GrotesqueBI;<br />
src: url('http://fnt.webink.com/wfs/?drawer=00000000-0000-0000-0000-<br />
00000000&font=FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFF'); }<br />
@font-face {<br />
font-family: GrotesqueI;<br />
src: url('http://fnt.webink.com/wfs/?drawer=00000000-0000-0000-0000-<br />
00000000&font=FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFF'); }<br />
@font-face {<br />
font-family: GrotesqueReg;<br />
src: url('http://fnt.webink.com/wfs/?drawer=00000000-0000-0000-0000-<br />
00000000&font=FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFF'); }<br />
Modified CSS tags<br />
Here are some CSS tags <strong>for</strong> the above @font-face elements, modified to utilize multiple font-family<br />
definitions. Note the definitions <strong>for</strong> combined tags; if you use the combination <strong>for</strong> bold italic text, you<br />
will need to define that combination, and likewise if you use the reverse notation . By defining this<br />
combination to use the actual bold-italic variant of the font, you avoid having the operating system or browser<br />
attempt to create its own variant from the base font (which usually has less than desirable results), or worse, in<br />
the case of some browsers, fall back to using the plain font.<br />
body { font-family: GrotesqueReg, Arial, sans-serif; }<br />
em { font-family: GrotesqueI, "Arial Italic", Arial-ItalicMT, Arial, sansserif;<br />
}<br />
i { font-family: GrotesqueI, "Arial Italic", Arial-ItalicMT, Arial, sansserif;<br />
}<br />
strong { font-family: GrotesqueB, "Arial Bold", Arial-Bold, Arial, sans-serif; }<br />
- 91 -