Bug 155889 - the exported *.png image can't be seen normally as the initial image
Summary: the exported *.png image can't be seen normally as the initial image
Status: RESOLVED DUPLICATE of bug 144195
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-17 05:01 UTC by solar020
Modified: 2023-06-19 10:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
It's a *.png image of the site mentioned in bug description (1.23 MB, image/png)
2023-06-17 05:01 UTC, solar020
Details

Note You need to log in before you can comment on or make changes to this bug.
Description solar020 2023-06-17 05:01:26 UTC
Created attachment 187955 [details]
It's a *.png image of the site mentioned in bug description

Simple explanation:
==================

  1. Right-click attachment and select "Open with -> LibreOffice Draw"
  2. Export to *.png
       and in PNG Options set "Resolution:" to 300dpi (pixels/inch)

  Conclusion:
    Bug: I can't see the exported *.png image as I can see the *.png image in 
           attachment that was opened with LibreOffice Draw 
          (particularly I can't see/read the text in the exported image as I can 
           see/read the text in the image before opening it with LibreOffice 
           Draw).


  Note:

    To be honest I don't even know exactly if this is a bug or if it is simply 
       something that isn't behaving as expected.


  Explanation of what I was expecting:
  ===================================
    
    Before I open the image with LibreOffice Draw, if I open the *.png image in 
      attachment in Firefox and then click in the image to zoom it, I can see 
      the image normally including the text in it.

    If I try to do exactly the same with the exported *.png image I cannot see 
       the image normally anymore I can't even read the text in it, I mean if I 
       open the exported *.png image in Firefox and then click in the image to 
       zoom it, I cannot see the image normally as before I can't even read the 
       text in it.

  And now you ask, why are you exporting to *.png an image that is already a
  ==========================================================================
       *.png image ?
       ===========

  Answer: Well, what I was trying initially was something similar but slightly 
  ======      different, initially I was trying to export the same *.png image 
              in attachment but with a "Text-box" inserted containing the text: 
    "https://www.intel.com/content/www/us/en/processors/processor-numbers.html" 

     and I tried to see in Firefox the exported *.png image of that and I 
     couldn't see it too as before not even read the text in it, so I've decided 
     to do even simpler which was what I described you in this bug report which 
     is simply open a *.png image with Libreoffice Draw and then immediately 
     export it as *.png, setting "Resolution:" to 300dpi (pixels/inch) and I 
     couldn't see it either not even read the text in it and 
     that's why I've decided to report this behaviour as a bug.

  Note2: The *.png image in attachment is basically the site above mentioned I 
             screenshot with Firefox right-click "Take Screenshot" option.
Comment 1 Stéphane Guillou (stragu) 2023-06-19 10:02:46 UTC
The underlying issue is that the dimension values are linked to the DPI values in that dialog, meaning we end up with the same file when changing the DPI value (whichon top of things doesn't have DPI information stored in it).

Relevant bugs:
- missing DPI info: bug 132959
- link between dimension and resolution: bug 144195

Workaround is to first change the DPI, _then_ change the dimensions to something bigger.

I'll mark you report as a duplicate of bug 144195 so we can focus on resolving that poor PNG export UX, hope that makes sense.

*** This bug has been marked as a duplicate of bug 144195 ***