<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILESAVE FILEOPEN): Format/Paragraph/Text Flow differs on file open from what saved as .docx"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108511#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILESAVE FILEOPEN): Format/Paragraph/Text Flow differs on file open from what saved as .docx"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108511">bug 108511</a>
from <span class="vcard"><a class="email" href="mailto:gtimur@gmail.com" title="Timur <gtimur@gmail.com>"> <span class="fn">Timur</span></a>
</span></b>
<pre>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
<a href="http://dev-builds.libreoffice.org/daily/master/">http://dev-builds.libreoffice.org/daily/master/</a> or using Separate Install GUI
tool <a href="http://tdf.io/siguiexe">http://tdf.io/siguiexe</a> 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 <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Formatting: Format/Paragraph/Text Flow changes only partially successful in large .docx documents"
href="show_bug.cgi?id=108509">Bug 108509</a> and
<a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILESAVE FILEOPEN): Format/Paragraph/Text Flow differs on file open from what saved as .docx"
href="show_bug.cgi?id=108511">Bug 108511</a>.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>