When I include special characters in my annotation it fails. How can I fix this?

Modified on Wed, Oct 2, 2024 at 3:37 PM

The issue occurs because the annotation by default uses Arial font family, and the PrizmDoc microservice that burns the annotation does not see the Arial font in the container. As a result, it maps Arial to the PDF's predefined Helvetica font, which only supports limited ANSI encodings.

This does not include characters such as § or £. In fact, prizmdoc-server container does contain more fonts, including Arial, but they are currently not visible to the microservice that burns markup out of the box.

We recommend you create an additional Docker layer over the prizmdoc-server container that would make those additional fonts visible to the burning process, using the following Dockerfile:

FROM accusoft/prizmdoc-server:14.0

RUN ln -s /usr/share/prizm/modules/poppler/fonts/* /usr/local/share/fonts & \
    fc-cache -f -v

Save the above script into a file name "Dockerfile"
Run this command in the directory you saved the dockerfile to build a Prizm Image with the modifications to link the necessary font: docker build --tag 'image_name'
Run the new container using the same commands as you would against a normal Prizm container to setup the config and start the container. For updating the image in the future, you can change the version tag in the first line of the script and remake the modified image.