[#11336] - The report does not export the correct data to Word table

Hello,

We stuck with the same problem, investigated it, and found the “incorrect pixels to points conversion” issue.

In JasperReports, all measures are stored in pixels. Pixels are device-dependent units. DOCX cell paddings are stored in twips (1/1440 inch). Twips are device-independent units.
When DOCX file is generated, JasperReports converts 1 px of each Border Paddings measure to 1 pt (20 twips) of Word table cell paddings measure. That causes vertical overflows of text as shown in the attached picture.

Assuming the 600 x 800 screen resolution and
1 horizontal px = 1 pt = 20 twips,
then
1 vertical px = 600/800 * 1 pt = ¾ pt = 15 twips.

For example, if we set Border Paddings for left, right, top and bottom to 4 px, these measures should be converted to Word table cell paddings so: left and right – 4 pt (80 twips); top and left – 3 pt (60 twips). After fixing that, the same text is displayed in Word table cells without cropping.
In Visual Basic, conversion between twips and screen pixels is achieved using functions such as TwipsPerPixelX and TwipsPerPixelY.

We fixed this problem for our reports by overriding DocxBorderInfo class:

/**
* Overridden Jasper DocxBorderInfo class for fixing pixels to points conversion.
*/
public class OurDocxBorderInfo extends DocxBorderInfo {

public OurDocxBorderInfo(JRLineBox box) {
super(box);
borderPadding[TOP_BORDER] = String.valueOf(verticalPixelsToTwips(box.getTopPadding().intValue()));
borderPadding[BOTTOM_BORDER] = String.valueOf(verticalPixelsToTwips(box.getBottomPadding().intValue()));
}

public OurDocxBorderInfo(JRPen pen) {
super(pen);
}

private static int verticalPixelsToTwips(float pixels) {
return (int) (pixels * 15); // 1 vertical px = 3/4 pt = 20 twips/pt * 3/4 pt = 15 twips
}
}