+++ This bug was initially created as a clone of Bug #90534 +++ The court requires documents to have two vertical lines on the left margin and 1 vertical line on the right margin. (Word puts these in the header.) Attachment 114701 [details] is a DOCX document that includes said vertical lines as expected by the courts. Here's how it looks in Mac Word 2011: attachment 114709 [details] Here's how it looks in a recent build of 5.3 alpha0: attachment 127334 [details] In LibreOffice, the right vertical line is missing on all pages and the left vertical lines are missing on the 2nd page. On the 1st page, the left vertical lines are visible, but are significantly further to the right, intruding into the main body of text.
It looks as if this vertical line is created by some table/frame combination, that is not related to the other (text)content of the document. So yes, this docx file opens broken, different. But no, it is not related to the format required by the court - one could get the needed result in another way too. Even more broken in 3.3.0.4 wrt severity: Just a 'normal' formatting issue
see https://bugs.documentfoundation.org/attachment.cgi?id=128005 in the other bug :)
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Dear Robinson Tryon (qubit), 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! Warm Regards, QA Team MassPing-UntouchedBug
Opened attachment 114701 [details] No vertical lines in either margin (tested with print preview and export pdf) Version: 7.0.0.0.alpha0+ (x64) Build ID: eeb2d19e77d6dc47c68e8ba0920a02cf64a1247b CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: CL
Dear Robinson Tryon (qubit), 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
Reproduced, but it seems the same like this bug: https://bugs.documentfoundation.org/show_bug.cgi?id=102913" Version: 25.2.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 905e7c1105536c9757fa2c2faf670738aab02595 CPU threads: 8; OS: macOS 15.0; UI render: Skia/Metal; VCL: osx Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
*** This bug has been marked as a duplicate of bug 102913 ***
I’ve run into similar issues when working with pleading templates, especially when the header uses nested tables. Sometimes Word shifts those vertical lines if the page layout settings or section breaks aren’t aligned. You might want to recheck the ruler settings and table cell margins. While troubleshooting, I also found some helpful reference details through https://hamiltoncourtrecords.org that clarified formatting standards. Hopefully adjusting the header structure fixes the misplaced lines for you.
Thanks for sharing this update! I’ve noticed similar formatting issues when working on legal documents, and it can really affect readability. For anyone needing accurate references, I found the Pork Court Directory to be very helpful for checking official details. Hopefully, the suggested corrections will improve consistency across submissions. It’s always great to have reliable resources for these filings.