Subject: Re: fop-ttfreader - output bounding box
information for characters?
I am happy to apply the patch and I have done something equivalent to this as part of the the project to configure Batik to use custom fonts.
Going forward, we hope to allow Batik to directly use Font provided by FOP when converting SVG to Java2D drawing commands. FOP will render text natively with no need to pre-embed the Font into the SVG. As mentioned this is a fairly involved piece of work that may even lead to a new Font library in XML Graphics, see http://markmail.org/thread/hkclkqaxlfh5wwvu
On Tue, Jan 8, 2013 at 8:10 AM, Chris Bowditch <bowditch_chris@xxxxxxxxxxx
On 08/01/2013 07:52, Alexey Neyman wrote:
On Monday, January 07, 2013 11:44:46 AM Chris Bowditch wrote:
>>>> Patch from pMML2SVG, slightly modified to apply to FOP 1.1 sources,
>>> Thanks for the patch. To get this added to the code base please raise an
>>> issue in JIRA, add the diff as an attachment and include [PATCH] in the
>>> subject line. A committer will then review the patch before applying it.
>> Created an issue:
> Thank you.
So, can this patch be reviewed/integrated?
That shouldn't be a problem. As I indicated Peter is working in a similar area right now, so I will ask him if he can take a look.
> >> I know Peter Hancock is looking into doing something similar as he is
> >> working on getting Batik to use FOP configured fonts instead of the
> >> system ones. Peter mentioned to me offlist that he was going to need to
> >> expose a few extra things in TTFReader to facilitate this, could be you
> >> are covering similar ground here.
> > Maybe. Then again, the root of the issue is not Batik - that issue I work
> > around by embedding fonts. It is JEuclid's use of system fonts which is
> > why I am switching to pMML2SVG - which needs bounding box information for
> > glyphs.
> > BTW, another useful feature in pMML2SVG that was not available in JEuclid
> > is that pMML2SVG outputs baseline position information in the generated
> > SVG - so that inline equations can be properly positioned on the line.
> Sounds like we need a FOP plug-in for pMML2SVG to replace the ageing
> JEuclid one.
Pardon my ignorance, but what is FOP using for the XSL transformation? Is it Xalan-based? In that case, it probably won't be sufficient: pMML2SVG requires XSLT 2.0, which, as far as I understand, is only supported by Saxon.
You can use whichever XSLT processor you choose with FOP, as long as you feed FOP with XSL-FO.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com