Missing characters when opening a PDF

[sjkellyfetti]

I am working with a web application that generates reports in PDF format and when I use the PDF-XChange Viewer (latest version - v2.0 b42.1) to open the PDF, it is not showing any numbers or special characters - this is not so useful when working with a report showing revenue numbers and metrics (as well as email addresses, dates, phone numbers and address information).

When opened in the Adobe Reader (7.0) or FoxIt, the report shows fine. The report was created using dbAutotrack PDFWriter for .NET using PDF version 1.3. Does anyone have any ideas what might be the cause of this?

Sean

[Bhikkhu Pesala]

Tracker support will need a sample PDF to identify the problem. You can send it via the Help menu, report a problem, if it is confidential, or zip a test document and upload it here.

[sjkellyfetti]

Here is the file I am having the issue with.

Sean

[Stefan - PDF-XChange]

Dear Sean,

There are some problems with an embedded true type font (it is incorrect) in the attached document. We are currently looking for a solution for handling such broken files in our software.

As a side note I would like to add that the Foxit I have on my machine is also having problems with those characters.

Regards,
Stefan

[Bhikkhu Pesala]

This seems to be fixed in build 41.3

Check for updates from the help menu.

[sjkellyfetti]

Bhikkhu - thanks for the update! I just dowloaded the new build and it is now working correctly!

Stefan - I am working with the developers and they are asking me if you know what is incorrect with the embedded font? They want to see if it is something they are doing wrong that they can fix or something that the PDFWriter app they are using is doing.

Sean

[Ivan - Tracker Software]

The Problem is with the embedded font TTF file (object 12 0 into PDF attached here). And there is more then one problem.

Firstly: From the TTF specification, tables in a TTF files should be sorted by name. To be honest, most TTF readers ignore this trouble, however it would be good to have well formed data.

Secondly, and the item which causes issues showing symbols: loca table has an incorrect size (in the file it occupies the correct size, but in the table header the wrong size is specified).

The size was calculated as a 'short' loca, but in this file it is a 'long', as specified in the indexToLocFormat field of head table. A Short table uses WORD as offset, long - uses DWORD values.

HTH