Created attachment 131887 [details]
See sample XLS and XLSX with specific margin and header/footer settings. When it's exported to PDF in Calc, part of the header and footer is cut off. Not sure if the margins make sense, but in Excel they are exported fine.
In Calc enabling AutoFit height in Format -> Page..., Header/Footer tab fixes the behavior, but also changes the value of height when the spreadsheet is saved.
Tested with LO 126.96.36.199 / Windows 7.
Created attachment 131888 [details]
Sample XLSX (same as XLS)
Created attachment 131889 [details]
Exported PDF (from Excel)
Created attachment 131890 [details]
Exported PDF (from Calc)
It's visible on print preview, you don't need to export as pdf.
I don't understand, except LibreOffice doesn't import fine the 'Autofit' option, why it should be applied as if it was disable?,
what is then the purpose of the option?
Build ID: d3b5bd4a07a619db6bee1c39c32280ac3c620532
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Sorry, sure I'm who is wrong, but I don't understand what is the bug?
m.a.riosv: If Excel prints the .xls document in question (perhaps to PDF) without clipping the header and footer, so should LibreOffice.
There is a Real Paying Customer who complains about this.
Has not excel 'Autofit' option?, if so, with it enable should work on both LibreOffice and Excel.
What about LibreOffice users having 'Autofit' disable just because it doesn't change the height?
How to know when LibreOffice are going to take care of it, maybe it should be eliminated as option.
- Enable it by default on opening excel files, but who knows what other customer with excel files using the option disable can think about this change.
- Insert also the option enabled by default ,on export as pdf dialog, for excel files.
Introduce a bug to make some happy, perhaps breaking the work of others?
At the end I don't why I care about this matter, I only use it occasionally,
but I do not like to say yes to everything, against what I think.
Please think twice about how to solve it. :)
Anyway, the customer is happy with a workaround, so I am not working on this any more.
** Please read this message in its entirety before responding **
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 http://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!