|
Re: Nested tables + truncated images + Word emitter [message #485216 is a reply to message #485010] |
Thu, 10 September 2009 19:50 |
|
James,
I believe this has been fixed in 2.5. I tried your report with 2.5 and
no images were messed up by the page breaks.
Jason
James Willans wrote:
> Hello,
>
> We have images contained in a table which is itself nested within
> another table. When we output the report using the Word emitter the
> images are truncated by the page break and sometimes by the right
> margin. Please see the attached report "reportTest.doc" which contains
> many examples. Note that this does not happen with the pdf emitter.
>
> The attached small example report design and associated csv file
> reproduces this behaviour. To use the design, please ensure the data
> source location points to the someData.csv file.
>
> We are using 2.3.2.r232_v20090211. Any help with solving this issue
> would be much appreciated.
>
> Kind Regards,
>
> James
>
|
|
|
|
Re: Nested tables + truncated images + Word emitter [message #485430 is a reply to message #485383] |
Fri, 11 September 2009 17:28 |
|
James,
As a work around can you put page breaks in after each image?
Jason
James Willans wrote:
> Hi Jason,
>
> Thanks, I appreciate your response. Yes this looks to be fixed in 2.5,
> although I have now hit issue #283984 which is frustrating since we
> can't upgrade to 2.5.1 at this stage because of all the other
> dependencies it brings in!
>
> James
>
> Jason Weathersby wrote:
>> James,
>>
>> I believe this has been fixed in 2.5. I tried your report with 2.5
>> and no images were messed up by the page breaks.
>>
>> Jason
>>
>> James Willans wrote:
>>> Hello,
>>>
>>> We have images contained in a table which is itself nested within
>>> another table. When we output the report using the Word emitter the
>>> images are truncated by the page break and sometimes by the right
>>> margin. Please see the attached report "reportTest.doc" which
>>> contains many examples. Note that this does not happen with the pdf
>>> emitter.
>>>
>>> The attached small example report design and associated csv file
>>> reproduces this behaviour. To use the design, please ensure the data
>>> source location points to the someData.csv file.
>>>
>>> We are using 2.3.2.r232_v20090211. Any help with solving this issue
>>> would be much appreciated.
>>>
>>> Kind Regards,
>>>
>>> James
>>>
|
|
|
Powered by
FUDForum. Page generated in 0.04297 seconds