[
https://issues.apache.org/jira/browse/PDFBOX-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785198#comment-17785198
]
Tilman Hausherr commented on PDFBOX-5713:
-----------------------------------------
Yes that one I have too, but it doesn't describe the PFB format, which is the
first 6 bytes, and some bytes later. The T1 specification mentions only one
binary and one ascii part.
I'm wondering whether we should bother at all, this PDF is rendered and
extracted properly despite that the (illegally embedded) font fails.
Also Adobe has discontinued type 1 font support for authoring.
https://helpx.adobe.com/fonts/kb/postscript-type-1-fonts-end-of-support.html
> PfbParser fails to parse PFB font with multiple binary records.
> ---------------------------------------------------------------
>
> Key: PDFBOX-5713
> URL: https://issues.apache.org/jira/browse/PDFBOX-5713
> Project: PDFBox
> Issue Type: Bug
> Components: FontBox
> Affects Versions: 3.0.0 PDFBox
> Reporter: JaromÃr Dobrý
> Priority: Major
> Attachments: DejaVuSerifCondensed.pfb, PDFBOX-5713.diff, T1_SPEC.pdf,
> type1_embedded.pdf
>
>
> * The attached PFB font can be opened in FontForge but PfbParser in fontbox
> fails to read it.
> * The problem is that fontbox assumes there are three records (ascii,
> binary, ascii) in the PFB file but the binary part is split into multiple
> shorter chunks (i.e. ascii, binary, ..., binary, ascii).
> * I didn't find that this is forbidden and according to FontForge behavior
> it seems to be valid.
> * The fix seems to be easy, it is probably sufficient to concatenate the
> binary records together in PfbParser and the result will work correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
