<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Word document renders incorrectly compared to Office on Windows"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=133680#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Word document renders incorrectly compared to Office on Windows"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=133680">bug 133680</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=133680#c5">comment #5</a>)
<span class="quote">> Wait, the OOXML .docx is bogus--it does not render correctly/consistently in
> Word (2016) or Word 365--the inserted pictures jump all over the pages</span >
Oh do they? I had only opened the document in Word 2016 and scrolled down and
up, and it looked like it didn't jump (although their positioning was
inconsistent - meaning the images on one page were in different coordinates wrt
counterparts on another page; but then the images likely were put by hand...?).
Is there a howto to see the jmping?
<span class="quote">> --why should we be burdened with attempting to parse out an ODF filter import
> from a clearly malformed document?</span >
Of course, if I overlooked that, it's OK to not try to "fix" what doesn't work
in Word - please close it again, but please don't forget to mention how to
repro the jumping in Word, to justify the decision. Sorry for the noise.</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>