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.

iText is able to handle that, yes.

Ok, we'll launch investigation of iText applicability instead of Pj.

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.

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.

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.

2/ Bring JEuclid under ASF (of cource in case founders accept such step) .

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?
How can we send it to Apache - via fax?

--
Siarhei Baidun
[EMAIL PROTECTED]


Reply via email to