[
https://issues.apache.org/jira/browse/PDFBOX-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100107#comment-14100107
]
John Hewson commented on PDFBOX-2144:
-------------------------------------
[~pslabycz], I've implemented a pluggable interface for retrieving external
fonts as part of my refactoring to remove the remaining AWT fonts from our
rendering pipeline. Please checkout the
[no-awt|http://svn.apache.org/viewvc/pdfbox/branches/no-awt/] branch and give
it a try. You'll need to implement the FontProvider interface and pass it to
ExternalFonts.setProvider(). See FileSystemFontProvider for an example.
> Provide a pluggable font manager
> --------------------------------
>
> Key: PDFBOX-2144
> URL: https://issues.apache.org/jira/browse/PDFBOX-2144
> Project: PDFBox
> Issue Type: Improvement
> Components: Rendering
> Reporter: Petr Slaby
> Attachments: FontManager.patch
>
>
> Our J2EE application has all fonts and resources configured and stored in its
> database. No files are accessed directly from file system or from system
> environment. To make PDFBox compatible with this philosophy, we need the
> FontManager in pdfbox and fontbox to be pluggable, e.g. as shown in the
> attached patch.
> The proposal defines a FontManager interface and default implementation which
> is the original one. FontManager then needs to be configured on and
> propagated from PDFStreamEngine and PageDrawer. It should also be
> configurable on PDFRenderer, which is not shown in the patch. There I would
> suggest to introduce a configuration object which would take care about all
> the current and future options of PDFRenderer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
