[
https://issues.apache.org/jira/browse/PDFBOX-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837602#action_12837602
]
Daniel Wilson commented on PDFBOX-635:
--------------------------------------
Villu,
I entirely agree with the *concept* of this patch -- if the right means of
parsing fails, warn and fall back to something less correct that will work.
Reading your patch, I see the warning. But I don't see the fallback actually
occurring.
Does it indeed fall back to a Type1 font? Could you explain how the code is
doing this?
Thanks!
Daniel
> Fallback mechanism for broken CFF fonts
> ---------------------------------------
>
> Key: PDFBOX-635
> URL: https://issues.apache.org/jira/browse/PDFBOX-635
> Project: PDFBox
> Issue Type: Improvement
> Components: PDModel
> Affects Versions: 1.0.1
> Reporter: Villu Ruusmann
> Attachments: PDFBox.patch
>
>
> PDFBOX-542 has not proven to be sufficiently foolproof for real-world PDF
> documents.
> PDFBox should fallback to a Type1 font with appropriate warning message (this
> is the default behaviour with PDFBox 0.8.0 and earlier versions) when there
> is a problem parsing/interpreting a CFF (aka Type1C) font.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
