On 27.07.2005 12:35:16 Siarhei Baidun wrote:
> > Ah, I see. But in that case external-graphic is probably not the right
> > element to use as it is an inline-level element.
>
> Any other ideas?
> The problem is XSL-FO specification does not describes the case of embedding
> external PDF files, so there is no special element there.
Right. For example we could provide an additional extension element
under fo:root which would involve extending its contents from:
(layout-master-set,declarations?,page-sequence+)
to:
(layout-master-set,declarations?,(page-sequence|fox:external-document)+)
This way it would be possible to freely mix content.
fox:external-document could have the following attributes:
- content-type ("application/pdf" in case of PDF files)
- src (URL to the PDF to be included)
> > iText is able to handle that, yes.
>
> Ok, we'll launch investigation of iText applicability instead of Pj.
You may also want to look around. I think someone mentioned having
written an iText Renderer (for 0.20.5) already.
> > Provided, we get the licensing issues right, yes. This would include
> > contacting the original authors of JEuclid if you based your code on it.
> > Furthermore, bringing in a whole subproject such as JEuclid would
> > involve going through the Apache Incubator. But let's first get some
> > opinions on that move (see my other thread).
>
> I agree that it would be nicer to keep extensions out-of-the-box.
> I'd vote to have a separate subproject under XML Graphics for MathML support
> as well.
Any volunteers to start talking to the JEuclid guys? I can serve as
sponsoring member.
> To have working sources ready-to-use in the nearest future, I'd suggest the
> following steps:
> 1/ Implement support of MathML in FOP based on existing JEuclid project.
> It would require minor implementation on the side of FOP - say, add MMLArea
> element and some code in PDFRenderer (renderMMLArea() method ) - as we have
> done it now.
Please don't do it this way. Please create an implementation of an
XMLHandler. Do it the same way SVG/Batik-support is implemented.
> Obviously, the impementation would require JEuclid jar archive.
> To make FOP sources compilable in case of absence of JEuclid jar, and build
> script could be modified a bit to foresee such case.
Initial feedback from a few committers indicates that you can simply
put the JEuclid jar in the lib directory and work from there. Due to its
license we can easily redistribute it.
> 2/ Bring JEuclid under ASF (of cource in case founders accept such step) .
I'm sure that's no problem. But it'll take some effort, especially from
the original authors. And someone has to talk to them.
> 3/ Commit our changes that have been made during several months to JEuclid
> project.
>
> Step 1/ we could launch right now.
>
>
> > No, the ASF policy was recently changed (or rather clarified) so you
> > would need to submit a CLA for any contribution bigger than a trivial
> > bugfix
> > on an existing file, i.e. for new files, even if you're not yet a
> > committer.
>
> Ok, no problem.
> Could you please give a link or send CLA template?
http://www.apache.org/licenses/ (scroll to bottom)
> How can we send it to Apache - via fax?
Yes. The number is on the form.
Jeremias Maerki
