<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Pdfium based insertion of a PDF as image results in unwanted solid background, enhancement request to support break after insert (comment 4)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=106581#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Pdfium based insertion of a PDF as image results in unwanted solid background, enhancement request to support break after insert (comment 4)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=106581">bug 106581</a> from <a class="email" href="mailto:vmiklos@collabora.com" title="Miklos Vajna <vmiklos@collabora.com>"> Miklos Vajna</a> <pre>See <<a class="bz_bug_link bz_status_NEW " title="NEW - pdfium based ipdf defaults to 96 dpi for image, need an option for higher resolution" href="show_bug.cgi?id=115811#c14">https://bugs.documentfoundation.org/show_bug.cgi?id=115811#c14</a>>, just rendering at higher resolution is not a great idea. For vector output, there are two problems: 1) Skia is the runtime-default on Windows, it's disabled on Linux/macOS by default; so in case pdfium wants to do skia API calls unconditionally, we're not there yet. 2) pdfium itself defaults to agg to produce pixel output, its skia backend is still experimental, see <<a href="https://pdfium.googlesource.com/pdfium/+/refs/heads/master/README.md#selecting-build-configuration">https://pdfium.googlesource.com/pdfium/+/refs/heads/master/README.md#selecting-build-configuration</a>>. Both are possible to solve long-term, but don't expect an instant fix.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>