Bug 67450

Hi John,

Yes, please provide the sample document(s), but pls also give a clear description of what needs improvement. When possible, a screen shot of the situation in Word is great.
Thoses detailed reports have helped developers a lot over the past time to get where we are, and every extra step is good.
Regards,
Cor

Created attachment 83193 [details]
docx with bugs

The file was too large and upload failed. I erased some content. I can not make the description more accurate because there isn't one bug on the docx but multiple. I provide the file to help you determine bugs.

Open it with MS Office 2010 and you can see the differences.

Created attachment 83203 [details]
Document in LibreOffice Writer 4.1.0.4

Created attachment 83204 [details]
MS Word 2013

I am getting similar results on MS Word 2013 and LibreOffice 4.1.0.4 - see attached images. MS Word 2010 looks identical to 2013, so I didn't bother to attach that.

Something is seriously wrong with this document, and it's not obvious whether this is the fault of LibreOffice or something totally different.

Maybe a screenshot from your machine would help here?

maybe the file is corrupt (cause i had to delete content in order to attach it). i will give you external link ( http://ubuntuone.com/3tq4ybEMtKvclYzWvO8wY4 ) so you can get it complete-untouched. i will attach here some screenshots too.

Created attachment 83398 [details]
LibreOffice 4.1 screenshot 1

Created attachment 83399 [details]
LO 4.1 screenshot 2

Created attachment 83400 [details]
LO 4.1 screenshot 3

Created attachment 83401 [details]
MS Word 2010 screenshot 1

Created attachment 83402 [details]
MS Word 2010 screenshot 2

Created attachment 83403 [details]
MS Word 2010 screenshot 3

Hi John - 

in the future when bug reporting please 

a) provide reproducible steps and any details about your system and LibreOffice version

b) a clear summary of the bug "very bad" doesn't give us much to work with ;)


Trying to reproduce now - thanks for the report

@John - can you attach the untouched one here also? Seems like Ubuntu one is down, we don't like relying on outside infra for attachments because of these kinds of issues.

a)I wish i could but bugzilla doesnt allow files with such size to be uploaded. I will have to delete content again and i dont know how much that affect the document.

b)Sorry for the description.

No worries - thanks for the update

With it behaving weird on MSO 2013 also I have my doubts about the file. Going to request some input.

I can confirm that

1) The document linked from ubuntuone named "complicate docx.docx" is 4.045.510 bytes in size and is a good sample

1) The document attached as "docx with bugs" (file BUG.docx) is the result of saving the original file with some old version of LO (possibly 3.5.7) and is useless for testing

3) Document "complicate docx.docx" loads correctly under MS Office 2010 and even under MS Office 2003 (with file conversion)

4) Document "complicate docx.docx" formatting is broken under LibreOffice 4.1.4.1

5) "LO 4.1 screenshot 3" from the 4th page of the document is a good reference. The schemes on top should be in page 3 (shown in "MS Word 2010 screenshot 3")

6) In addition to all the changes in the position of elements, the screenshots from the Hellenic (aka Greek) LO also show that there is a problem in displaying some math elements E.g. the squares in the formulas in "LO 4.1 screenshot 3" should be an Epsilon or Sum symbol; the vertical curved brackets in "LO 4.1 screenshot 2" are missing (compare with "MS Word 2010 screenshot 2")

7) The missing math symbol problem does not occur in my PC using LO 4.1.4.1 en_US under Windows XP Pro x86 SP3

8) Loading "complicate docx.docx" in LO 3.5.7, 3.6.7 and 4.0.6.2 shows different problems. There were progresses and regressions...

It sounds like this is a lot of bugs in one document. If at all possible it would be nice to isolate the problems and report 1 bug report for 1 problem. 

Pedro - am I correct in this assumption? If so, might be best to close as INVALID and narrow down the issue(s) so that it's a functional bug report for our developers. If you think that this is impossible then that's fine, but it's much harder to find a developer to tackle a meta bug than individual bugs.


Thanks all

(In reply to comment #18)
> It sounds like this is a lot of bugs in one document. If at all possible it
> would be nice to isolate the problems and report 1 bug report for 1 problem. 

Whiteboard: MultipleBugs

Joel -- I managed to download the entire document from UbuntuOne, so one of us can go through and try to generate some smaller test documents that exercise just a single bug each. I'll try to get to that soon, if you don't beat me to it :-)

For now, I'll leave this open as a reminder to split-up the test cases. Once each of those individual bugs is fixed, the entire document should render properly, and then we can close this bug as well.