PDF Does Not Render Non-Latin Characters


When generating a PDF from ArchivesSpace, if a character outside of the standard Serif font family is present, it will render as "#" in the output.

For example, the following term:
Teʼaṭron "ʻInbal"

is rendering as:
Te#a#ron "#Inbal"

Unfortunately, I believe that the base 14 PDF fonts do not support the full Unicode plane, so the solution may require embedding extended fonts within ArchivesSpace's FOP.




Christine Di Bella
April 29, 2020, 2:14 PM

To reduce confusion and since the staff side solution was merged in 2.7.1, I'm closing this issue and have made a new one for the public PUI PDF. Further comments should be added to ANW-1075.

Brittany Newberry
April 23, 2020, 1:18 PM

Tested on test site and I get the same results as Joshua. The staff interface pdf shows the non-Latin characters and the public interface pdf omits them

Joshua Shaw
April 14, 2020, 1:14 PM

This appears to be fixed in the SUI, but not in the PUI which just omits the non-latin characters. See attached PDFs.


Christine Di Bella
February 24, 2020, 1:58 PM

Significant improvements for this went into v2.7.1 thanks to . Since it sounds like more needs to be done, I'm leaving this open pending analysis of the additional work to be done and determination of whether that can be a separate/new issue.

Laney McGlohon
October 23, 2019, 1:20 PM

was a good start but need to continue to enhance fonts for PDFs -



Alexander Duryee


Alexander Duryee

Fix versions