Created attachment 193436 [details] Test Kit Steps how to reproduce with Server Installation of Version: 24.8.0.0.alpha0+ (X86_64) Build ID: 2146e66d8df2b7b6a2dd868e886cae76aaf7f48b CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE; Theme: Colibre Calc: threaded – normal Test Profile created from 7.6 and also newly created User Profile 0. Download and unzip TestKit 1. Open SampldDocument.ods 2. Click cell CX3 and with select range CX3 - A1 3. Release Mouse Button » Area keeps highlighted / selected 4. Menu ˋFile → Export → Format = PNG → (Keep Auto-Filename-Extension and "Selection" checked → Exportˊ » Export Dialog appears 5. ˋRadio button "Modify Dimensions" → in Width add a "0" left from comma → <TAB> for reaching Height fieldˊ » Height value also becomes more or less ten times as much, similar to width. 6. ˋKeep resolution at 96 px/inch → Interlaced and Transparency unchecked, Compression = 9 → [ok]ˊ » PNG will be created 7. Open PNG in IrfanVIEW Expected: looks as SampldDocument.png from TestKit, all text contents included 😉 Actual: Text in row 2 is missing as in SampldDocument_HR.png from test kit.
I wasn't able to reproduce the same behavior in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Attempting to reproduce the bug results in a PNG file that is corrupted.
(In reply to Armondo Lopez from comment #1) What kind of corruption?
The file itself was corrupted, so I was unable to access the PNG file whatsoever.
The STR in comment 0 are slightly inaccurate, but anyway... (In reply to Rainer Bielefeld Retired from comment #0) > 5. ˋRadio button "Modify Dimensions" → in Width add a "0" left from comma → > <TAB> for reaching Height fieldˊ > » Height value also becomes more or less ten times as much, similar to > width. The problem is the value for this pair of fields. With a higher value in the "Width" field, the content of the cells is exported "too high", moving it upwards (as opposed to keeping the content of the cells within the cell's limits). This is probably caused by the "angle" of the content (80 degrees), or by not being horizontal text. This seems to be the reason for the incorrect export if the cell's content. NOTE: the problem only happens when Interlaced and Transparency are both _unchecked_. Now, the following step: > 6. ˋKeep resolution at 96 px/inch → Interlaced and Transparency unchecked, > Compression = 9 → [ok]ˊ > » PNG will be created ... is inaccurate. Either you set the Width/Height fields, or the resolution ratio. When you modify both alternative settings, one of them has to be adapted. > Actual: Text in row 2 is missing as in SampldDocument_HR.png from test > kit. The content of the cells is not missing; it is exported but not within the cell, because of the non-horizontal content of the cells. If you don't modify the Width/Height fields, you should see the cell's content. If you make the values slightly higher than the original, the cell's content "moves up" in the exported PNG. Make a third export with even higher values... Repeat several exports with higher values each time, and you should see the cell's content "moving" upwards, until it is not seen. Please let me repeat: the problem only happens when Interlaced and Transparency are both _unchecked_. I would suggest to modify the Summary field of this report accordingly to my findings. (In reply to Armondo Lopez from comment #3) > The file itself was corrupted If the original value of the Height field is "too big" (e.g. multiply the original value by 100 instead of by 10), then the resulting png is corrupted.
Ah. You are correct. I was able to reproduce the same behavior in the versions I listed above. I see what you're saying when it comes to the values of the various fields contributing to the information being missing.
This is the same issue as bug 137263: some text does not get scaled with the rest. Bug 137263 is originally about wrapped text, but let's include rotated text in it too. *** This bug has been marked as a duplicate of bug 137263 ***