[PDFBOX-4811] Glyphs getting lost when rendering

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.19
• Fix Version/s: 2.0.20, 3.0.0 PDFBox
• Component/s: FontBox
• External issue URL: https://github.com/mozilla/pdf.js/issues/11768
• Assignee: Tilman Hausherr
• Reporter: Tilman Hausherr
• Created: 13/Apr/20 20:07
• Updated: 15/Jun/20 04:54
• Resolved: 14/Apr/20 04:41

Description

I missed a rendering change (sorry) in the linked PDF.js issue that happened in PDFBOX-4810 but it is not a regression, rather a difference in displaying a bad input due to having different data.

The CMap has these ranges:

4 begincodespacerange
<00><7f>
<c080><dfbf>
<e08080><efbfbf>
<f0808080><f7bfbfbf>
endcodespacerange

The content stream has segments like

(Check\340up Date:2020/ 3/ 4  11:46) Tj

0340 is 0xE0. The current code at CMap.readCode() reads bytes until a range fits, and this means it reads 4 bytes until it noticed that this has failed. After the failure it doesn't reposition. So this is displayed as "Check ·Date" instead of "Check -up Date", i.e. input is lost. The "·" is the default glyph.

The solution is to remember the position and to reposition there. I'm using mark() and reset() which, surprisingly, works both when loading in memory and when loading with temp file.