Created attachment 107554 [details] The picture in the upper left corner is scaled and cut back different A writer document created in a Windows graphic environment scaled to 100% looks different on a system scaled to 125% or 150%. This is evil because it`s hard to find the failure and many people won`t recognize they have a wrong looking version of a document. I recognized the issue because I had pictures in a document scaled and cut back different when using on OS with different scaling.
The document you provided has empty slots for images - I suspect they are linked to file instead of embedded. Also please provide clear, enumerated steps to reproduce. Lastly please try to refrain from the extra language like "this is evil..." - doesn't add anything to the bug report and does not help to encourage our volunteers to give their time for free. Marking as NEEDINFO as the description is not clear and the sample document doesn't load correctly. Mark as UNCONFIRMED after correcting these. Thanks
Created attachment 107588 [details] .odt file with a picture cut back in the upper left corner A. Make sure your windows 7 graphic environment is scaled to 100% following the steps below: 1. In Control Panel, click Appearance And Personalization. 2. Under the Display heading, click Make Text And Other Items Larger Or Smaller. 3. The default scaling options allow you to choose a 100-percent scale (the default), a 125-percent scale, or a 150-percent scale. To use one of these scaling options, make a selection, and then click Apply. 4. To choose a custom setting of between 100 and 500 percent, click Set Custom Text Size (DPI) in the left pane, and then use the Scale combo box to select or specify a scale. 5. You need to log off the user and then log on the user again for the changes to take effect. desktop B. Open the attached file and have a look at the logo in the upper left corner. Close the file. C. Now set your windows graphic env. scaling to 125% by following the steps as described before. D. Open up the attached file again. The Logo should disappear since the picture is cut back and scaled different. Therefore only a white picture can be seen instead of the logo.
sorry for the sloppy speech and the unclear description. I hope it is to satisfaction now. Thanks for your guidance
Hi amon, Thanks for the additional description. Nearly clear to me ;) So the problem is that when you view the document with scaling in the Windows graphic environment, that the picture is ... not shown? white? wrong size ? Maybe you can also make a screen shot for 100% and one with the different scaling? (Sorry, I've no windows to test in) thanks, Cor
Created attachment 107598 [details] screenshot with windows 100% scaling
Created attachment 107599 [details] screenshot with windows 125% scaling
Hi Cor, the attached screenshots should make it clear. It is to be seen that the Picture which has has a lot of whitespace around the logo is cut back to fit the logo into the document. When scaled to 100% the cut back values are different and also the scaling is different. As a result of this, the logo is no longer to be seen in the document, but only the white space of the picture. In Other words: If the background of my picture would be black instead of white, you would see only black area instead of the logo. Im sorry the picture is choosen a bit unlucky becaus of the white background. Best, Amon
thanks Amon, I think that the cropping is related to the problem here ;) So to circumvent you could use a picture that doesn't need cropping. Still, it's a bug and thanks for clarifying. Did you see the problem in previous versions too (I expect it to be an old problem...) I set the severity to normal. (others in QA could point you to the page where that is explained, Sorry I don't know that.) Cor
Hi Cor, Thanks for your workaround guidiance, but it`s not an option to replace all pictures in our company documents. The only solution for now, is to send out a warning to all employees be aware of that bug and check the documents before printing and handing to a customer. I tested one older version but it showed the same behaviour. That was a 4.2.6.x I think. Thanks, Amon
(In reply to amon from comment #9) > Thanks for your workaround guidiance, but it`s not an option to replace all > pictures in our company documents. The only solution for now, is to send out > a warning to all employees be aware of that bug and check the documents > before printing and handing to a customer. I can understand that. Maybe it's an option for your company to pay someone to fix this? There are quite some developers that you could ask http://www.libreoffice.org/get-help/professional-support/ > I tested one older version but it showed the same behaviour. That was a > 4.2.6.x I think. Thanks for that extra check. Cor
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.3 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-20170522
Yes the cropping is broken in LO 5 and greater versions. The reason for this is that the cropping attribute (fo:clip) is dependant to the original size of the graphic. So in general the fo:clip attribute is broken. Other document formats (docx..) are saving croppings with relative values (percentage). They do not have a problem. If now a graphic does not have dpi information saved LO is using the monitor resolution to calculate the original size of the graphic -> and this is wrong... 96DPI should be used in this case as it was the case in OO4.0. This leads to the bug that if a image is cropped on one computer it might look different if opened with another computers.
Dear amon, 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 https://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
Confirming this still is an issue at current master against 7.2.0. Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 4a9eef7849a75ba91806886ea9c96d114c8d56f9 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Original STR were a little unclear. Simply put LibreOffice is not handling the dimensions of the crop portion of an image held in ODF correctly. In the test document, the coordinates from the "cropped" image are being extracted from a sd session with a full A4 page PNG image. That is, that an os/DE scale factor while applied to the VCL canvas is not handled correctly for an inserted image with sd cropping applied to an image held in the ODF archive. If you extract the PNG from the attachment 107588 [details] ODT archive's Pictures folder, to open in draw and apply an sd crop. And then use that to paste into a new Writer document--and then scale the os/DE this is reproducible. Apparent with FlatODT (attached a new sample) as well as an ODT archive.
Created attachment 172274 [details] A test doc in Flat ODT Open the attached with os/DE at current scale. Then close LO and set os/DE to a new scale factor and reopen the document. The proportion of the embedded sd "cropped" image that shows shifts.
I just re-tested related bug #118299 with LO 7.3.1.3 and figured that the issue is gone; from the described symptoms I'd bet this one is, too. Please re-test.
*** Bug 157407 has been marked as a duplicate of this bug. ***
I can reproduce in Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: ro-RO (ro_RO); UI: en-US Calc: CL threaded using the steps that I described in Bug 157407. It reproduces in both Writer and Impress.
Created attachment 189824 [details] odt with image crop scaling issue
The One Home exemplifies the essence of a childrens home, transcending its role as a shelter. https://onewayfarm.org/ It embodies a beacon of hope, providing transformative support for at-risk children. In the heart of every community, such homes stand as pillars of compassion, reshaping futures by instilling security, belonging, and purpose.