Description: I want a scaling upped image using "Export as PNG" on Calc, but the exported image was not what I was expecting. I tested and tested, Finally I found a Mysterious bug. Steps to Reproduce: 1. Create a sheet. 2. In 1st cell, Type a string using English only. 3. In 2nd cell, Type a string mixing English and Japanese(日本語). 4. In 3rd cell, Type a string using Japanese(日本語) only. 5. Select between 1st and 3rd cells. 6. Choose File -> Export, then choose "PNG" type. 7. Check on "selected". 8. Click "save". 9. Change DPI and size, then click "OK". Actual Results: Scaling up and locating of 1st and 3rd cells are correct. But 2nd cell is NOT scaling up and locating always. Please see the attached images. Expected Results: 2nd cell is scaling up and locating the same. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 151527 [details] File "Export as PNG on Calc.ods"
Created attachment 151528 [details] Image of 96 dpi (default) scaling.
Created attachment 151529 [details] Image of 120 dpi scaling.
Created attachment 151530 [details] Image of 150 dpi scaling.
Created attachment 151531 [details] Image of 192 dpi scaling.
Comment on attachment 151528 [details] Image of 96 dpi (default) scaling. All cells are correct.
Comment on attachment 151529 [details] Image of 120 dpi scaling. 2nd cell is NOT correct.
Comment on attachment 151530 [details] Image of 150 dpi scaling. 2nd cell is NOT correct.
Comment on attachment 151531 [details] Image of 192 dpi scaling. 2nd cell is NOT correct.
I can reproduce this in 6.1.6 on Windows 10. Version: 6.1.6.3 (x64) Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU threads: 2; OS: Windows 10.0; UI render: default; Locale: zh-CN (zh_CN); Calc: group threaded BTW, I am not sure whether it's the language barrier or not, but changing DPI doesn't trigger the bug for me, instead changing image size does. At least on my setup, changing DPI doesn't automatically change the image size in pixels, but changes the image size in inches while keeping the pixel size. When I kept the image size in pixels the same, but increase the DPI to 192, I got a correct image. On the other hand, when I increased the image size in pixels but kept the 96 DPI, I could reproduce the bug. It also happens to mixed-language cell for English and Simplified Chinese.
Created attachment 151898 [details] PNG export dialog This is the dialog I get when I export the selection to PNG. How can I change the DPI or size ?
Setting to NEEDINFO until the information has been provided
(In reply to Xisco Faulí from comment #11) > This is the dialog I get when I export the selection to PNG. How can I > change the DPI or size ? To change the image size, edit the "Width" or "Height" box to a diffrent number (only one, they seem to be linked); and for DPI, edit the "Resolution" box (if you change the drop-down option after the box to "pixels/inch", you'll see the default 96 DPI (acronym of dots per inch) we've mentioned). As I said, in my case, changing DPI will automatically change the physical size (in centimeters or inches) while keeping the pixels intact.
I can reproduce it from scratch as described using Version: 6.3.0.0.alpha1+ Build ID: f6e7dbccf063767c2ac87c6460bd1004df742081 CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-05-30_00:13:29 Locale: de-DE (en_US); UI-Language: en-US Calc: threaded Export of cell with mixed languages is wrong.
Dear i.kato80, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear i.kato80, 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
The issue here is not the language, but the fact that the cell has multiple lines of text. Marking as duplicate of more recent bug 137263 as it is more clearly described there. Thank you! *** This bug has been marked as a duplicate of bug 137263 ***