Description: Contracts in Word frequently contain style separators such as for definition clauses. This has been reproduced on page 2 attached Word document. Other problems exist such as conversion of the TOC retaining columns. However the bug in which the odt format file has two lines for each Word single line including style separator renders Libreoffice Writer unusable as this bug results in excessive lines in a document in which it is essential to visually contain information to one page. Also due to discussions referring to page numbers it is not advisable to change the layout area and page numbering. Steps to Reproduce: 1.Create Word document with style separator used over on page as in law office/business common practice. 2.Open said Word document with LO Writer. 3.Save in odt format to reveal bugs. Actual Results: Major bug in sample document is inability to reproduce Word style separator effect so as to retain single lines containing the information. Double line appearance in Writer means document area is effectively doubles compared to the Word appearance. Expected Results: Bug persists with no apparent remedy. Reproducible: Always User Profile Reset: Yes Additional Info: Retained the style separator information so that the sigle Word lines can be reproduced in Writer.
Created attachment 147624 [details] Word document with style separator
(In reply to brucehatfield from comment #0) > Description: > Contracts in Word frequently contain style separators such as for definition > clauses. This has been reproduced on page 2 attached Word document. Other > problems exist such as conversion of the TOC retaining columns. However the > bug in which the odt format file has two lines for each Word single line > including style separator renders Libreoffice Writer unusable as this bug > results in excessive lines in a document in which it is essential to > visually contain information to one page. Also due to discussions referring > to page numbers it is not advisable to change the layout area and page > numbering. You are discussing several issues. Please open separate bug reports for each issue. So please narrow down this bug report to one issue (for example style breaks) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' after giving the requested informations.
Dear brucehatfield, 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
Dear brucehatfield, 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-FollowUp