At present, if you try to print from a record history widget, the resulting output appears to be vectorized prior to being printed. What is the reasoning behind this?
As a result
Nobody cares or is it unclear what I mean by “vectorizing”? It essentially seems to turn the printout into something like an image rather than just spitting out some standard text…
Hi @sebme - we definitely care, but thank you for the clarification! I had to check with the Tulip product team that owns this to make sure I could answer this correctly.
Basically, there isn’t a strong reason for this other than it was how it was originally implemented many, many years ago 
Unfortunately, changing anything related to printing would require a heavy technical lift that we currently cannot prioritize. Realistically, we’ll only be able to work on this once we implement a new review experience (which should hopefully happen next year).
Thank you, @Beth. Can you have someone please check this again… I mean… look at this: Someone wanted to check a trail and does not have access to any of the workstations… This is what we have to send around… IF it actually get’s finally exported/printed at all.
And on top of that nobody can search it for any data in the end because of the vectorization.
Idea: Just please give us a HTML view of the output with all data with a simple print-ready CSS 
