https://bugs.documentfoundation.org/show_bug.cgi?id=45789
--- Comment #44 from Lionel Elie Mamane <lionel@mamane.lu> ---
(In reply to kerem from comment #43)
In comment 24, reportbuilder creates an odt file, not through Writer. I
can't this. How to create odt file?
An ODT file is basically a ZIP structure with XML in it.
In reportbuilder, the Java top-level class that does the process seems to be in
file
reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java
(in combination with the external jfreereport), but that is not where you will
need to intervene, but in the code that creates a table row.
The code responsible for a cell is basically
reportbuilder/java/org/libreoffice/report/pentaho/layoutprocessor/TableCellLayoutController.java
My original idea was to find the code responsible for a row and inject the
attribute for "fit to size" row height there. However, now that I take a fresh
look at it, I realise that the <table:table-row> tags are probably copied
unchanged from the report definition. So it might be easier to change the way
the report definition is saved rather than the way it is processed.
The saving of the report definition happens in C++, in
reportdesign/source/filter/xml/
I think it is particularly in reportdesign/source/filter/xml/xmlExport.cxx
function void ORptExport::exportContainer(const Reference< XSection>&
_xSection)
looks relevant; need to set the right attribute or style for "automatic height"
there.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Bug 45789] automatic row height in reports · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.