Even with keep ratio checked, picture does not scale properly for height, resulting in a stretched out appearance.
Please supply sample file (along with screenshot of what is expected/unexpected if possible) & steps to reproduce that problem. Otherwise no one could confirm your report.
Then please mark this bug UNCONFIRMED
Created attachment 82004 [details]
Sample image for scaling failure
Created attachment 82022 [details]
Screenshot of the sample in LibreOffice 126.96.36.199
I am not sure what you are expecting.
This is the screenshot of your sample file in LibreOffice 188.8.131.52. I don't think the image is wrongly scaled.
Created attachment 82023 [details]
Scaled image in 184.108.40.206
This is a scaled image of your sample file, with keep-ratio option on.
This shows correct scaling I believe.
Tested with LO 220.127.116.11, OS X 10.8.4.
Looks good to my eyes.
Adjusting Importance to medium and normal and setting to WORKSFORME.
Sharky, could you post a screenshot of the issue happening and explain what is wrong? If you still see this feel free to re-open.
Created attachment 82025 [details]
No one tested this with 18.104.22.168?
I can add a screenshot later when I get some time, but hopefully this just doesn't occur in 22.214.171.124 or something.
Created attachment 82085 [details]
Screenshot of Image Height Scaling Problem
Created attachment 82086 [details]
More thorough presentation slide of scalling failure
When I switch back to the current version of Writer (126.96.36.199) this scaling problem also goes away. I.e, it only seems to show up in the latest prerelease.
Hi Sharky, James has said on comment 5 that it's ok with 188.8.131.52. Have you tested with that release?
You can only reopened this bug if you reproduce the problem with that release or later.
So we mark that NEEDINFO until you confirm
Unfortunately no, the latest prerelease I see is 184.108.40.206.
It looks like all the cool kids have 220.127.116.11 or something. It's not something I seem to be able to find (nightly builds?)
It's available now, or you could use this link instead:
*** This bug has been marked as a duplicate of bug 65870 ***