https://bugs.documentfoundation.org/show_bug.cgi?id=169315
--- Comment #13 from Eyal Rozenberg <[email protected]> --- (In reply to Heiko Tietze from comment #10) > I see no actual use case that is broken, and you all get why the PDF is > inserted as raster graphics. So why bother with a confusion? My take: WF. Well, 1. A PDF is not a PNG. If we insert a PDF, in any other way than clobber it into a PNG with the original gone forever - we can't refer to it as a PNG, that's lying to the user and is itself unacceptable. And indeed, as Stuart Stuart points out, we don't fully-clobber, we remember that it's a PDF that we might do something with. 2. When inserting a PDF, at least a choice of page to display is important to offer (if not, in fact, a choice of whether to rasterize a page or just show an opaque PDF icon). That is bug 114234. When that is implemented, we will need to tell the user which page has been rasterized, which we can't do if we claim it's just a PNG image. Plus, we don't need a complicated fix for this bug. It could just be: "Type: PDF (rasterized first page)" or "Type: Rasterized PNG image (from PDF)" or whatever. -- You are receiving this mail because: You are the assignee for the bug.
