[
https://issues.apache.org/jira/browse/PDFBOX-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101150#comment-14101150
]
Tilman Hausherr commented on PDFBOX-2262:
-----------------------------------------
These are the files that have an exception:
ApacheConPDFBox.pdf (p32)
eci_altona-test-suite-v2_technical_H.pdf
ELVIA-Reiserucktritt-Vollschutz.pdf
gs-bugzilla694585.pdf
PDFBOX-1094-094730.pdf (p3)
PDFBOX-1422.pdf
PDFBOX-1451.pdf
PDFBOX-1452.pdf
PDFBOX-1879.pdf
PDFBOX-2059-zerowidth.pdf
PDFBOX-2149.pdf
PDFBOX-2187-005541.pdf
PDFBOX-2215-027073.pdf (p3)
PDFBOX-2250.pdf
> Remove usage of AWT fonts
> -------------------------
>
> Key: PDFBOX-2262
> URL: https://issues.apache.org/jira/browse/PDFBOX-2262
> Project: PDFBox
> Issue Type: Improvement
> Components: PDModel, Rendering
> Affects Versions: 2.0.0
> Reporter: John Hewson
> Assignee: John Hewson
> Attachments: PDFBOX-1094-094730.pdf-1.png, PDFBOX-1770.pdf-1.png,
> bugzilla886049.pdf, bugzilla886049.pdf-1.png
>
>
> We're still using AWT fonts to render the "standard 14" built-in fonts, which
> causes rendering problems and encoding issues (see PDFBOX-2140). We're also
> using AWT for some fallback fonts.
> Removal of these AWT fonts isn't too difficult, we need to load the fonts
> using the existing PDFFontManager mechanism which has recently been added.
> All missing TrueType fonts loaded from disk have been using SystemFontManager
> for a number of weeks now.
> We should ship some sensible default fonts with PDFBox, such as the
> Liberation fonts (see PDFBOX-2169, PDFBOX-2263), in case PDFFontManager can't
> find anything suitable, rather than falling back to the default TTF font, but
> by default we'll probe the system for suitable fonts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
