eb onts

The usual advice is to use only web-safe fonts on web sites because unless site visitors have the same font installed they won’t be able to see the web page as you designed it. This is no longer true for modern browsers like Opera, Firefox, and Vivaldi.

Font embedding hosts fonts on the web site. Users can see the text using the font with which it was designed. The @font-face tag tells browsers where to find the font, and it is downloaded to display the page. WebPlus x8 will add suitable code automatically and upload a copy of the font to the wpscripts folder.

@font-face { font-family: 'Odana'; src: url('wpscripts/wpce31d242.ttf'); font-weight: bold;}

In earlier versions of WebPlus one can add suitable code manually and upload the font to the server. This is better as it allows the use of compressed web fonts, but it also requires some knowledge of coding. WebPlus x8 makes it easy for novices.

@font-face {font-family: "Kabala"; src: url("http://www.softerviews.org/WebFonts/Kabala Regular.woff") format("woff");}

The benefits are that the designer has much greater freedom to choose any font with the requisite licensing rights instead of being restricted to a dozen or so web-safe typefaces.

Another benefit is that the designer can ensure that extended characters or special symbols are available. Using Pāḷi or Burmese on web sites has always been a problem because one cannot be sure that all readers will have a suitable font. One can offer a font for down­loading, but then the user has to download and install the font to read the site. With web fonts, this is all done automatically without any intervention from the user.

My fonts contain a lot of symbols. If you use web fonts, these will be displayed as text, without any loss of quality at large sizes or on high-resolution displays.



96 DPI Image 200 DPI Image