Incorrect encoding when exporting to pdf

[ishaulov]

Attempted Debugging

• I have read the debugging page

Searched GitHub Issues

• I have searched GitHub for the issue.

Describe the Scenario

Hi! When exporting a document in PDF format, the encoding of the headings breaks: in Cyrillic, I see "?????" instead.
I searched for a solution on Github, but couldn't find one. Please, help me: what's wrong and what can be fixed?

Exact BookStack Version

BookStack v25.07

Log Content

Hosting Environment

Ubuntu 22.04,
PHP 8.3.19,
~# locale
LANG=ru_RU.UTF-8
LANGUAGE=
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=

[shmbatom]

I met this truoble too, but I don't know how to solve it.

[zhang-nianqiang]

BookStack uses dompdf as the PDF export engine.
You can find a solution at https://github.com/dompdf/dompdf?tab=readme-ov-file#about-fonts--character-encoding.

[shmbatom]

To zhang-nianqiang
You should give detail link, and we all know that bookStack uses dompdf as the PDF export engine.
What you given is unuseful.

[Ozilly]

Switching to WKHTMLTOPDF helped me

[Alexandr-Falcon99]

Переход на WKHTMLTOPDF мне помог.

I confirm this statement.

[hillw3318-ui]

I am using the docker version of BookStack (from the linuxserver repository). In my case, the problem was only with the header. So, I go to the container:

docker exec -it bookstack_app /bin/bash

then inside the container, I looked at the existing fonts:

fc-list

and saw Free Serif.

Then I just set Custom HTML Head Content to:

<style>
  * {
    font-family: 'Free Serif', free-serif !important;
  }
</style>

and PDF Export works correct.

[ssddanbrown]

I believe this was caused by the issue addressed in #6069.
The fixes for that will be part of the next feature release.

Feel free to request this to be opened if still experiencing issues after upgrading to the next feature release (once it becomes available).