[Libreoffice-bugs] [Bug 92444] New: Formatting of docx

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Bug ID: 92444
Summary: Formatting of docx
Product: LibreOffice
Version: 5.0.0.2 rc
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-***@lists.freedesktop.org
Reporter: ***@whsg.info

Created attachment 116944
--> https://bugs.documentfoundation.org/attachment.cgi?id=116944&action=edit
docx that looks really bad

It was suggested that doc and docx documents that LO munges should be reported
as bugs.

If this is wrong please let me know who would be interested in these documents
as we have quite a few. If this is the correct way to bring compatibility
errors to light then I have a whole bunch of them you can look at.

The attached document is one a student brought in this morning.
It looks REALLY bad in 4.4.3 and just very bad in 5.0.0.2. ( and
looks fine in Word 2013 surprisingly )

4.4.3 from openSUSE repos
5.0.0.0.2 from Libreoffice
openSUSE 13.3 64bit
Nvidia blob
KDE Plasma5

Mal

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Marc Kaulisch <***@kaulisch.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |***@kaulisch.de
Ever confirmed|0 |1

--- Comment #1 from Marc Kaulisch <***@kaulisch.de> ---
Hello mal,
Thank you for reporting the bug. I can confirm that the bug is present in LO
5.0.0.2 64bit on Win8.1.

It is also a loss of information as the second page is not displayed.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #2 from mal <***@whsg.info> ---
Since we are a school and our students seem to have a particular knack at
producing documents that look like this one, do you want me to report them as
bugs? I could do them individually or batch up a few at a time.

Ta

Mal

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #3 from steve -_- <***@openmailbox.org> ---
@mal: rule of thumb: one problem per bug. Otherwise things escalate quickly and
it get's really hard to keep track of anything at all.

If you have a document which has 6 problems, open 6 reports. Interlinking the
reports via the "see also:" field might be a good idea then.

But generally speaking: if you run into trouble it's always good to report the
problem. That's the first step to improve the situation. QA will then deal with
your reports i.e. mark them duplicates or valid + new etc.

As for filing good bug reports, this Wiki is a good starting point:
https://wiki.documentfoundation.org/QA/BugReport

"looking bad" is not a good description. The more specific you can be the
better. And giving good reproduce steps and clearly indicating what QA / devs
should be looking for in the title of your bug + the description will help a
lot to move things forward faster.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

raal <***@post.cz> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@post.cz
Version|5.0.0.2 rc |4.4.3.2 release

--- Comment #4 from raal <***@post.cz> ---
(In reply to mal from comment #0)

Post by b***@bugs.documentfoundation.org
The attached document is one a student brought in this morning.
It looks REALLY bad in 4.4.3 and just very bad in 5.0.0.2. ( and
looks fine in Word 2013 surprisingly )

Version is earliest affected.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Timur <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |filter:docx
CC| |***@gmail.com
Hardware|x86-64 (AMD64) |All
Version|4.4.3.2 release |5.0.0.0.alpha0+ Master
Summary|Formatting of docx |FILEOPEN: Frames
| |overlapping in DOCX
OS|Linux (All) |All

--- Comment #5 from Timur <***@gmail.com> ---
Problem here is the opening of DOCX with frames.
Opening was never fine, but it's better now from LO 5.0. At least you see it's
not OK, unlike when you see 3 frames and don't know about other 3.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Buovjaga <***@suomi24.fi> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@suomi24.fi

--- Comment #6 from Buovjaga <***@suomi24.fi> ---
Created attachment 125350
--> https://bugs.documentfoundation.org/attachment.cgi?id=125350&action=edit
Another example of frames overlapping

Looks like I don't have to create a new report :)
I thought I'd nevertheless upload this example DOCX coming from Word 2013.

Confirmed with Version: 5.3.0.0.alpha0+
Build ID: 9d2f7be4e65595241db3cf5135b69bd9e4ce6a30
CPU Threads: 4; OS Version: Windows 6.29; UI Render: default;
TinderBox: Win-***@42, Branch:master, Time: 2016-05-27_22:55:26
Locale: fi-FI (fi_FI)

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Telesto <***@surfxs.nl> changed:

What |Removed |Added
----------------------------------------------------------------------------
Blocks| |88173


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=88173
[Bug 88173] [Meta] Tracking bug for limitations of DOCX (OOXML) format

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Telesto <***@surfxs.nl> changed:

What |Removed |Added
----------------------------------------------------------------------------
Blocks|88173 |104461


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=88173
[Bug 88173] [Meta] Tracking bug for limitations of DOCX (OOXML) format
https://bugs.documentfoundation.org/show_bug.cgi?id=104461
[Bug 104461] [META] DOCX Frame related issues

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #7 from QA Administrators <qa-***@libreoffice.org> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #8 from Timur <***@gmail.com> ---
6.1+ opens like 5.0.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

Timur <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|FILEOPEN: Frames |FILEOPEN: Frames
|overlapping in DOCX |overlapping in DOCX (see
| |Comment 10)

--- Comment #10 from Timur <***@gmail.com> ---
Repro in LO 6.3+ with attachment 116944. Wee see 3 out of 6 frames. But that
DOCX was created in Macintosh Word 2011. Opens OK in LO if resaved in MSO 2016.
Yet we should open it properly.

Attachment 125350 is created in Microsoft Office Word 2013. With LO 6.3+ still
shows the same overlap. That one is more appropriate for this bug.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #12 from Timur <***@gmail.com> ---
Created attachment 147414
--> https://bugs.documentfoundation.org/attachment.cgi?id=147414&action=edit
docx that looks really bad compared in LO 6.3+ MSO 2016

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #11 from Timur <***@gmail.com> ---
Created attachment 147413
--> https://bugs.documentfoundation.org/attachment.cgi?id=147413&action=edit
docx that looks really bad looks OK when resaved in MSO 2016

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=92444

--- Comment #9 from QA Administrators <qa-***@libreoffice.org> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug