Do you want to: Report a bug
OS version: Win 11 Pro
App version: 9.4.0.129 (x64 exe)
Downloaded from: ONLYOFFICE website
Additional information;
Export to PDF from a Spreadsheet page is fields as “### …” far more aggressively than it should.
With a spreadsheet view of ;
the date fields are not cramped for space from their appearance.
And even the view in Print preview would confirm this;
which is what I would expect to see on the PDF rendering, but instead the following results;
which is less than ideal.
I opened the document in Libre, and did the similar pdf generation, and got a result of;
In a similar document, I avoided the data hash conversion by widening the fields to almost double, and the hashing was avoided, by the document was unusable as it rendered on multiple pages as a result.
I created this document in 2019, and it is reused on an annual basis since then without issue, until now, so this effect has no precedence.
Hi @DavidRGreen, thank you for the detailed report!
Could you please save a copy of this .xlsx aside right now and attach it here — before saving and reopening it in ONLYOFFICE?
Also, does closing and reopening the file fix the export on your side this time as well?
G’day @Nurullo ,
Thanks for taking an interest in the issue, but I have just found out that I cannot replicate the issue. The PDF rendering is fine now.
A change in performance is most often due to a change in the software or the environment, and I realised that Intel pushed a video driver update yesterday. And according to the log, the previous driver update occurred a month after I ran this report for the previous financial year.
I would hazard a guess that the last driver introduced the bug, and then it remained undetected until I ran the report again. And as we all know, drivers hook deep into the OS Kernel where that can get up to most mischief.
At this stage, I would suggest closing this ticket. And if I can replicate the issue, and confirm it is not a driver is not at the root cause, I will advise.
Thanks,
David…
@DavidRGreen, thanks for the update — good to hear it renders correctly now.
Closing this one. If it comes back, save a copy of the file aside at that moment and open a new topic with it attached.
