Thai Names are not being created properly in Finding Aid PDF.

Description

Resources with Agents with Thai names and diacritics display properly in ASpace but when PDF finding aid report is created, they are incorrect.
For example,
Saphā Kānsưksā hǣng Chāt (Thailand)
is in the PDF as
Saph# K#ns#ks# h#ng Ch#t (Thailand)

I presume this is true for other languages.

Environment

None

Activity

Show:
Christine Di Bella
January 28, 2019, 5:07 PM
Edited

The general version of this issue is already in the prioritized queue (see https://archivesspace.atlassian.net/browse/ANW-758), so I'm closing this as a duplicate, but linking for the important context.

Ed Busch
January 24, 2019, 6:49 PM

Per Adam Jazairi
This is a problem with the fonts included in the version of Apache FOP that ASpace uses. There's an open ticket here: https://archivesspace.atlassian.net/browse/ANW-473

We've encountered the same issue when we attempt to generate a PDF finding aid containing Irish or Japanese diacritics. An interim solution we've been using is to export the EAD, then run Saxon on it to generate an FO file, then run FOP 1.0 with the appropriate font on the FO file to generate the PDF. It's a bit cumbersome, but it's worked for us so far.

Here's the FOP conf file that we use: https://github.com/BCDigLib/bc-aspace/blob/master/fop/fop.xconf

The only catch is that you'll need a font that supports the unicode characters you need. In your case, it looks like Arial v2.95 would work: https://en.wikipedia.org/wiki/Arial#TrueType/OpenType_version_history

Duplicate

Assignee

Unassigned

Reporter

Ed Busch

Labels

None

Priority

Major