Created attachment 45050 [details]
Original OO Letterhead and modified letterhead to work in Libre
This is a biggie. This is Libre OOO330m19 (Build:202) on Arch LInux i686. The table font/paragraph handling in Libre has changed from OO causing the letterhead formatting that uses tables to display what was a single line of information as a wrapped line in the letterhead. This causes the prior 5 years of letters saved in odt/ott format to print incorrectly. This is thousands of documents.
Included as an attachment to this report are 2 ott files:
ltr-rankin-oo.ott (the original OO letterhead)
ltr-rankin-libre.ott (the same modified to print correctly in Libre)
If you open ltr-rankin-libre.ott you will notice the right column containes two lines of text that do not wrap. This is how the OO file looked in OO. After switching to Libre, if you open ltr-rankin-oo.ott, you will notice that the bottom line of the right-column wraps pushing the bottom table boundary down and impacting the remainder of the document spacing.
I don't know what is causing Libre to space the right column different than it did in OO, but it prevents the ability to recreate thousands of documents in their original form. (not good in my profession)
The documents attached may be used freely for the purpose of this bug report, but redistribution outside of that purpose is prohibited (for obvious reasons). They should be marked for internal use, if possible.
The same issue effects entire document pagination. Pleadings previously created in OO now experiece page run-ons causing many nearly blank pages (one sentence wraps to the top of the next page) to be added to doocuments. Whatever the default change to kerning/leading or spacing is, it is the same as in the examples already provided.
Created attachment 45357 [details]
Screenshot OO and Libre 3.3.2 on Windows - Same Behavior
I went ahead and performed a test on Windows by installing the current windows versions for OpenOffice and LibreOffice and testing whether the spacing bug is present on windows. It is. You can see in the screenshot. I have both OO and Libre open and arranged in the window so you can see both. I opened the same original OO template in both. It displays correctly in OO, but the right side of the letterhead wraps in Libre destroying the document spacing.
As mentioned in the latest post - this effects entire document spacing -- not just tables. All of the pleading originally created in OO now have page run-ons in libre resulting in pagination problems where the original document cannot be re-created.
Let me know if I can provide anything else. Thanks.
This not only affects user created documents -- This also affect all predifined templates that ship with Libre. That means All Labels, etc. If you create a new label sheet with:
File -> New -> Labels -> (eg. Avery 5160)
the labels run off the end of the page. I'll attach the Avery 5160 example as a separate post.
Created attachment 46128 [details]
Avery 5160 label sheet created in Libre - labels run off end of page
This is the label sheet created with:
File -> New -> Labels -> Avery 5160
It worked fine in OpenOffice. Due to this spacing bug, the label spacing is all screwed up in Libre causing labels to mis-print and causing the last row of labels on the page to run off the bottom of the label sheet.
This may not be limited to Libre - I just installed OO3.3 on windows and was hit with the same spacing problem in OO3.3. I have also reported the issue to OO:
I know for a fact that table spacing in OO3.2 was fine, so this looks like a new version issue. I have included a side-by-side screenshot in the OO bug showing the OO3.3 Avery 5160 label spacing next to the Word Avery 5160 spacing. In both OO and Libre, the label run-on extends well into the nonprintable region of the page leaving 'zero' margin at the bottom.
As this effects ALL pre-defined label templates, we may want to bump the priority up on this bug. I have changed the importance to high.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
The bug remain in all releases up through. 3.5.1-1. This bug should remain as new.
Forgot to change status :)
Thanks for bugreport
Reproduced in 3.3.4, but not reproduced in 3.5.5 and 3.6.0
May be fixed. Please, verify
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 INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
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!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID 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 FDO