Created attachment 125846 [details] 2 ODT doc's with printed PDF output, 2 screenshots I chose "Other" for the hardware because this is an Intel CPU running 64-bit Windows 7. The closest in the list is "x86-64 (AMD64)". Given the long history of these problems with printing margins & other related printing-and-margin problems that are still sitting in the bug list with the status of "New" I decided to create a new bug with a screenshot included of my search query of "summary:printing AND summary:margin" which produces a list of 12 bugs as is shown in the screenshot. Of course I would imagine some of these are impertinent to this specific problem of the printing margins but these search criteria find them so they're in the list. I've been into software architecture and customer service for a long long time, and for the life of me I cannot fathom how such basic fundamental functionality such as correctly formatted output is not perfected by the version 1 incarnation of a program -- not to mention a suite of programs -- whose purpose is to create documents that ultimately have the purpose of being printed, be it on paper or to a PDF file. So instead of just giving my own bug report as an addendum to one of these that already exist with some short little explanation, I have attached a ZIP file with my source ODT files so you can see the page margins are what they are, and PDF files to which these ODT files have been printed by a PDF printer driver (as opposed to being exported to a PDF). I have double-checked that these PDF files are exactly the same as what is printed on paper. In the spirit of helpfulness that will hopefully catch on, I have also included a screenshot of my Task Manager window which shows the name of the processes for LibreOffice that are still using the same name of StarOffice from which the LibreOffice codebase is derived (I discovered these process names when LibreOffice had frozen up and I had to terminate the process from Task Manager). In the spirit of excellence and thoroughness, I would also suggest that these process names be given a break from anything of the past and let them be given a fresh and clean image by just being called its own name of LibreOffice. My reasoning behind including these files, especially the ODT files, is that hopefully maybe somewhere in them will be found the reason why despite the margins being set to what they are, the printed output has very different margins. I really do hope all this will be helpful and I really do hope that the LibreOffice programming team will find a fresh and new invigoration for putting these problems very high on the priority list. In this ZIP file are the following files: 1) The 2 screenshots, 1 of the bug list with "printing" and "margins" in the Summary, showing how old these bugs are to hopefully give a renewed priority or urgency to fixing these problems, and the other screenshot being of my Task Manager window. 2) Document "Butt & Gluteus Minimus" document in ODT format and printed to a PDF printer driver. This document is various exercises. 3) Document "Off-Balance Workout" in ODT format and printed to a PDF printer driver. This document also has various exercises.
Created attachment 125871 [details] print to PDF with current ghostscript and the CutePDF engine Can not confirm on Windows 8 Ent 64-bit en-US with Version: 5.1.4.2 (x64) Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a CPU Threads: 8; OS Version: Windows 6.29; UI Render: GL; Locale: en-US (en_US) I'm attaching the Print filter output of the two ODF Writer documents as sent to Ghostscript based CutePDF writer. Margins are correct as set in LibreOffice and as displayed with internal Print Preview. With correctly configured print services printing and export to PDF works correctly in LibreOffice. Looking to be NAB or NOB. Please reinstall your printer software/drivers and your print to PDF software and retest.
Created attachment 125872 [details] print to PDF with current ghostscript and the CutePDF engine here is the other ODF Writer document printed to PDF with Ghostscript v.9.18 and CutePDF Writer v.3.1 -- no issues with margins apparent.
Please retest and report on result with current Ghostscript and PDF print software, or other dedicated PDF print utility (Adobe Acrobat, that has been correctly configured. Thanks.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170131
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170301