What is the difference between a Desktop-Font and a Web-Font?

A desktop font is designed to be installed on your computer for use with applications such as Microsoft Word or Adobe InDesign. Desktop fonts often have special OpenType features that give the user flexibility in designing with them. Webfonts are for one specific domain and will be delivered in Webfont formats WOFF, WOFF2 and TTF. EOT and SVG are obsolete and will only be made available on request.

 

A small test to document the web suitability of your browser: (with special thanks to Andreas Seidel)
If you see .ttf or .woff2 or .woff or .eot or .svgz or .svg supported picture above, your browser supports WebFonts in principle and you will see what taste your browser prefers. If you only see one dot, your browser cannot integrate WebFonts or if this option is deactivated in the browser. Then you won't see any fonts on my website - which would be a pity...

A webfont is a specially tuned font for use on websites using the CSS @font-face declaration. The PreussType-WebFonts have no OpenType features and often have extraneous glyphs removed (especially in default WebFonts [e.g. PreussType [STD] fonts).

 

The single license of PreussType Webfonts costs so as much as a normal PreussType [STD font].
The Webfont license is issued on a specific domain and unlimited access.

 

A webfont comes in different flavors. A WOFF file (for all newer browsers), an WOFF2 file (for all recent and future browsers) and an TTF file (for Microsoft-Browser above IE8, Android, iOS ...). Each one is designed to target different browsers. You will need all files when using webfonts to build a website. If you need for your Web presence Webfonts with extensions with OpenType features and/or other languages, don't be shy please, to get in contact with us. I am the specialist...

Our web font license does not allow you to use other font formats besides those offered by us. Font replacement techniques such as Cufon or typeface.js are also not allowed.

 

PreussType web fonts are NOT licensed for desktop use; they are only licensed for hosting on your web server.

 

Installing Webfonts

1. Include the webfont stylesheet

A special CSS @font-face declaration helps the various browsers select the appropriate font it needs without causing you a bunch of headaches. Learn more about this syntax by reading the Fontspring blog post about it. The code for it is as follows:

@font-face {
    font-family:"MyWebfont";
    src:url("MyWebfont.woff2") format("woff2"),      /* Modern and future Browsers */
        url("MyWebfont.woff")  format("woff"),       /* Newer Browsers */
        url("MyWebfont.ttf")   format("truetype");   /* IE 9+, Android, Safari, iOS */
}

EOT and SVG are obsolete and are no longer supported by us. If you still need these formats, please contact us.

2. Modify your own stylesheet

To take advantage of your new fonts, you must tell your stylesheet to use them. Look at the original @font-face declaration above and find the property called "font-family." The name linked there will be what you use to reference the font. Prepend that webfont name to the font stack in the "font-family" property, inside the selector you want to change. For example:

p { font-family: 'MyWebfont', Arial, sans-serif; }

3. Test

Getting webfonts to work cross-browser can be tricky. Use the information in the bottom to help you if you find that fonts aren't loading in a particular browser.

Troubleshooting - Font-Face Problems

Having trouble getting your webfonts to load in your new website? Here are some tips to sort out what might be the problem.

Fonts not showing in any browser

This sounds like you need to work on the plumbing. You either did not upload the fonts to the correct directory, or you did not link the fonts properly in the CSS. If you've confirmed that all this is correct and you still have a problem, take a look at your .htaccess file and see if requests are getting intercepted.

Fonts not loading in iPhone or iPad

The most common problem here is that you are serving the fonts from an IIS server. IIS refuses to serve files that have unknown MIME types. If that is the case, you must set the MIME type for SVG to "image/svg+xml" in the server settings. Follow these instructions from Microsoft if you need help.

Fonts not loading in Firefox

The primary reason for this failure? You are still using a version Firefox older than 3.5. So upgrade already! If that isn't it, then you are very likely serving fonts from a different domain. Firefox requires that all font assets be served from the same domain. Lastly it is possible that you need to add WOFF to your list of MIME types (if you are serving via IIS.)

Fonts not loading in IE

Are you looking at Internet Explorer on an actual Windows machine or are you cheating by using a service like Adobe BrowserLab? Many of these screenshot services do not render @font-face for IE. Best to test it on a real machine.

Fonts not loading in IE

IE9, like Firefox, requires that fonts be served from the same domain as the website. Make sure that is the case.

 

Language Support

The subset of PreussType STD-Fonts in this kit supports the following languages:
Afrikaans, Albanian, On, Basque, Bemba, Bena, Chiga, Congo Swahili, Danish, German, English, Estonian, Faroese, Filipino, Finnish, French, Galician, Gusii, Indonesian, Irish, Icelandic, Italian, Kabuverdianu, Kalenjin , Cornish, Luo-language Machame, Makhuwa-Meetto, Makonde, Malagasy, Malay, Manx, Mauritian Creole, Dutch, Northern Ndebele, Norwegian Bokmål, Norwegian Nynorsk, Nyankole, Olulujia, Oromo, Portuguese, Romansh, Rombo , Kinyarwanda, Rundi, Rwa, Samburu, Sango, Sangu, Swedish, Swiss German, Sena, Shambala, Shona, Soga, Somali, Spanish, Swahili, Taita, Teso, Vunjo, Zulu

Glyph Chart

The PreussType STD-Fonts includes all the glyphs listed below. Unicode entities are included above each glyph to help you insert individual characters into your layout. Further details into the PDF specification.