[
https://issues.apache.org/jira/browse/PDFBOX-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100088#comment-14100088
]
ASF subversion and git services commented on PDFBOX-2262:
---------------------------------------------------------
Commit 1618516 from [~jahewson]
[ https://svn.apache.org/r1618516 ]
PDFBOX-2262: Removed AWT font rendering
- split CFFFont into CFFType1Font (Type 1) and CFFCIDFont (CID-Keyed)
- Fixed major parsing/conceptual errors in CFFEncoding and CFFCharset
- Moved Type1 and Type1C handling code into seperate classes
- Replaced SystemFontManager with pluggable FileSystemFontProvider
- Replaced PDFFontManager with ExternalFonts
- Added Type1Equivalent interface for Type 1 fonts which may be substituted,
e.g. standard 14.
- Moved all code for embedding fonts into new PDxxxFontEmbedder classes
> 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
>
> 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)
