Hi,
I have a problem when using padding-left on a fo:inline element inside a
repeating table header. The padding-left value is ignored on the repeated
table header on the next page.
Test case: http://old.nabble.com/file/p30077409/bg_bug.fo bg_bug.fo
PDF result file: http://old.nabble.com/file
Hi Jeremias,
do you think it would be very complicated to implement flow maps? I might
have clients which are interested in this feature.
Regards,
Matthias
Jeremias Maerki-2 wrote:
>
> Hi Russel,
>
> what you're looking for is essentially the flow-map feature of XSL 1.1,
> I believe. That al
lor()) in order to keep the code
separated from fop-rgb-icc().
I'm not quite sure how to implement the output part, so I guess I'll start
reading the PDF specification... :-)
Regards,
Matthias
Jeremias Maerki-2 wrote:
>
> Hi Matthias
>
> On 29.07.2009 16:47:15 Matth
be to implement support for spot colors? (e.g.
rgb-icc(0,0,0,#Separation, PantoneXYZ))
Regards,
Matthias Reischenbacher
MatthiasR wrote:
>
> Hi,
>
> I've built the fop and commons trunk in order to check if there are some
> improvements regarding CMYK TIFFs. But unfortunately
Hi,
I've built the fop and commons trunk in order to check if there are some
improvements regarding CMYK TIFFs. But unfortunately my tiff images are not
displayed as expected. I see some kind of greyscale image without
recognizing the original image in the PDF output.
JM wrote in the commons cha
the transcoder cannot determine the intrinsic size
> of the graphic. Of course, the code could do some guessing but that
> could just as well be wrong.
>
> On 11.04.2008 22:09:11 MatthiasR wrote:
>>
>> Hi,
>>
>> I'm trying to transcode svg documents to eps fil
Hi,
I'm trying to transcode svg documents to eps files. This works very well for
most of my svg files but sometimes the transcoder adds blank space on the
right and below to the generated eps files. When this happens image width
and height are the same (widht = height) and the eps file is display
Hi,
Thanks for your reply. I will modify my xsl-fo files.
It seems that the new FOP version will be more strict about
standard-compliance of xsl-fo code. I experienced as well
ValidationExceptions when there were less fo:table-column - elements than
table-cells in a row.
Is there any informatio
Hi,
with current FOP trunk I'm running into a problem when using the
number-rows-spanned attribute for a table-cell element inside a table
header. With FOP 0.94 it works fine, but FOP Trunk refuses to generate a pdf
output with the error message:
org.apache.fo.ValidationException: A table-cell is
