Loading

After Copying Non-English TrueType Fonts (.ttf) To Path /usr/share/fonts, Tableau Font May Be Changed To Truetype During Server-Side Rendering

Дата публикации: Apr 29, 2025
Описание

After copying non-English TrueType fonts (.ttf) to path /usr/share/fonts (e.g. Japanese), unexpected fonts may be used by server-side rendering regardless of the default font(s) used in Tableau Desktop.
 

Cause

Depending on the font, the default Tableau Font may not include code points for non-English fonts, such as TrueType Japanese. If the font does not contain the required code points, the Linux OS will search for the appropriate font as the "best" font based on its .conf file when rendering the text on the server-side.
This is not a Tableau Server issue. The behavior is not controlled by Tableau Server.
Решение
Workaround 1
Use a "web-safe" fonts for proper server-side rendering. For more details see Use Custom Fonts. Noto CJK Sans is a safe choice for Chinese, Japanese, and Korean.

Workaround 2
Increase the complexity threshold for Web Browsers to use client-side rendering when accessing the Vizs. For more details see Configure Client-Side Rendering.
Note: this is not effective for server-side rendering processes, such as subscriptions and export PDFs.

Workaround 3
Run Tableau Server on Windows Server.
Дополнительные ресурсы
For more related information, see The rules to choose a font.

Fonts Not Displaying as Expected After Publishing to Tableau Public or Tableau Cloud

 
Номер статьи базы знаний

001472553

 
Загрузка
Salesforce Help | Article