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

Issue with polish "Ł" #2150

Open
bigretromike opened this issue Aug 30, 2021 · 8 comments
Open

Issue with polish "Ł" #2150

bigretromike opened this issue Aug 30, 2021 · 8 comments

Comments

@bigretromike
Copy link

I got invoice with "zł" as payment sign. in 3.3.3 there is square in place, on pre-3.4.14080 there is empty space.

@GitHubRulesOK
Copy link
Collaborator

Sample needed
BUT do not post personal data files

No problem with other files just the common issues over poor PDFs with poor Unicode font mapping
in england it could be £ or € in Denmark see #2069

image

@bigretromike
Copy link
Author

I did sent "sample" to @kjk any clue why it stopped to work ?

@kjk
Copy link
Member

kjk commented Sep 10, 2021

I looked at it but don't really know.

The file is not generated correctly. Apparently earlier versions of mupdf was able to repair the file but latest version cannot. It's not easy to tell why because a lot of code has changes and it's complicated code.

@bigretromike
Copy link
Author

happy that sample arrived to you.
Yes something did change in mupdf, and that thing prevent us from upgrading pdfsumatra on-site :(

@GitHubRulesOK
Copy link
Collaborator

The core changes in MuPDF since 3.1.2 are mainly down to two key changes,
one is greater dependency on not correcting included font library with mainly some issues over white space (n/a in this case) and determining font substitution including unicode (may or may not be relevant)
two is stricter MuPDF rejection / lesser tolerance of malformed font definitions (more likely) Those can sometimes be corrected via a bug report at MuPDF.
The simple solution as shown in my example is when creating a PDF use correctly defined fonts that natively support embedding European characters.

@bigretromike
Copy link
Author

The simple solution as shown in my example is when creating a PDF use correctly defined fonts that natively support embedding European characters.

That wouldn't be a problem if those PDF files was create by me, we get those from outside source, and currently because of issue with displaying printing also is missing characters.

While we can stay on old sumatra version for some time, we will need to migrate to something else... because more and more people demand crypto support (validation of sign) and the issue with characters is also annoying.

But thanks for you sugestion, @GitHubRulesOK

@GitHubRulesOK
Copy link
Collaborator

Try to determine if the fault is due to one source client/software
then find an equivalent sample that is not too complex (single page)
or if private test identical fault after very simple deletions of names in an editor
Then the sample may be suitable for bug reporting to MuPDF or send simplified to kjk

@bigretromike
Copy link
Author

Try to determine if the fault is due to one source client/software
then find an equivalent sample that is not too complex (single page)
or if private test identical fault after very simple deletions of names in an editor
Then the sample may be suitable for bug reporting to MuPDF or send simplified to kjk

I did sent sample to kjk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants