-
Notifications
You must be signed in to change notification settings - Fork 80
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
thread 'main' panicked at 'assertion failed: name == \"Identity-H\" #57
Comments
Can you provide an example PDF where this happens? |
I've seen two ways in which this can fail: ascii characters in names can be non-canonically encoded: "/Identity-H" as "/Identity%2dH" and "/Identity-V" may be used instead of "/Identity-H" which should both be treated identically according to the standard. |
@sftse do you have a reference in the standard for that behaviour? |
The standard mentions Identity-V five times, and the only information I can gather from them is |
I'm mistaken, the standard does spell out how to treat vertical writing differently, see table 117 where some entries may only exist for vertical writing, such as /DW2. For the purposes of text encoding specifically, it seems /Identity-V is treated the same as /Identity-H. |
I got similar issue too |
Can you post a link to an example pdf? |
I have another one: https://scholar.harvard.edu/files/stantcheva/files/lecture1_0.pdf |
hi,report this
The text was updated successfully, but these errors were encountered: