Hi Glen,
Now I'm using Eclipse, and it works well.
- Original Message -
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: 2005年6月6日 22:14
To: fop-dev@xmlgraphics.apache.org
Subject: Re: build fop-1.0dev in java IDE
Kevin should make sure he's using the Ant build script to build FOP, and n
Team,
Anyone have a problem if I remove the initialize() method from the
LayoutManager interface (and assorted related code from
AbstractLayoutManager), by having the eight LM's currently using it
initialize themselves internally instead?
Currently, for those 8 LM's using external initializa
BTW, FOP-devs, if you're interested in learning more about "Document
Science" and don't mind adding another 15 or so emails to your pile each
day, I might recommend subscribing to the Docbook-Apps ML [1][2]. They are
fairly heavy users of FOP (although we do lose out to the commericial
implementat
On 06.06.2005 18:36:17 Luca Furini wrote:
> A related question: if there is a fo:block with linefeed-treatment =
> "preserve" and two consecutive linefeeds, what is the expected output?
>
> For example:
> Text line 1.
>
> Text line 2.
>
> At the moment, there is an empty line between "Text line
Kevin should make sure he's using the Ant build script to build FOP, and not
his IDE commands--I suspect that may be the main problem. (I would also
encourage him to consider using Eclipse as his IDE--I switched to it from
JEdit three months ago, and only regret I did not switch much earlier.)
Gl
Jeremias Maerki wrote:
> Right now, that last empty block creates a block area that has a BPD of
> 14400. In the end this area should collapse to a BPD of 0 so it doesn't
> affect the page breaking. A footnote like this is a regular work-around
> in 0.20.5 and we should have it working again. Or m
Yes, you're absolutely correct. Up until now my "ROT" was pure line
count -- if just one, don't bother with the isDebugEnabled(). But now I see
the need to also check the parameter supplied. BTW, if you're making
changes to the code today if you can take care of this it would be
appreciated. El
> I don't intend to. It would send the wrong signal. I've
> already renamed
> the API to avoid "FOP" in the name, so I don't scare potential
> commercial implementors away. It's probably going to end up
> on java.net.
> But it's Apache v2 licensed, just like FOP. The intention is
> to have as
>
I loaded FOP stuff via CVS this morning.
> -Original Message-
> From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 06, 2005 3:21 PM
> To: fop-dev@xmlgraphics.apache.org
> Subject: Re: [Tests] automated Tests for FOP's XSL-Standard compilance
>
>
> Are you really sure
Are you really sure you got the latest sources? I've just updated
everything and don't see the problem. At first, I thought it would be a
problem with the Xalan version because the XPath statements might not
have been resolved correctly, but obviously text-transform doesn't even
have an effect on y
:)
here are all messages, I got (only on junit target (which are the interesting
one))
HTH,
Matthias
junit:
[echo] Running basic functionality tests for fop-transcoder.jar
[junit] Testsuite: org.apache.fop.BasicTranscoderTestSuite
[junit] Tests run: 2, Failures: 0, Errors: 0, Ti
Yes, there are a few footnote tests that currently don't work. The
text-transform tests should work, though. What were the error messages
for text-transform? CVS HEAD is still a moving target and the file with
the disabled test cases may not always be up to date. But as it seems
you're of the flexi
On 06.06.2005 13:29:30 Matthias Wessendorf wrote:
> Hi,
>
> see comments inline
>
> > We've started a systematic test suite for FOP 1.0dev development. It's
> > located here:
> >
> > http://cvs.apache.org/viewcvs.cgi/xml-fop/test/layoutengine/
> >
> > Some initial documentation is here:
> > ht
Hi Jeremias,
I just looked at exsisting base of test cases. I had to disable some
footnotes xml. And also text-transform1|2 . xml
After the the unit test for layout engine works fine for me (BUILD SUCCESSFUL)
Is that a known issue?
Matthias
> -Original Message-
> From: Matthias Wessen
Hi,
see comments inline
> We've started a systematic test suite for FOP 1.0dev development. It's
> located here:
>
> http://cvs.apache.org/viewcvs.cgi/xml-fop/test/layoutengine/
>
> Some initial documentation is here:
> http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests
thanks
On 06.06.2005 13:02:29 Kevin wrote:
> Hi,
> I do the code generating indeed. And all files in build/gensrc are:
> |-build
> |-gensrc
> |-org
>|-apache
> |-fop
>|-fonts
> |-CodePointMapping.java
> |-base14
>|-Courier.java
>|-CourierBold.
Hi,
I do the code generating indeed. And all files in build/gensrc are:
|-build
|-gensrc
|-org
|-apache
|-fop
|-fonts
|-CodePointMapping.java
|-base14
|-Courier.java
|-CourierBold.java
|-CourierBoldOblique.java
|-Courie
Hi Kevin
You didn't say what your problem is, but I suspect you're missing the
sources that are generated during the build. You need to run "ant
codegen" which generates the missing sources in the directory:
build/gensrc
If you add this directory to the source directories you should be a lot
clo
Hi Matthias
On 06.06.2005 10:41:37 Matthias Wessendorf wrote:
> Hi there,
>
> are there any (unit) tests regarding FOP's standard compilance?
We've started a systematic test suite for FOP 1.0dev development. It's
located here:
http://cvs.apache.org/viewcvs.cgi/xml-fop/test/layoutengine/
Some i
Hi,
I try to build fop-1.0.dev in JBuilder9, but I failed.
Who can tell me how to build fop-1.0dev in such IDE? Otherwise how to trace the
executing?
Hi there,
are there any (unit) tests regarding FOP's standard compilance?
I'd like to document the FOP behaivor when it becomes an input file that
contains a with NO table-layout="fixed".
So in my case (not a test case (yet)) I saw a PDF file on my disk (so
"out.size() > 0" is true ;)), but th
FYI, I've just posted a proposal for Google's Summer of Code on the Wiki
at:
http://wiki.apache.org/general/SummerOfCode2005
I thought, since I'm currently too busy in the layout engine and Peter
Herweg has obviously gone inactive, I'll post this. Maybe we get lucky.
The task is quite isolated whi
On 06.06.2005 09:15:34 Jeremias Maerki wrote:
> operator it depends on the intelligence of the JIT compiler whether it
That should have been the Java Compiler, not the JIT compiler.
Jeremias Maerki
An explanation why the "log.isDebugEnabled()" was there and why it
should be added again (maybe not necessarily in this case since it's
only called once per page but as a general rule):
"+" operations with Strings usually results in a StringBuffer being
created the two Strings before and after the
24 matches
Mail list logo
