Question - Missing font in PDF export?

It’s the same in the GDPR Data Flow Tree.
Looks nice in Google chrome but crap in PDF.

oh ! i see now! Crap! @kristijan.sabic will issue this for next release

Github issue:
https://github.com/eramba/eramba_v2/issues/2159

Thanks! By the way it seems to me, that this is not only an issue in the trees but also in other charts,
e.g. in the compliance analysis report:
image
or the donut and cake charts in the asset risk summary report (in my reports at least there is no line break issue):
image

I guess it’s all due to the same bug. Just for information to maintain completeness :slight_smile:

yep - is perfect that you let us know this so we try to fix it everyone for once , thanks fabian !

Has this now been confirmed and part of a future bugfix? It is still the same issue in latest release.

you can check rodmap, is not for next release:

1 Like

What happened to this?

We have a similar problem when converting a risk analysis report to PDF.

What version of eramba are you using? Are you on latest 2.9?
I’m asking because this fix was part of release 2.3.

App Version
e2.9.0
DB Schema Version
e2.9.0

Thanks for reporting. I created new issue.

Int. ref: https://github.com/eramba/eramba_v2/issues/2436

This is still not fixed as far as I can tell.

Any ETA?

Its likely to come on e2.15.0 , compliance charts were fixed i think but not risk ones

Hi!

I updated to latest release and still this is in the PDF output

2020-04-02 11_29_53-Window

It would really help if the reports you run just open in a separate browser tab (or maybe some back-end way to achieve that). Then you’d at least be able to print them as PDF if this is an issue that cannot be solved.

the report you showed in post above is which one? is it system report or user report? what section?

It is the PDF output for “System report - Item” on a control

Looking at older reports - you might have fixed the line spacing on the right side of the tree structure - but not the left. I am not sure if that makes any sense?

Yes you are right, we forget to put it there. Fix will be part of 2.16
Int. ref: https://github.com/eramba/eramba_v2/issues/2551