On 10/05/2016 03:07 PM, Michael Stahl wrote:
On 05.10.2016 17:24, Michael Meeks wrote:
Sure - so the PDF import is a bit of a mess; it currently spawns a
remote process using poplar to parse the PDF, and then extracts (via a
it's spelled "poppler" :)
simple text protocol) data from poplar's rendering to re-constitute into
internal ODF callbacks to produce an internal document; at least -
that's if I got it right =)
Poplar/xpdf has a GPL license and so requires all this silliness.
actually the separate process is a potential security advantage, if we
would only realize that and sandbox it properly - C++ based PDF readers
tend to accumulate quite some CVEs...
[snip]
CVE = Common Vulnerabilities and Exposures?:
https://cve.mitre.org/about/
In general - it would be -way- better to pick up something like eg.
pdfium - and add a rendering front-end there to match first, the same
protocol (but we can do this in-process), and subsquently to simplify
and factor lots of that madness out =) PDFium seems to be gaining
traction in browsers (Chrome + Firefox) and so on.
Mr. Stahl, what about this idea of using PDFium?
-regards,
Larry
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.