Skip to main content

Improve your HTML(5) websites with @font-face

For a long time web designers were limited to a very small set of “web safe” fonts. Anything beyond those fonts, had to be done through images. Images for text not only meant creating and maintaining dozens (if not hundreds) of images, but it introduced accessibility issues.

@font-face to the rescue

With the introduction of @font-face in 1998(!)  in the CSS 2 specification, web designers could link to actual font files via CSS:

@font-face 
{     
font-family: "ChunkFiveRegular"; 
src: url('Chunkfive-webfont.ttf') 
format("truetype"); 
}

And then utilize those specified fonts in style declarations:

h1 
{     
font-family: "ChunkFiveRegular", serif;
}

However as the specification was there, the browser support wasn’t.. And then each browser vendor decided to support different, rarely-used formats. Plus, there were the licensing issues. Even if you had supported font formats, that didn’t mean you could legally use those fonts with @font-face.

Browser Support Today

Today all of the latest browsers support @font-face and many more file formats are supported, including the TrueType/OpenType TT (.ttf) and OpenType PS (.otf) formats. Unfortunately, “latest” doesn’t include Internet Explorer before version 9.


  .ttf .otf .woff .svg .eot
Chrome v4+ v4+ v6+    
Firefox v3.5+ v3.5+ v3.6+    
Internet Explorer v9   v9 v9 v4+
Opera v10+ v10+   v10+  
Safari v3.1+
 v3.1+
   SafariMobile iOS 4.1+  

Licensing Support Today

Before you can dive into the wonderful world of @font-face, you first need to choose a font. And not just any font, but a font that is licensed for web use.

There are many free and commercial fonts that have web licenses, making it easy for you. Some of the top sites when looking for a properly licensed font:

Some fonts, you can download and host yourself, others you can only use hosted versions. If you already have a font that is licensed for web use, for example, you can save it to your web server and reference those files in your CSS.

Looking for more information and some sample code? Have a look at this post by Emily Lewis.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more