[
https://issues.apache.org/jira/browse/PDFBOX-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilman Hausherr closed PDFBOX-4570.
-----------------------------------
Resolution: Won't Do
> U+2225 rendered as U+2016 glyph when use UniJIS-UCS2-H and non embedded font
> ----------------------------------------------------------------------------
>
> Key: PDFBOX-4570
> URL: https://issues.apache.org/jira/browse/PDFBOX-4570
> Project: PDFBox
> Issue Type: Improvement
> Components: FontBox
> Affects Versions: 2.0.15
> Environment: Windows 10 64bit, Adobe Reader 2019.012.20034
> Reporter: chunlinyao
> Priority: Minor
> Attachments: correct.png, incorrect.png, u2225.pdf, u2225.png
>
>
> Maybe this is not a bug of PDFBox, This pdf rendered difference than adobe
> reader. it use MS PMincho font, this font has glyph for U+2225, the glyph in
> Win10 different from WinXP (I confirmed that by using FontForge.)
> The Adobe Reader 2019.012.20034 ON Win10 rendered it correctly. Even Adobe
> Reader 2019.012.20034 ON macOS rendered incorrect. (with MSPMincho font
> installed)
> MuPDF 1.6 on Windows, Chrome, FireFox all rendered it like PDFBox.
> Although Adobe Reader on win10 rendered it correctly, When you copy the text
> from pdf, you will get U+2016 not U+2225.
> I doubt Adobe Reader doesn't use UniJIS-UCS2-H to convert unicode to cid then
> convert back to unicode when retrive glyphs.
> The UniJIS-UCS2-H is obsoleted. It mapping both U+2225 and U+2016 to CID+666,
> Change to UniJIS-UTF16-H can workaround this problem.
> Is there some posibility to improve PDFBox render like Adobe Reader?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
