On 25.01.2004 12:46:08 Thomas DeWeese wrote:
Jeremias Maerki [EMAIL PROTECTED] wrote:
Damn, you're right. I wonder why we haven't made use of this, yet. BTW,
is this code from JAI (like the classes Oleg Tkachenko uses in his TIFF
renderer) or is this separately developed code (ASF
Jeremias Maerki wrote:
I will probably have some time next month to write a proposal on how our
two projects can move closer together to make the code sharing happen.
Stuff that comes to mind immediately:
- fonts, metrics, character and word width
- various configuration stuff
- character
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
I will probably have some time next month to write a
proposal on how our
two projects can move closer together to make the
code sharing happen.
Jeremias Maerki
Ummm...Jeremias, remember, your recent nominations for
FOP committers included
Noted. I will make it a point in the proposal so the Batik people will
be able to comment and we can develop mechnisms to ensure quality.
On 25.01.2004 18:42:20 Glen Mazza wrote:
The current (lowered) committer standards on the FOP
team definitely needs to be explained to the Batik
team before
Very classy response. (You're getting good at knowing
how to handle me... ;-)
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
Noted. I will make it a point in the proposal so the
Batik people will
be able to comment and we can develop mechnisms to
ensure quality.
On 25.01.2004 18:42:20
Hi all,
It is certainly true that javax.imageio is the direction
to go in the future.
However, It is probably worth pointing out that you already
include a PNG encoder/decoder with the FOP distribution,
from Batik!
org.apache.batik.ext.awt.image.codec.PNGImageEncoder
Damn, you're right. I wonder why we haven't made use of this, yet. BTW,
is this code from JAI (like the classes Oleg Tkachenko uses in his TIFF
renderer) or is this separately developed code (ASF origin)?
You know that there's a number of people who would actually be
interested in creating/having
The ASF does see a problem. Until the FSF has clarified the relationship
between linking and Java's import concept the ASF's policy is not to
allow usage of LGPL packages. There are certain exceptions. For example,
if you have a JAI-compatible image codec under the LPGL you could use it
because
Hi Jeremias,
thanks for the quick response.
Jeremias Maerki wrote:
The ASF does see a problem. Until the FSF has clarified the relationship
between linking and Java's import concept the ASF's policy is not to
allow usage of LGPL packages. There are certain exceptions. For example,
if you have a
No apologies required!
Image IO (javax.imageio) support is not there, yet, I'm afraid. But if
you created an implementation for Image IO then your idea would work.
Shouldn't be very hard. Check the org.apache.fop.image package. You
wouldn't need to use JIMI. Think of JIMI, JAI and ImageIO as
Hi,
I was looking into getting FOP to run with kaffe[1] recently[2][3], and
decided to have another look at it today, after gettig maven to run with
kaffe. I tried to generate DocBook docuemntation for another package,
and the Maven sdocbook plugin insisted on fetching jimi.jar from Sun.
So
--- Dalibor Topic [EMAIL PROTECTED] wrote:
If that's not the case, would it be possible to use
the LGPLd code from
http://catcode.com/pngencoder/ and
http://www.sixlegs.com/software/png/
for the job, and dropping the dependency on JIMI
completely?
No, (L)GPL and the Apache licenses are
Hi Glen,
thanks for the quick reply.
Glen Mazza wrote:
--- Dalibor Topic [EMAIL PROTECTED] wrote:
If that's not the case, would it be possible to use
the LGPLd code from
http://catcode.com/pngencoder/ and
http://www.sixlegs.com/software/png/
for the job, and dropping the dependency on JIMI
13 matches
Mail list logo
