Hi Simon & Benson,
Benson Margulies a écrit :
Simon,
The claim is that it's fixed on trunk. I did a trunk build, and my
colleague who started all this will test it. If his test fails, I'll
reopen it.
This is the right way, IMHO.
FOP always needs to be tested in many situations, and such tests (both
against official releases and dev versions) are welcome.
--benson
On Mon, Jan 4, 2010 at 3:12 PM, Simon Pepping <spepp...@leverkruid.eu> wrote:
Pascal and Abel,
Why was this bug closed? I believe it is Benson's intention to report
a known issue. He is looking to get it resolved and is willing to pay
for the effort. Unless Benson is raising a non-existent problem, I am
happy with his initiative. And I do not have the impression that it is
a non-existent problem.
I closed the bug because FOP TRUNK behaves correctly with the material
provided by Benson, while FOP 0.95 doesn't.
Benson,
Can you submit the resulting XSL-FO file, and possibly the resulting
HTML file for comparison of the intended result? I have a problem
running your transformations, and I do not wish to debug my XSLT2
system now.
Regards, Simon
On Mon, Jan 04, 2010 at 06:41:00PM +0100, Abel Braaksma wrote:
It concludes what was said. And Pascal's remark is about the issue
that was solved. But you try it with FOP Trunk and decide whether it
is sufficiently solved. If not, provide a reproducible example
(reproducible with the latest build) .
My talk about character-by-character is a known issue and is
unrelated to your bug report and is sufficiently covered on other
places.
Benson Margulies wrote:
Does this add up to a reason to reopen the bz?
--
Simon Pepping
--Pascal
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
