Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337767 - Paddings and margins are ignored for cells in DOC reports.
Summary: Paddings and margins are ignored for cells in DOC reports.
Status: CLOSED DUPLICATE of bug 302108
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7.0   Edit
Assignee: Birt-Report-inbox@eclipse.org CLA
QA Contact:
URL:
Whiteboard: Obsolete
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-21 15:56 EST by Stanislav CLA
Modified: 2011-05-26 13:32 EDT (History)
1 user (show)

See Also:


Attachments
Example report design to reproduce the problem (10.17 KB, application/xml)
2011-02-21 15:59 EST, Stanislav CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav CLA 2011-02-21 15:56:41 EST
Build Identifier: Build id: M20090917-0800

I've created simple report design with a table with 1 row and 1 cell. Added a Text element and set left Margin to 30 pixels. The PDF report looks good, the text is moved on right from the beginning of the page, but when export as DOC the text starts from the beginning of the page.
Same happens with Left Padding. 
There is similar bug:
Bug 180657 - Padding and margin don't take effect in word emitter[1202]

but it is reported in 2007 and the solution is - we do not support margins in DOC files :(

Reproducible: Always

Steps to Reproduce:
1. Create new report design
2. Add table with 1 details row and 1 column
3. In the only cell add Text element with some text.
4. Set some (30 pixels) Left Padding to the Text element (or the cell, doesn't matter)
5. Export as PDF and DOC
6. Compare both - the text in DOC file is not moved on right
Comment 1 Stanislav CLA 2011-02-21 15:59:41 EST
Created attachment 189444 [details]
Example report design to reproduce the problem
Comment 2 Xiaoying Gu CLA 2011-02-21 21:41:47 EST
Discuss of this issue can be found in #217066, #302108.

Set as duplicated of #302108

*** This bug has been marked as a duplicate of bug 302108 ***