Description: Hello, when inserting a PDF as an image into a writer page (using "insert a picture"), there is no dialog window to choose the page of the PDF. Only the page 1 can be inserted. If the PDF file is a multipage, there is no way for inserting directly another page, you first have to separate pages in another software. Maybe, a dialog window could appear when Writer detects that the file is a multipage PDF, asking what page you want to insert. Steps to Reproduce: 1.having a multipage file 2.open a new writer document 3.click on "insert a picture" 4.choose the PDF file Actual Results: You can only import page 1 of the PDF (no choice in the dialog window) Expected Results: the dialog window should ask "what page would you insert ?" Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.5.2 / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 4; OS: Mac OS X 12.6; UI render: default; VCL: osx Locale: fr-FR (fr.UTF-8); UI: fr-FR Calc: threaded
Currently this is not supported. What some users do is to insert as a Draw OLE object and then edit the OLE object using Draw. See: https://ask.libreoffice.org/t/insert-multi-page-pdf-as-image-how/77007/7 However, this is not a perfect solution. IMO this is an interesting request. Let's hear the opinion of the UX team.
(In reply to Rafael Lima from comment #1) > Currently this is not supported. What some users do is to insert as a Draw > OLE object and then edit the OLE object using Draw. See: > Insert PDF as image was implemented for bug 89727 and uses a different pdfium render engine rather than cairo. Additional enhancement is still needed to work against multi-page PDF. In the meanwhile, users continue to need to extract PDF pages external to LibreOffice, for which the PDFtk or ghostscript work well. Using the cairo based PDF importing to a draw canvas (or to Writer or Impress) sufferes from poor fidelity in rendering the PDF elements to Draw objects. Fidelity is poor compared to the pdfium based insert. *** This bug has been marked as a duplicate of bug 114234 ***