Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Fonts not working as expected. #165

Closed
agnipanda opened this issue Oct 18, 2023 · 0 comments · Fixed by #233
Closed

[BUG] Fonts not working as expected. #165

agnipanda opened this issue Oct 18, 2023 · 0 comments · Fixed by #233
Labels
bug Something isn't working

Comments

@agnipanda
Copy link

Environment

  • chromium Version: 114.0.0
  • puppeteer / puppeteer-core Version: 20.6.0
  • Node.js Version: 16.x
  • Lambda / GCF Runtime: nodejs16

Description

I was facing issue #33 which got fixed on assigning /etc/fonts to FONTCONFIG_PATH.

Behavior with FONTCONFIG_PATH:

All custom fonts loaded using await chromium.font() are working fine, but unable to use Open Sans which ships with the package.
Noto Sans JP renders English text in Noto Sans along with the Japanese text.
The default font here becomes Noto Sans.

Behavior without FONTCONFIG_PATH:

On using font Noto Sans JP(Japanese) the english text renders in Open Sans but Japanese texts are rendered properly.
The default font here becomes Open Sans.

@agnipanda agnipanda added the bug Something isn't working label Oct 18, 2023
@Sparticuz Sparticuz mentioned this issue Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant