Skip to main content
Mitratech Success Center

Appendix- Installing Fonts on Linux-Unix Reports

For some organizations, customized or third-party font typefaces are required for reports generated in Suite. This document is a guideline rather than the specific procedure(s) to install fonts.

The Challenge: Each Unix and Linux distribution (such as Oracle Solaris, Red Hat Linux Enterprise, SUSE Linux Enterprise, Canonical Ubuntu Server, etc.), requires a different procedure to install custom fonts. The font packages may have different names based on the Linux distribution in use. Additionally, each Linux distribution provides a different package management system, and may or may not provide a Graphical User Interface (GUI) front-end to the package management system.

For these reasons, Mitratech can only provide a logical procedure to install custom fonts. It is also imperative that your organization’s Linux (or Unix) administrative staff perform the font installation, as additional steps may be required beyond the scope of installing font packages.

Identify and Acquire Font Packages Required

Mitratech testing indicates the following TrueType font packages should be installed:

Font Family Name

Font CAB Filename

Embedded Font File(s)






arial.ttf, ariali.ttf, arialbd.ttf, arialbi.ttf

Arial Black



Comic Sans MS


comic.ttf, comicbd.ttf

Courier New


cour.ttf, courbd.ttf, courbi.ttf, couri.ttf



georgiaz.ttf, georgiab.ttf, georgiai.ttf, georgia.ttf




Times New Roman


times.ttf, timesbd.ttf, timesbi.ttf, timesi.ttf

Trebuchet MS


trebuc.ttf, trebucbd.ttf, trebucbi.ttf, trebucit.ttf



verdanab.ttf, verdanai.ttf, verdanaz.ttf, verdana.ttf




Download Font Files

The font (CAB) files are available with the same base HTTP URL, with the difference being the server where the files are located. The available servers are: jaist, voxel, heanet, kent, nchc, easynews, waix, internode, internap; and the base URL is:

http://<server name> For example, the URL for the font files stored at server “jaist” would be:

The server list is provided because some servers may be offline. Simply change the “server name” to one of the nine names listed above.

Unpack and Copy the Font Files

The font files are actually Microsoft-format CAB files with an “EXE” extension. CAB files are similar to ZIP files—one of more files are compressed and stored in a single file. Each of the CAB files will contain one or more TrueType (“TTF” extension) font files (as listed in the previous table). Most modern compression utility programs (WinZip, 7Zip, etc.) can read and extract the contents of a CAB file.

If extracting the TTF files on a Microsoft Windows computer, a compression utility should be used to extract the TTF files. Selecting the file while in Microsoft Windows Explorer will result in the execution of the font executable, thereby installing the font(s), which is not the desired result.

To extract the CAB files on a Linux system, the “cabextract” utility is required. This utility is available as different packages at the servers listed in the previous section. For example, to view the available “cabextract” packages at the “jaist” server, the URL is:

Install the desired “cabextract” package per the Linux distribution package manager. Usage for “cabextract” is simple—supply the CAB filename to the “cabextract” utility, such as:

$  cabextract arial32.exe Extracting cabinet: arial32.exe
extracting: FONTINST.EXE extracting: fontinst.inf extracting: Ariali.TTF
extracting: Arial.TTF
Finished processing cabinet.

To execute the “cabextract” utility for all the CAB files, a wildcard can be used:

# cabextract *.exe

After all the TTF files have been extracted from their CAB files, all the TTF files must be copied to the appropriate font subdirectory. It is recommended to change the filename case for all the TTF files first. For example, at a command line, the following can be executed:

# for i in *; do mv -f "$i" `echo "$i" | tr A-Z a-z`; done

The resulting “[…] are the same file” messages can be ignored.

Finally, the files should be coped to the Linux system’s well-known font subdirectory. It is recommended that a subdirectory be created where the Microsoft fonts will be stored, such as: /usr/share/fonts/ms.

The example below is an excerpt from the Red Hat Linux Enterprise 6 documentation ( International_Language_Support_Guide/add_fonts_all_users.html). This example should not be considered as comprehensive or that this procedure will work on all installed instances of Red Hat Linux Enterprise 6, or any other Linux (or Unix) distribution. Adjust the commands and font subdirectory location names as appropriate.

Adding New Fonts for All Users

To install fonts for all users you need to login as root (or administrator account) and create a directory under: /usr/share/fonts/ (for example, /usr/share/fonts/ms).

Copy the fonts into the subdirectory created and execute the following to update the font cache:

# cp *.ttf /usr/share/fonts/ms
# fc-cache -v -f /usr/share/fonts/
/usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs
/usr/share/fonts/default: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/default/Type1: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/default/ghostscript: caching, new cache contents: 17 fonts, 0 dirs
/usr/share/fonts/dejavu: caching, new cache contents: 21 fonts, 0 dirs
/usr/share/fonts/khmeros: caching, new cache contents: 3 fonts, 0 dirs
/usr/share/fonts/kurdit-unikurd-web: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/liberation: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/ms: caching, new cache contents: 30 fonts, 0 dirs
/usr/share/fonts/opensymbol: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/smc: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/stix: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/un-core: caching, new cache contents: 2 fonts, 0 dirs
/var/cache/fontconfig: cleaning cache directory fc-cache: succeeded

All existing and new users should now be able to use the installed fonts.


  • Was this article helpful?