[
https://issues.apache.org/jira/browse/PDFBOX-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898197#comment-13898197
]
John Hewson commented on PDFBOX-1895:
-------------------------------------
Thanks, that's perfect. Incidentally, the PDF file you linked to has some major
problems, it does not display at all in OS X Preview. Chrome's PDF viewer does
not correctly display the text. Adobe Acrobat displays the message "The file is
damaged, and could not be repaired" but is able to open and view the file.
Attempting to use Acrobat's preflight to verify conformance fails with the
message "An error occurred while parsing a contents stream. Unable to analyze
the PDF file". Running PDFBox preflight results in the following relevant error
messages:
{code}
3.1.3 : Invalid Font definition, FontFile entry is missing from FontDescriptor
for MS-Mincho
3.1.3 : Invalid Font definition, FontFile entry is missing from FontDescriptor
for MS-Gothic
3.1.7 : Invalid Font definition, The CMap is a string but it isn't an
Identity-H/V
3.1.3 : Invalid Font definition, FontFile entry is missing from FontDescriptor
for HeiseiMin-W3
{code}
> Font definitions must precede font references
> ---------------------------------------------
>
> Key: PDFBOX-1895
> URL: https://issues.apache.org/jira/browse/PDFBOX-1895
> Project: PDFBox
> Issue Type: Bug
> Components: Writing
> Affects Versions: 1.8.3, 1.8.4
> Reporter: Pat Hickey
>
> When re-writing a document with font descriptions, Adobe Reader is unable to
> display the fonts in the document. Reader can display the fonts in the
> original document. The difference is that in the original document, the font
> descriptions are in lower object numbers than the font references; in the
> output document, the font descriptions are in higher object numbers than the
> font references. Is there a quick way to re-order them?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
