[
https://issues.apache.org/jira/browse/BATIK-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Hennebert updated BATIK-1041:
-------------------------------------
Attachment: FontFamilyResolver.diff
Updated patch with defaulting to DefaultFontFamilyResolver.
I'm not sure I understand your comment regarding StrokingTextPainter: is there
a bridge or a user agent it can rely on? ATM it returns the
DefaultFontFamilyResolver, which essentially mimics what Batik was doing before
that change. Is that wrong?
Thanks,
Vincent
> Make it possible to plug custom FontFamilyResolver
> --------------------------------------------------
>
> Key: BATIK-1041
> URL: https://issues.apache.org/jira/browse/BATIK-1041
> Project: Batik
> Issue Type: Improvement
> Reporter: Vincent Hennebert
> Attachments: FontFamilyResolver.diff, FontFamilyResolver.diff,
> FontFamilyResolver.diff, FontFamilyResolver.diff
>
>
> This patch turns FontFamilyResolver into an interface and moves the current
> code into a default implementation. It also adds a getFontFamilyResolver to
> StrokingTextPainter that can be overridden in order to provide a custom
> implementation.
> This allows to use fonts from other libraries than AWT. In fact, AWT fonts
> can be totally disabled if necessary.
> This patch is experimental and should be put in a branch. Further updates are
> to be expected.
> This is a joint work from Peter Hancock and me.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
