Replies: 9 comments 3 replies
-
Thanks for reporting. Can you supply patches? |
Beta Was this translation helpful? Give feedback.
-
I'm not in the position to make patches . |
Beta Was this translation helpful? Give feedback.
-
The extra paragraphs (and extra tables!!) in MS Word output are caused by the fact that BIRT supports things like border, margin, padding at every possible place. These are supported technically by using nested tables (in the Word output) for almost everything. From the experience with my fork, I think it might be useful to review and discuss some of the changes I made, and maybe merge them into the master branch after making the behavior change optional (e.g. it would be necessary to explicitly opt-in to the changes by setting a render option or whatever. However, I don't have enough time to do this myself. |
Beta Was this translation helpful? Give feedback.
-
I was planning to make an other issue that there should be more types that are not generated as a table ( I think so far only a label is not table). For example a list (and also a grid) also has a use case (especially when making word documents) that you just want to use the expression part of the list, but not the table part. A property not generate as table or something , could that be part of the solution? |
Beta Was this translation helpful? Give feedback.
-
For list items, in my tup_main branch, you can set a UserPropety WordEmitter.LAYOUT_MODE to the string value NONE (not sure about the exact phrasing of the option name). This will cause the List Item to basically work like a for-loop in a programming language: It doesn't provide anything to the output in itself. It just enables you to generate several instances of the content of its detail area. Thus this user options prevents the creation of a word table for a BIRT list item. For texts inside cells, there is a similar optimization preventing nested Word tables (but at the cost of some layout support). |
Beta Was this translation helpful? Give feedback.
-
Ok, then don't get your hopes up to get this resolved. We are not in a position to fix hidden cosmetic things. Transferring this to a discussion |
Beta Was this translation helpful? Give feedback.
-
Just for reference: The tup_main branch I mentioned is here: https://github.com/triestram-partner/birt. See https://github.com/triestram-partner/birt/blob/tup_main/engine/org.eclipse.birt.report.engine.emitter.wpml/src/org/eclipse/birt/report/engine/emitter/wpml/AbstractEmitterImpl.java for the names of the user properties. Define a string user property WordEmitter.LayoutMode with a value of "NONE" for a list item to make it a "for-loop". |
Beta Was this translation helpful? Give feedback.
-
@MSDelorme Could you provide a small example like report so that somebody who is interested can take a look into it, because it is not easy to understand the topic of your note. So I'm not realy understand your topic. Because in the most cases I'm focused on output of HTML, PDF or XLSX. |
Beta Was this translation helpful? Give feedback.
-
@MSDelorme |
Beta Was this translation helpful? Give feedback.
-
Word emitter generates extra paragraph markers in footer and header. Although hidden,it is not necessary.
To put elements in an header you need to add a grid first. When generated in word you can see a hidden paragraph marker in the footer/header before the grid. There are more places that extra paragraph marker are generated but I will make separate issues for that (I mention it here because it could be the sames issue)
Beta Was this translation helpful? Give feedback.
All reactions