Custom Fonts

PDF files are supposed to be rendered exactly the same, no matter which PDF viewer you’re using. One reason why this is the case is because a PDF file can embed the fonts required to render it.

However, sometimes — due to size reasons or other considerations — fonts are not embedded, which makes the PDF viewer look for fonts on the current system. Depending on the fonts that are available, this can cause rendering problems.

While the best option is to always embed the fonts in the PDF, this isn’t always possible, especially if you’re working with third-party PDF files. This is where custom font path support comes in.

iOS comes with a relatively complete set of fonts, so it usually isn’t necessary to add a custom font path, except in special circumstances. We provide an example of how to properly do this in our SDK DMG file found in Examples/CustomFontPath.

The important part is supplying the extra font path when setting the license using the PSPDFAdditionalFontDirectories option:

Copy
1
2
3
let additionalFontDirectory = Bundle.main.bundleURL.appendingPathComponent("AdditionalFonts", isDirectory: true).path
let options = [PSPDFSettingKey.additionalFontDirectories: [additionalFontDirectory]]
PSPDFKitGlobal.setLicenseKey("YOUR_LICENSE_KEY_GOES_HERE", options: options)
Copy
1
2
3
NSString* additionalFontDirectory = [[NSBundle.mainBundle bundleURL] URLByAppendingPathComponent:@"AdditionalFonts" isDirectory:YES].path;
NSDictionary<PSPDFSettingKey, id>* options = @{PSPDFAdditionalFontDirectories: @[additionalFontDirectory]};
[PSPDFKitGlobal setLicenseKey:@"YOUR_LICENSE_KEY_GOES_HERE" options:options];

This should be done as early as possible in the application’s launch process, like in application(_:willFinishLaunchingWithOptions:). You can read more about when to set the license key in Adding the License Key.

The font directory can be any directory that is accessible to your app, and all .ttf, .ttc, and .otf files will be added to the font list of PSPDFKit.

Microsoft Core Fonts

According to Wikipedia:

“Core fonts for the Web was a project started by Microsoft in 1996 to create a standard pack of fonts for the World Wide Web. It included the proprietary fonts Andalé Mono, Arial, Arial Black, Comic Sans MS, Courier New, Georgia, Impact, Times New Roman, Trebuchet MS, Verdana and Webdings, all of them in TrueType font format…”

While Microsoft no longer offers these files directly, they can be legally downloaded. The EULA prohibits redistribution, but you can download them and add them to our Server product via the Custom Fonts feature. You can use free software such as 7-Zip to extract the .TTF font files from the downloaded packages.

These fonts are widely used on the web and PDF files and will improve render fidelity for PDF documents that use them.