Open wingjson opened 1 year ago
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 p.275 Table 118 "Vertical version of Identity-H. The mapping is the same as for Identity-H."
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.
hi,report this