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.

Sign up for GitHub

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

Jump to bottom

PDF text missing #2884

Closed
vyv03354 opened this issue Mar 4, 2013 · 9 comments
Closed

PDF text missing #2884

vyv03354 opened this issue Mar 4, 2013 · 9 comments
Labels
font-conversion font-wont-sanitize

Comments

@vyv03354
Copy link
Contributor

vyv03354 commented Mar 4, 2013

http://www.chotatsu.e-aichi.jp/portal/pdf/1/4.6.1.pdf
This is broken by 78213e8. Why is this heuristic added?
@vyv03354
Copy link
Contributor Author

vyv03354 commented Mar 4, 2013

Hm, #1597.

@yurydelendik
Copy link
Contributor

Type1 CMap parser needs to be refactored to avoid this heuristic.

@timvandermeij
Copy link
Contributor

Still broken on Windows 7 x64, Firefox 22 (HWA on) and the latest PDF.js development build.

@Snuffleupagus
Copy link
Collaborator

This will be fixed partially by PR #3674.

@Snuffleupagus Snuffleupagus mentioned this issue Sep 19, 2013
Merged
@brendandahl brendandahl mentioned this issue Feb 7, 2014
Merged
@Snuffleupagus
Copy link
Collaborator

With #4259 all glyphs are now rendered, but some of them are placed on top of each other.

@timvandermeij
Copy link
Contributor

That, and some glyphs have more space between them than they should have. Compare the first lines in Acrobat/PDF.js for example.

@timvandermeij
Copy link
Contributor

Spacing issues and glyps on top of each other seem to be resolved, but some glyps are still not correct, espcially in the header we miss the digits and throughout the document there are some vertical bars.

@brendandahl
Copy link
Contributor

Looks to be the same issue as #6397 (comment)

@Snuffleupagus
Copy link
Collaborator

Snuffleupagus commented Jul 23, 2017 •
edited

It seems that this is almost fixed by PR #8580; please see the comparison between Adobe Reader (on the left) and PDF.js (on the right):

2884

brendandahl added a commit that referenced this issue Oct 24, 2017
@brendandahl
Move char codes from high surrogate pair range into private use.
096d9b3 
Fixes #2884
@brendandahl brendandahl mentioned this issue Oct 24, 2017
Merged
brendandahl added a commit to brendandahl/pdf.js that referenced this issue Dec 7, 2017
@brendandahl
Move char codes from high surrogate pair range into private use.
306999c 
Fixes mozilla#2884
ltetzlaff pushed a commit to ltetzlaff/pdf.js that referenced this issue Apr 24, 2018
@brendandahl @ltetzlaff
Move char codes from high surrogate pair range into private use.
e4855e6 
Fixes mozilla#2884
movsb pushed a commit to movsb/pdf.js that referenced this issue Jul 14, 2018
@brendandahl
Move char codes from high surrogate pair range into private use.
4f5cb24 
Fixes mozilla#2884
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
font-conversion font-wont-sanitize
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@brendandahl @vyv03354 @yurydelendik @timvandermeij @Snuffleupagus