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

thread 'main' panicked at 'assertion failed: name == \"Identity-H\" #57

Open
wingjson opened this issue May 12, 2023 · 9 comments
Open

Comments

@wingjson
Copy link

hi,report this

@jrmuizel
Copy link
Owner

Can you provide an example PDF where this happens?

@sftse
Copy link

sftse commented Oct 12, 2023

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.

@jrmuizel
Copy link
Owner

@sftse do you have a reference in the standard for that behaviour?

@sftse
Copy link

sftse commented Oct 12, 2023

The standard mentions Identity-V five times, and the only information I can gather from them is
p.275 Table 118 "Vertical version of Identity-H. The mapping is the same as for Identity-H."

@sftse
Copy link

sftse commented Oct 12, 2023

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.

@IRONAGE-Park
Copy link

I got similar issue too

@jrmuizel
Copy link
Owner

jrmuizel commented Oct 7, 2024

Can you post a link to an example pdf?

@IRONAGE-Park
Copy link

@jrmuizel Okay. I'll send to that.

Test.pdf

This file is Korean documents.

can you check this document?

@jawj
Copy link

jawj commented Oct 8, 2024

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

5 participants