A complain about file loading in LibreOffice

Recently I found AOO blog posted a thanksgiving mail, which originally sent to AOO developer mailing list by Mr. Ziegler. He praised its usability and stabality, but seen from the whole mail, I found there is alao a large complain about LibreOffice:

By that, I enjoyed the progress in LibreOffice, but didn’t really need it. Although I switched to LibreOffice on some machines, I am always glad that there is OpenOffice, too. In my eyes, it is the more stable and efficient branch of the project. This year it was my fallback tool and salvation in a book project that I started with LO Writer; I first invested hours to get my pictures back to the place they belonged to when they got more and more (as others did decades before with MS Word) and then had to give up as it didn’t open the file anymore without crashing. Apache OpenOffice (standard and portable) solved the problem. It got a nice book, by the way, for our church jubilee.

Does it still afftct LibreOffice at the moment? If so I suggest we can launch an investigating to hunt the bug.

Hello @KrasnayaPloshchad,
A story about a bug is not a bug.
It seems to me that mr. Ziegler’s file got corrupted, perhaps even due to the invested hours of trying to correct the effects of his previous commands, whereas he could have asked for help here on Ask.LibreOffice.org, and perhaps even uploaded his corrupted file to see if an expert could salvage it.

It is not completely clear from the text which the exact problem was and it is not mentioned on which LibO version it happened either, but I had some severe trouble with object positioning on LibO 5.0.x.

Most of those problems got fixed on 5.1 (there is still this moving anchor point thing, though, but it is not a new problem). That said, image positioning on Writer (any incarnation) was, still is and probably will be, frustrating at times and always requires a lot of manual work, specially when your pictures are big and use a good portion of the page. Nothing beats LaTeX’s floats :wink:

So is there anyway to fix that bug?