Created attachment 144419 [details] logo/image that is destroyed during export to pdf I have an image which i would like to put into a writer. This works as expected, the image is shown as it should. When i export this now as PDF, the image gets messed up horrible. It makes no difference if the image is a .png or a .jpg. Only with .svg it works.
affects both latest stable releases, 6.0 and 6.1
i had to use openoffice now because i urgently need that document. it works in openoffice 4.1.5
Created attachment 144425 [details] Result of PDF-Export For me everything looks normal (if you consider, that the image-file is very small) I did the export with Version: 6.0.6.2 (x64) Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
Created attachment 144427 [details] export of logo anchored as Char Can not confirm on Windows 10 Home 64-bit en-US with Version: 6.1.0.3 (x64) Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: en-US (en_US); Calc: CL Also, settings on the PDF export dialog will control the compression quality and and resolution--defaults may not be set to your liking The logo (the PNG in attachment 144419 [details] ) is exported with its full resolution of 72dpi with "lossless" compression set. Please post a screen clip, or the resulting PDF, showing the "destruction" noted.
Created attachment 144432 [details] source odt
Created attachment 144433 [details] resulting pdf
i added the source odt and the resulting pdf maybe something is wrong with my pdf reader or with the settings in my writer
it also looks that wierd in chromium, so i think its not a viewer problem. i am running win7 x64 GER
I could export your odt-file without any problems. I also could had wrong image in your PDF. So I think, there is something wrong with you PDF-Export.
can you tell me what i have to delete to have a clean new install of libreoffice to get rid of that behaviour?
I'm no expert, but if a simple update doesn't help, you can a) try it with a fresh user profile (see https://wiki.documentfoundation.org/UserProfile) b) try with the master (separate installation) from https://dev-builds.libreoffice.org/daily/master/
i deleted libreoffice and the folder in appdata/roaming/libreoffice after installing again version LibreOffice_6.0.6_Win_x64.msi, it is still the same behaviour.
I extracted the source.odt file contents. The image in the source.odt file is a very poor quality BMP which is only 77x97 pixels (100000000000004D00000061606A3C89746C458A.bmp). In the ODT file the display dimensions on the image are set to approx. 0.8in x 1in. Even at 300 DPI this image would have to be approx. 240x300 pixels. So you have a very bad quality, very small image being enlarged. I assume it also looks as bad in print as well as in Export to PDF. Or am I missing something here?
i know that the picture is very bad, i can't change that as i do not have another one in .svg or high res jpg. But when i export this .odt with openoffice, its fine. When i export it in libreoffice, its messed up. So something is wrong here. It zooms in the shield of the bear - this can not be correct. no matter how bad the quality of the image is.
LibreOffice seems to have problems with images which have virtually no metadata inside. I am now remembering seeing this before. So use an image editor to losslessly convert it to a PNG. That should add proper metadata. My guess is that then it will at least look the same as OO. Please come back and let us know if that works.
I already tried that with windows 7 paint - opened it and exported it as .png/.jpg/.bmp - no change, same behaviour. The only thing that seems to work is to online convert it to .svg but then i lose a lot of details
What is the original source of this image? Perhaps there is a way to aquire it at better quality.
An old men who sent it to me in a .doc letter.
s/letter/email
I tried with your odt and cannot reproduce the "shield zoom" on Windows with 6.0, 6.1. Neither on Linux with 6.1, 6.2. As you tried deleting your profile, I guess you were using the default PDF export settings after that. I can't figure out what could be different in your case.
I just removed everything from libreoffice (including appdata/roaming/libreoffice), installed LibreOffice_6.1.1_Win_x64.msi, downloaded the .png, went into libreoffice writer "insert" -> "picture" (the "" are guessed, i have the german version so it is "einfügen" -> "bild"), created a pdf and it behaves the same wierd way. I have absolutely no idea what could cause that and i do not understand why no one is able to reproduce that. iirc i also was able to easily reproduce that on linux too, with fedora 28. I always use default settings in libreoffice, absolutely standard, so it is no problem to delete the roaming folder.
Do you get the same result if you use a special PDF Creator (like PDFCreator or PDF24) or is it only if you use the PDF-Export from LibreOffice?
Just tested the pdfcreator - with that it works as expected when i convert the .odt to .pdf
I could reprodeuce it, when I choose "Export directly as PDF". If I choose "Export as PDF, everything is O. K. Version: 6.2.0.0.alpha0+ (x64) Build ID: 62cd86977ca41677c56fb2d1f97bb1c5cbdbd416 CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-20_02:34:32 Locale: en-US (de_DE); Calc: CL
(In reply to Dieter Praas from comment #24) > I could reprodeuce it, when I choose "Export directly as PDF". If I choose > "Export as PDF, everything is O. K. > > Version: 6.2.0.0.alpha0+ (x64) > Build ID: 62cd86977ca41677c56fb2d1f97bb1c5cbdbd416 > CPU threads: 4; OS: Windows 10.0; UI render: GL; > TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-20_02:34:32 > Locale: en-US (de_DE); Calc: CL I cannot repro even with directly, Win or Linux. Maybe some underlying settings thing after all?
I did some further test, because I suddenly could reproduce it with "export as PDF" also. My observation: If you reduce JPEG compression to 90%, I get the messed image; if it is 100%, everything is O. K. Tested with Version: 6.2.0.0.alpha0+ (x64) Build ID: 62cd86977ca41677c56fb2d1f97bb1c5cbdbd416 CPU threads: 4; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-20_02:34:32 Locale: en-US (de_DE); Calc: CL
(In reply to Dieter Praas from comment #26) > I did some further test, because I suddenly could reproduce it with "export > as PDF" also. My observation: If you reduce JPEG compression to 90%, I get > the messed image; if it is 100%, everything is O. K. 90% is the default, though. I tried with different DPI reduction settings, but still could not repro.
Dear libre, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No reliable repro steps and no repro in general. Please put to New only with exact repro steps and PDF settings after profile reset.
Dear libre, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
(In reply to LibreTraining from comment #15) > LibreOffice seems to have problems with images which have virtually no > metadata inside. I am now remembering seeing this before. Bug 52598 and bug 96178. Needinfo for exact steps, also needs to be searched for being a duplicate.
Dear libre, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp