Replies: 2 comments
-
I created a PR #1262 which implements 1) and 2):
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Fixed with PR #1262. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Way back in 2013, some kind of support of the CSS
overflow
property was added to BIRT.Unfortunately, the default in BIRT is
hidden
which is different from the CSS defaultvisible
.This is causing me headache in the BIRT DOCX emitter, because the emitter respects this setting and thus long words get truncated.
A long word is a word that is too wide for the cell. This is not uncommon in German, e.g. "Bundestagspräsident".
Other users experienced the same issue.
See #1013 where I proposed a dirty workaround in the report.
I tried this workaround last week, but the designer would not accept the modified XML.
Anywy, even if it works, it is a really ugly workaround.
What makes things difficult here is that
overflow
property cannot be specified in a style in BIRT.I think the latter is an incorrect consequence of the first point; the original developer probably thought: If it cannot be inherited anyway, so why use it in a style?
But IMHO this is a misconception and it absolutely makes sense to specify the property in a style.
We don't have cascading style sheets in BIRT anyway. With "inheritance", BIRT means that e.g. a property of a cell can be inherited from the same property at table level. So "inheritable or not" is only related to the layout element tree structure in BIRT, but not to inherited CSS classes.
I propose to make the following changes to BIRT and I'm asking you for your opinion here:
overflow
to bevisible
instead ofhidden
.Not sure about:
3) Allow overriding the default value for
overflow
with a RenderOption for the emitter, similar to PDF_WORDBREAK for the PDF emitter.4) Should we increase the version number of the RPTDesign XML file? I don't think this is needed. It's only a changed default value, and probably 99% of all BIRT reports don't care about this anyway.
Note: The PDF emitter needs emitter options to support this. I'm always using
Beta Was this translation helpful? Give feedback.
All reactions