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

/ToUnicode spec violation #70

Open
sftse opened this issue Oct 5, 2023 · 2 comments
Open

/ToUnicode spec violation #70

sftse opened this issue Oct 5, 2023 · 2 comments

Comments

@sftse
Copy link

sftse commented Oct 5, 2023

get_unicode_map includes a check that if the /ToUnicode key is a name, that it must be /Identity-H.
I have searched the pdf spec and checked a bunch of personal pdfs to see whether this is justified.
It seems to be a violation of the standard, is there an example of this occurring in practice?

@sftse sftse changed the title /ToUnicode checking /ToUnicode spec violation Oct 5, 2023
@jrmuizel
Copy link
Owner

jrmuizel commented Oct 5, 2023

I added db3a490 to make the intention here more clear.

@sftse
Copy link
Author

sftse commented Oct 5, 2023

From the PDF standard p.292
"This information can be provided as an optional ToUnicode entry in the font dictionary (PDF 1.2; see
9.10.3, "ToUnicode CMaps"), whose value shall be a stream object containing a special kind of CMap file
that maps character codes to Unicode values."

To clarify my question, it seems the PDF standard mandates the entry to be a stream object, is there an example where this entry was a name object?

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

2 participants