Problem description: I need to convert multi-page TIFF file to PDF. When I open a multi-page TIFF file is opened only the first page. Steps to reproduce: 1. .... 2. .... 3. .... Current behavior: When I open a multi-page TIFF file is opened only the first page. When you select File -> Export to PDF ... converted only the first page Expected behavior: Means to LibreOffice convert multi-page TIFF file to multi-page PDF Operating System: Windows 7 Version: 4.0.2.2 release
please upload a multipage .tiff file so we can test it
Created attachment 78318 [details] multi-page *.tiff multi-page *.tiff
I confirm that LibO 4.0.2 only loads the first page of that multipage .tiff file. PDF export only converts the first page as well. I wonder if previous versions of LibO did support multipage or not.
same issue on LibO 3.6.4 either on loading or PDF exporting I suspect the same applies even to previous release. probably LibO has never handled multipage TIFF as expected.
What needs to be done to make this functionality were present?
I'm not a developer, so I can't help fixing it. I can just confirm the issue.
confirming issue on LibO 3.4.4 as well, so changing the version field. I strongly suspect that multipage TIFF handling has never been available in any LibO release.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1.2 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
Confirmed. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
Created attachment 118871 [details] sample multipage tiff tiff file taken from here - http://support.leadtools.com/SupportPortal/CS/forums/44475/ShowPost.aspx
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I can confirm this bug on LOo, 5.2.x on linux and windows.
still repro in Version: 6.1.0.0.beta2+ (x64) Build ID: fe1a23b5c49c94410a604c8d4a6f50f43d575403 CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:libreoffice-6-1, Time: 2018-06-17_06:31:41 Locale: ru-RU (ru_RU); Calc: CL but may be it's enhancement?
We do actually import the full set of images, the UI isn't great around this and we don't export the way the original reporter has in mind. But FWIW in impress, insert image and insert this example, ensure it's selected in the ui, then insert, media, animated image and pick the "apply objects individually" button and at the top of this dialog there is a spinbutton which can be used to cycle through the images contained in the .tiff. (This is clearly intended for old-school animated gifs) Why this UI is in impress only and not even draw I don't know, and how to use that dialog effectively is also a bit of a mystery, but we are reading all the images in a multi-image tiff so its not a failing of the import filter.
I too see this problem in version 7.4.2.3. I'm too looking for a possibility to export a multipage TIFF to PDF.
This is now fixed in trunk, and will arrive with 24.2. *** This bug has been marked as a duplicate of bug 155444 ***