Description: This started with LO Calc around 6.1.x release. Exporting selection to PDF doesn't work as it uses wrong range (one starting from the beginning of the document) Steps to Reproduce: 1. Create new spreadsheet 2. Type something into cels below default printing range block (in my case this falls between G/H columns and 53/54 rows) 3. Select those cells (for example range from E48:J60) 4. File -> Export to PDF, choose "Selection", confirm Actual Results: Output PDF doesn't have our selection but rather jest range starting from A1:G53 Expected Results: Selected range should be included Reproducible: Always User Profile Reset: No Additional Info: Format -> Print Range -> Define seems to mark desired cells and export works correctly. I would argue that exporting selection to PDF should not mark selected cells (i.e. leave dashed line in the spreadsheet)
Please attach sample document. Sounds like a duplicate of bug 119189.
Created attachment 145328 [details] spreadsheet with example data
Created attachment 145329 [details] pdf with wrong output/range
Created attachment 145330 [details] screenshot of what's been selected and what ranges Calc used
It does look like it's related. I attached example sheet, resulting PDF with wrong output and screenshot of the selection which I made and range that Calc used. I hope it sheds more light on the issue.
Created attachment 145333 [details] selection export i can confirm this. only the first quadrant is exported. printing the selection to pdf has same result. please have a look at the attached picture. Version: 6.1.2.1 (x64) Build-ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc:
export and pdf print was ok in LO 6.0.6.1
Isn't this a duplicate of this https://bugs.documentfoundation.org/show_bug.cgi?id=120161 but this have suplimentary printing to PDF?
(In reply to BogdanB from comment #8) > Isn't this a duplicate of this > https://bugs.documentfoundation.org/show_bug.cgi?id=120161 but this have > suplimentary printing to PDF? yes, looks like both issues have same root cause *** This bug has been marked as a duplicate of bug 120161 ***