18 Jan
2017
18 Jan
'17
9:23 p.m.
I think this is a good idea for the future, but not right now. There are
several things that current browsers don't support yet, such as the
ability to specify page size and orientation, setting custom headers and
footers, and we'd need to work more to generate the cover and ToC. With
FOP we can control exactly how things work in all browsers, while
leaving this part to the browser is guaranteed to lead to inconsistent
and buggy output.
On 01/18/2017 08:54 AM, Vincent Massol wrote:
Hi devs,
We have plenty of existing limitations in our PDF export (table autoresize, etc) which
comes from FOP and our usage of it. And it’s hard to improve it.
I’d like to propose the following:
* Promote the browser’s print to PDF feature instead of our PDF Export by triggering the
browser’s print feature when clicking on Export > PDF in the UI.
* Work on our print.css so that it has all the styles we have in view mode (right now for
ex, info boxes for ex do not have a nice style).
* Move our PDF Export java code out of xwiki-platform and into an optional extension that
we move into xwiki-contrib. The use case for it would be when you need to generate PDF
from scripts.
WDYT?
Thanks
-Vincent
--
Sergiu Dumitriu
http://purl.org/net/sergiu