makeplane / makeplane/plane

[bug]: PDF export does not embed CJK fonts in the page.

Open
#8,567 2 comments 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Jan 21, 2026.

🐛bug plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior

PDF export does not embed CJK fonts.
On Linux / Chromium-based PDF rendering, Chinese characters are garbled.
Please add Noto Sans CJK (or equivalent) and ensure font embedding.

Steps to reproduce

Open Plane.

Navigate to Pages.

Create a new Page or open an existing Page.

Add Chinese characters to the Page content, for example:

Page title

Paragraph text

Bullet lists or headings

In the Page view, click Export → PDF.

Download and open the exported PDF file.

Expected behavior

All Chinese characters in the Page are rendered correctly in the exported PDF.

The PDF content matches what is displayed in the Plane web UI.

Actual behavior

Chinese characters in the exported PDF are:

Garbled

Rendered as squares or some weird symbol(□ / ▢)

Or missing entirely

Non-Chinese (Latin) text renders correctly.

Environment

Plane: Self-hosted
Feature: Pages → Export PDF

OS: (e.g. macOS / Windows / Ubuntu)

Browser: (e.g. Chrome)

PDF viewer: (e.g. Preview / Adobe Reader)

Additional notes

The issue is consistently reproducible.

Exporting the same Page using browser “Print to PDF” renders Chinese text correctly.

This strongly suggests the built-in PDF export pipeline does not embed or load CJK fonts.

Installing and embedding fonts such as Noto Sans CJK (or equivalent) in the PDF renderer should resolve the issue.

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.1.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.