[
https://issues.apache.org/jira/browse/PDFBOX-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837756#action_12837756
]
Villu Ruusmann commented on PDFBOX-635:
---------------------------------------
This patch can only be understood if one analyzes it in the context of method
org.apache.pdfbox.pdmodel.font.PDFontFactory#createFont(COSDictionary).
Here's an excerpt:
if(cosDictionary.getFontType().equals("Type1")){
PDFont retvalue = new Type1Font(cosDictionary);
if(cosDictionary.getFontSubType().equals("Type1C")){
try {
retvalue = new Type1CFont(cosDictionary);
} catch(Exception e){
log.warn("Cannot create replacement Type1C font, returning original Type1
font");
}
}
return retvalue;
}
> 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.
