xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Hennebert (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BATIK-1041) Make it possible to plug custom FontFamilyResolver
Date Thu, 30 Jan 2014 12:32:10 GMT

     [ https://issues.apache.org/jira/browse/BATIK-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vincent Hennebert resolved BATIK-1041.
--------------------------------------

    Resolution: Fixed

Committed in [rev. 1562797|http://svn.apache.org/r1562797]

> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org


Mime
View raw message