Description: Compress Image, reducing image resolution actually increases resolution Steps to Reproduce: 1. Open the attached file 2. Format -> Image -> Compress 3. Actual image dimensions: 640 x 480 px -> After compress 1599x1200 at 300 DPI Actual Results: The checkbox is misleading, does not always do what is promissed Expected Results: Redesign the compress dialog. A) Show the boxes to be interconnected. Change DPI lowers/increases (height/width). Some as touching height/width.. affects resolution B) Please add a similar to the one for PNG/JPG export options -> File -> Export -> select JPG/PNG format -> Press Save. I don't really like to work with pixels... and of course.. more coherent.. C) And the 'actual dimensions' stuff needs to go. Why do I want to know the size at, for me 96 DPI. The file itself has a DPI ratio already... D) Let compress resave the file in the current image format (if png/jpg). Why convert JPG to PNG/ and backwards Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: b8fb7ecd9cdbe1898c41eaecd9894df8e8f01e25 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc:
Created attachment 160297 [details] Example file
Created attachment 160298 [details] Screenshot
So you mean _Reduce_ image resolution is sometimes _Enlarge_ and we better name it _Change_? a) The width/height/resolution fields depend on each other and changing the dpi result in larger/smaller dimension. b) AFAIU, jpg and png compression are just two methods here and both can be applied to the selected image. c) I like this info. And it's just one label. d) I believe it's a misconception. Admittedly the user is not to blame. So some dev input needed too. Tomaz, you are the expert for images :-).
telesto - See Also - bug 115464 Good catch, now I cannot object anymore. But let's forward the discussion to this ticket (incl. a mockup). *** This bug has been marked as a duplicate of bug 115464 ***
(In reply to Heiko Tietze from comment #4) > telesto - See Also - bug 115464 I can object, the see also was for inspiration purposes only.. This is about the Writer Compress Dialog, not the PNG export dialog
a) If there is an easy way how we can show visually these are inter-connected then sure. b) What should we add exactly? The logical dimensions don't make sense because that would change the size of the image in the document and I don't think this is the job of this dialog. c) Sure, for logical dimensions, but pixel size is important. d) Because it depends on what you want to do. JPEG compression is lossy, PNG lossless. If you have a PNG that takes a lot of space and want to compress it more - you can change to JPEG. If you have a JPEG and don't want to degrade the image more, you can choose to save it as PNG.
I would love a mockup... in the same direction as attachment 142672 [details]
*** Bug 131116 has been marked as a duplicate of this bug. ***
Quote from Justin L bug 131116 "Image compression appears to be more accurately a "resize" rather than a compression. The default compression value is 300dpi (in LO 7.0), and for an image with a smaller DPI already, it will expand the image to 300dpi, increasing the filesize for no apparent benefit. I can't really think of a reason why anyone would want to force a reverse compression, so probably it should just do nothing in this case. This will especially be important when <hopefully> there will be option to compress all images in the document. When used interactively, it could be argued that the user has all the information they need to determine whether or not to compress. True enough for a knowledgable user, but there can probably be some improvements here. One possibility would be to set the default to min(currentViewsizeDPI, 300) [an interesting easyhack?]. The other option would be to add a (by default enabled) checkbox to only compress."
Mockup for a UX/UI solution with mockups is in bug 115464.
Compression dialog can't use the same solution.
> Mockup for a UX/UI solution with mockups is in bug 115464. e.g. https://bugs.documentfoundation.org/show_bug.cgi?id=115464#c40
(In reply to edera from comment #12) > > Mockup for a UX/UI solution with mockups is in bug 115464. attachment 168197 [details]
I can object because the view was just intended as an inspiration. The PNG export dialogue is unrelated to this and is not discussed here. I also looked at https://jpegcompress.com site for interior design.
Please also see some very relevant comments in Bug 145161.
See bug 77407 comment 9, especially the resolution limit which prevents the compression if the image resolution is below this limit.
(In reply to tylergloria from comment #14) > I can object because the view was just intended as an inspiration. The PNG > export dialogue is unrelated to this and is not discussed here. I also > looked at https://jpegcompressor.com site for interior design.
Dear Telesto, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug