Thank you for the answers, they provide very valuable info. So there is no real way to have a generic PDF printer, and each developer have to write its own, by writing its own Paint() function. That was that I though, unfortunately.
Unfortunately, because writing my own drawing function brings another issue in my case: I cannot get back the content of the delegate property encapsulated inside my TableView object, in my qml interface file from the c++ code. More exactly, I can, in the best situation, retrieve a part of these info, by getting back the items already drawn on the user interface, from the TableView cache. But as not all the items may be available in this case, I may miss important info in various scenarios, e.g.for still not painted items. Or I may also hardcode the values to use during the PDF export inside the c++ code to reflect what was did in the qml file.
These solutions may resolve my issue in a certain manner, but are weak in terms of generating good and reusable code, especially when designers are intended to often modify the qml interface during the development cycles.
I perhaps will explore the QTextDocument object, and the way it handles the PDF printing. However I don't know if I really can use this component to replace my qml TableView object, as its organization was exactly what I needed to show my data to the user. I will also take a look in the QtWebEngine solution, but this may work only if the text remains editable in the generated PDF, as I said in my original post above.