When designing user forms in DriveWorks Administrator it is important to use fonts that are available on all machines your projects are to be specified on.
Many applications install fonts by default, so what is available on your machine may not be available on others.
This is particularly necessary when using DriveWorks Live, where many device types and operating systems are used.
The table below lists the most commonly used fonts available on Windows (Windows 7 or newer) operating systems.
Using any of these fonts will ensure your forms display correctly when specifying on any machine with a DriveWorks client module (Administrator, User or Autopilot).
When using any other font, please make sure it is installed on each machine using the project.
Arial | Georgia | Sitka Banner |
Calibri | Impact | Sitka Display |
Cambria | Lucida Console | Sitka Heading |
Cambria Math Regular | Lucida Sans Unicode | Sitka Small |
Candara | Microsoft Sans Serif | Sitka Subheading |
Comic Sans MS | Palatino Linotype | Sitka Text |
Consolas Regular | Segoe MDL2 Assets | Tahoma |
Constantia | Segoe Print | Times New Roman |
Corbel | Segoe Script | Trebuchet MS |
Courier New | Segoe UI | Verdana |
Franklin Gothic | Segoe UI Emoji | Webdings |
Gabriola | Segoe UI Symbol | Wingdings |
However, when using DriveWorks Live your projects can be specified on any type of device or operating system. These may not have the same fonts installed.
When a browser loads a DriveWorks form it will try and find the font used on the clients machine or device. If the font is not found it will fallback to the default font declared in the .css for the page being loaded.
The .css will list the fallback font in order of preference, usually ending with a font-family name that all browsers are aware of.
The only way to ensure a non-standard font is displayed correctly is to embed the font into the .css (see Non-Standard Fonts below).
The table below lists fonts that are standard to Windows and Mac systems along with the fallback font-family name used for other devices.
Windows | (Mac) OS X | font-family |
---|---|---|
Arial | Arial | sans-serif |
Courier New | Courier New | monospace |
Georgia | Georgia | serif |
Palatino Linotype | Palatino | serif |
Times New Roman | Times New Roman | serif |
Trebuchet MS | Trebuchet MS | sans-serif |
Verdana | Verdana | sans-serif |
Non-standard fonts need to be embedded in the .css used to display fonts.
If you are using DriveWorks Live, and have already customized the Skin (in line with the instructions given in the section Skin Customization in the topic Customize the Web Theme - Advanced), follow the instructions below from step 3.
If you are using DriveWorks Live without any customizations follow all the steps below:
This is located at: C:\ProgramData\DriveWorks\[version number]\Live\Themes\Web\content\system\skins
This should be copied to the location:
C:\ProgramData\DriveWorks\[version number]\Live\Themes\Web\content\custom\skins
This is located at: C:\ProgramData\DriveWorks\[version number]\Live\Themes\Web\content\system
This should be copied to the location:
C:\ProgramData\DriveWorks\[version number]\Live\Themes\Web\content\custom
If the font is installed on your computer it can be found by:
This should be copied to the location:
C:\ProgramData\DriveWorks\[version number]\Live\Themes\Web\content\custom\fonts
@font-face { font-family: 'My Font Name'; src: url('/content/custom/fonts/My-Font-File-Name.ttf'); font-weight: 700; font-style: normal; }
For example the skin.font.css file may contain the line:
font-family: 'Open Sans';
Add the Font Name immediately after font-family: so it looks like:
font-family: 'roboto light', 'Open Sans';
The skin.font.css should look like the image below
If your embedded font doesn’t display, use the developer tools in your browser to inspect what font name the browser is expecting. You can then amend your font.skins.css file.
When running DriveWorks Live through IIS, recycle the Application Pool to ensure that any cached files are removed and the new embedded font is displayed.
Knowledge Base Article Ref: | KB16051701 |
---|