[Bug 160485] FILESAVE: Some Cells Text missing in EXPORT.png with highresolution.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=160485

--- Comment #4 from ady <adylo811...@gmail.com> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.