On Thursday 13 July 2006 22:09, Jeremias Maerki wrote:
> What I tried to propose is mostly just that. Implementing some
> shortcut that at least treats all integer values differently from
> "always" with a constant penalty value. That gives FOP the
> opportunity to relax while still allowing the ra
Jeremias Maerki wrote:
+1 for PCL
+0 for AFP (I didn't have time for even a quick glance at it).
J.Pietschmann
Jeremias Maerki wrote:
remember this thread on fop-users? I've just found out what's wrong.
Great!
There's absolutely nothing wrong with the PDFRenderer or the PDF library
concerning reference freeing. It does it so as soon as each image is
written to the PDF which always happens immediately.
Jeremias Maerki wrote:
Anyone else?
No way. Sorry, family and the day job take all the time.
J.Pietschmann
Jörg,
remember this thread on fop-users? I've just found out what's wrong.
There's absolutely nothing wrong with the PDFRenderer or the PDF library
concerning reference freeing. It does it so as soon as each image is
written to the PDF which always happens immediately.
But I found that org.apach
On Jul 13, 2006, at 17:43, Jeremias Maerki wrote:
Andreas, what about you? Could you make it to the Cocoon GetTogether?
Yep, count me in.
Cheers,
Andreas
Jeremias Maerki a écrit :
Andreas, what about you? Could you make it to the Cocoon GetTogether?
One or two days of Hackathon (discussions, hacking, fun). Anyone else?
Jörg, Chris, Finn, Peter, Vincent maybe?
I don't know yet what will be my situation at that time, but I will do
my best to part
Uh, no. I just wanted to point out that "auto" is not a valid value for
column-width. What you probably meant was the case when the user doesn't
specify the column-width property in which case the value is not "auto"
but "proportional-column-width(1)" (see FOPropertyMapping). If that's
correct and
Thank you for the advice.
I will sum this up on the wiki page.
So if I understand correctly we have to support certain values even if
they are illegal ?
Patrick
Jeremias Maerki wrote:
Right, but strictly speaking the value "auto" is illegal for
column-width. FOP currently defaults to "prop
Andreas, what about you? Could you make it to the Cocoon GetTogether?
One or two days of Hackathon (discussions, hacking, fun). Anyone else?
Jörg, Chris, Finn, Peter, Vincent maybe?
It would really be good to be at least 3 or 4 FOP people to make the
expenses worthwhile.
Jeremias Maerki
Jeremias Maerki schrieb:
> Subject says it all. I think it's time. They work pretty well and have
> grown beyond sandbox state. I'm sure there maybe a few nits here and
> there, but the same applies to the other renderers.
+1
I've only tested the PCL renderer a bit but I'm sure the AFP renderer i
What I tried to propose is mostly just that. Implementing some shortcut
that at least treats all integer values differently from "always" with a
constant penalty value. That gives FOP the opportunity to relax while
still allowing the rather intuitive "always" not to relax thus providing
both kinds
On Jul 13, 2006, at 5:55 AM, Jeremias Maerki wrote:Subject says it all. I think it's time. They work pretty well and havegrown beyond sandbox state. I'm sure there maybe a few nits here andthere, but the same applies to the other renderers.+1 from me.Jeremias Maerki +1 Web Maestro Clay[EMAIL PROTEC
[2] makes sense to me. I would make the same argument regarding
'overflow'.
Peter
On Thu, 2006-07-13 at 14:19 +0200, Jeremias Maerki wrote:
> Fabio Gianetti made a good comment [1]. I answered like this [2].
...
>
> [1] http://lists.w3.org/Archives/Public/xsl-editors/2006JulSep/0001.html
> [2] h
On Thursday 13 July 2006 20:55, Jeremias Maerki wrote:
> Subject says it all. I think it's time. They work pretty well and
> have grown beyond sandbox state. I'm sure there maybe a few nits here
> and there, but the same applies to the other renderers.
>
> +1 from me.
>
Yes, I am biased on this ma
Jeremias Maerki wrote:
Subject says it all. I think it's time. They work pretty well and have
grown beyond sandbox state. I'm sure there maybe a few nits here and
there, but the same applies to the other renderers.
+1 from me.
+1 from me too. My thanks to all those who improved the AFP and PC
Jeremias Maerki wrote:
Fabio Gianetti made a good comment [1]. I answered like this [2]. I'm
currently thinking about how best to implement this. To keep it simple
for the moment, we could implement "always" like before but
remove/disable the overflow recovery I've implemented. That way, the
con
Subject says it all. I think it's time. They work pretty well and have
grown beyond sandbox state. I'm sure there maybe a few nits here and
there, but the same applies to the other renderers.
+1 from me.
Jeremias Maerki
Fabio Gianetti made a good comment [1]. I answered like this [2]. I'm
currently thinking about how best to implement this. To keep it simple
for the moment, we could implement "always" like before but
remove/disable the overflow recovery I've implemented. That way, the
content would again overflow.
Right, but strictly speaking the value "auto" is illegal for
column-width. FOP currently defaults to "proportional-column-width(1)"
if no value is specified.
Another thing we should be careful about is the distinction between the
value set for table-layout and the effective algorithm to be used. I
20 matches
Mail list logo
