I’ve brought this up before but I think it needs reconsideration.
For me, printing is a much wanted feature. Without going into too much detail, one of the reasons I want it is note typesetting.
A while ago I did some fiddling with PDF export but I gave it up for several reasons: the only really free C code I could find was rather old and didn’t cover gradients, transparency and other features very relevant to Juce rendering that have been added to the PDF format later, the PDF format in itself is rather complex, I didn’t know how to embed fonts and images, etc. etc., and on top of that, the graphics rendering system of Juce was undergoing changes so it seemed I was aiming at a moving target.
Now that the rendering seems to have found its new form, I figure it might be easier to add printing. I haven’t studied the new rendering system in detail but as I understand, the refactoring was driven by a need to support accelerated drawing by allowing renderers to work on top of platform-specific accelerated apis like Direct2D.
Now, if Juce can do its rendering via Direct2D, or OSX or Linux equivalents, printing might be a matter of directing the platform-specific api to the printing system.
You would still need printer dialogs etc. Perhaps the native dialogs could be used, they may not look perfect in a juce app but this would still IMO be a lot better than not being able to print.
I know it’s not your highest priority but OTOH, it might come easier now, with rendering code on your fingers.