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

Wrong rendering of multiplication sign #12632

Closed
rutkowskii opened this issue Nov 16, 2020 · 4 comments
Closed

Wrong rendering of multiplication sign #12632

rutkowskii opened this issue Nov 16, 2020 · 4 comments

Comments

@rutkowskii
Copy link

Seen with this setup:

  1. PDF.JS as currently deployed in https://mozilla.github.io/pdf.js/web/viewer.html
  2. Chrome 86.0.4240.198
  3. Windows 10

Repro steps:

  1. Download this document : https://www.dropbox.com/s/k8032s77j5c7l0f/latest-core.pdf?dl=0
  2. Open this document with https://mozilla.github.io/pdf.js/web/viewer.html

Expected behavior:
Multiplication chars should be rendered correctly as here:
image

Actual behavior:
Instead, the chars are rendered as dots:
image

The font of these chars appears to be Symbol. I am wondering, if there's a workaround for this situation, like having a fallback font somewhere?

@Snuffleupagus
Copy link
Collaborator

WFM, with PDF.js version 2.7.276 in Firefox Nightly 84 on Windows:

firefox


Chrome 86.0.4240.198

This could possibly suggest a Chromium-specific bug, rather a PDF.js one.

The font of these chars appears to be Symbol. I am wondering, if there's a workaround for this situation, like having a fallback font somewhere?

The best solution, to guarantee that fonts always render correctly, is to always embed all font data in the PDF file.

@calixteman
Copy link
Contributor

I've the same issue using https://mozilla.github.io/pdf.js/web/viewer.html with firefox nightly on debian but no problem with chrome (debian too). The default fallback font is likely not the same.

@timvandermeij
Copy link
Contributor

It's also broken for me using Firefox 82.0.3 on Arch Linux. The fonts are indeed not embedded properly, and Okular (in which it does work) falls back to another (system) font. The proper solution here is indeed to always embed fonts in the PDF file, otherwise correct rendering is not guaranteed.

@Snuffleupagus
Copy link
Collaborator

Duplicate of #4244

@Snuffleupagus Snuffleupagus marked this as a duplicate of #4244 Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants