Skip to main content
Skip table of contents

Asian fonts support for direct print

This article explains how to fix documents that are unreadable after printing due to missing fonts (particularly Asian fonts). This may happen if a PDF is uploaded to SAFEQ Cloud via public API. This solution is not applicable to the situation where a user submits the PDF document via the SAFEQ Cloud Client and the document is flattened and converted to PDF/A.

Background information

Once a print job is submitted via public API, the Primary or Secondary servers convert it. The goal is to convert any print job to PDF format. If the submitted job is a PDF already, the conversion process will leave it as is and the file will be spooled in the original format. When the job is released using direct print, another service converts it to the Postscript format. Sometimes, the printed document lacks certain fonts. Typically if the original contains Asian languages. You can solve this issue by adding the fonts into the operating system for your Primary or Secondary server and providing a configuration file for the Xpdf converter.

Solution for CentOS (RHEL)

Due to many languages ​​and distributions, we only provide support for the most used platform - CentOS (RHEL). Packages and configuration can also be customized based on the customer's needs.
  1. Check whether the CMap package is installed by running the following command:

    rpm -q poppler-data
  2. If it isn't, install it.

    sudo yum install poppler-data
  3. Install the required fonts, for example, Google Noto fonts. Note that the Xpdf converter does not support ttc (true type collections) such as google-noto-cjk. Use only otf or ttf format. Example:

    sudo yum install google-noto-sans-japanese-fonts
    sudo yum install google-noto-sans-korean-fonts
    sudo yum install google-noto-sans-traditional-chinese-fonts
    sudo yum install google-noto-sans-simplified-chinese-fonts
  4. Prepare the xpdfrc configuration file for Xpdf converter. This file must have the following structure:

    #----- begin Japanese support package
    cidToUnicode    Adobe-Japan1    /usr/share/poppler/cidToUnicode/Adobe-Japan1
    unicodeMap      ISO-2022-JP     /usr/share/poppler/unicodeMap/ISO-2022-JP
    unicodeMap      EUC-JP          /usr/share/poppler/unicodeMap/EUC-JP
    unicodeMap      Shift-JIS       /usr/share/poppler/unicodeMap/Shift-JIS
    cMapDir         Adobe-Japan1    /usr/share/poppler/cMap/Adobe-Japan1
    toUnicodeDir                    /usr/share/poppler/cMap/Adobe-Japan1
    fontFileCC      Adobe-Japan1    /usr/share/fonts/google-noto/NotoSansJP-Regular.otf
    #----- end Japanese support package
    • You can download the file here.

    • Or from Y Soft CDN using the following command:

      sudo wget

      In this case, we use mapping to the poppler-data resources. As conversion fonts, we use installed NotoSans regular otf versions.

  5. Place the xpdfrc file in the /etc/ folder.

  6. Set the permissions for the file to 644 at minimum.

    sudo chmod 644 xpdfrc

For Xpdf configuration in general, see

For Xpdf language support, see

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.