-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Defective PPTX format in BIRT 4.9.0-20220204-win32 #813
Comments
Can you provide an example report that reproduces this error? |
Attached you will find 2 reports:
Any sort of help is very much appreciated |
Ok, I have narrowed down this error to a faulty handling of margins in the pptx emitter. |
Null guard for when DimensionType.parseUnit() fails in PPTXUtil.convertCssToEnum(). This happens typically when the cssDimension is "auto" for margins, which really should have a special case treatment in the TableWriter.endCell(). However, from the look of it, the "margin" code in endCell needs a lot of refactoring and should perhaps be done in other places in PPTXCanvas instead ( .drawText() etc )
@joachim-wesenberg : We have fix for this in PR #818. Please try it out. You can find the builds here: https://github.com/eclipse/birt/actions/runs/1811619251 |
OP said that PR #818 fixed the issue. |
PR is not merged yet, so this only works in the CI build. |
Null guard for when DimensionType.parseUnit() fails in PPTXUtil.convertCssToEnum(). This happens typically when the cssDimension is "auto" for margins, which really should have a special case treatment in the TableWriter.endCell(). However, from the look of it, the "margin" code in endCell needs a lot of refactoring and should perhaps be done in other places in PPTXCanvas instead ( .drawText() etc )
Using Run/View Report/As PPTX
will generate output which is not recognized by Microsoft Powerpoint nor LibreOffice. It did not work in BIRT 4.7 either. However, in 4.7 the ODP format was supported and could be used to produce PPTX slides via LibreOffice (convert ODP to PPTX) as a workaround.
Are there any plans to have that fixed or would you suggest to stay with BIRT 4.7?
The text was updated successfully, but these errors were encountered: