Bug 108509 - Formatting: Format/Paragraph/Text Flow changes only partially successful in large .docx documents
Summary: Formatting: Format/Paragraph/Text Flow changes only partially successful in l...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.7.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-13 17:43 UTC by Brad Calcagni
Modified: 2017-06-15 11:16 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Document saved but not yet reopened (1.17 MB, text/.docx)
2017-06-13 18:45 UTC, Brad Calcagni
Details
Same document reopened and re-saved with no edits (1.17 MB, text/.docx)
2017-06-13 18:49 UTC, Brad Calcagni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brad Calcagni 2017-06-13 17:43:25 UTC
Selected 95% of a large document (.9 meg) and tried to change formatting to 
[off] Do not split paragraph
[off] Keep with next paragraph
[on]  Orphan Control
[on]  Widow control

1.a The change was implemented for (loosely) the first half of the document.  "Do not split document" returned to [on] for much of the remainder.
1.b Also, when attempting to format small pieces of the unchanged half to the same above settings, it would work unreliably (usually not work), except when a single paragraph was selected.
2. When "Keep with next paragraph" was set to [off] for a single paragraph, it appeared to be implemented as if it meant *Keep with prior paragraph*.  
When "Keep with next paragraph" was set to [off] for one paragraph, the rule-implemented page break would disappear between the changed paragraph and the prior paragraph, not between the changed paragraph and the next paragraph.

I cannot add the document as an attachment, because it is copywrited material that I am working to proof-read. Apologies.
Comment 1 Brad Calcagni 2017-06-13 18:41:02 UTC
Please remove item (2.) below and replace with" 

When "Do not split paragraph" was set to [off],
it would return to [on] on reopen

Also, sample document will be attached.
Comment 2 Brad Calcagni 2017-06-13 18:45:37 UTC
Created attachment 134002 [details]
Document saved but not yet reopened

Test document created for testing this problem.  Same content in each of the 42 chapters.
Comment 3 Brad Calcagni 2017-06-13 18:49:22 UTC
Created attachment 134003 [details]
Same document reopened and re-saved with no edits
Comment 4 Timur 2017-06-14 16:41:27 UTC
Bugzilla is "issue based", so a single issue must be pointed at, after a search for not being a duplicate. 
Bugzilla is not "document based", like "this document doesn't display nice". 
It's highly unlikely that any bugs of type "multiple problems/bad rendering", will be fixed.
Each issue (section break, paragraph break, text box, picture...) should be reported separately, but only after a search for already reported bugs. 
FILEOPEN problems are different from FILESAVE, and DOC is different filter from DOCX.
Issues may preferably be checked before with master LO version from http://dev-builds.libreoffice.org/daily/master/ or using Separate Install GUI tool http://tdf.io/siguiexe in Windows. It downloads and extracts different LO versions, without installing, so you may test different versions. It only needs MS Visual C++ Runtime installed. 
Only if bugs don't exist, they should be reported separately, even if they happen with the same file.

What I conclude from this bug report is that you work on DOCX but you don't say how it was created, with MSO (and then you must know exactly when LO problem happens) or with LO (slim chance than to know when problem happens) and what it means saved with your attachment.
Also, you mention format change but don't says whether it's direct or style formatting and how you did that. 
So, you steps are not precise and easily reproducible. Same for Bug 108509 and Bug 108511.
Comment 5 Xisco Faulí 2017-06-15 11:16:22 UTC
Closing as RESOLVED INVALID.
Please follow instructions from comment 4 in order to report the bugs...