https://bugs.documentfoundation.org/show_bug.cgi?id=167313
--- Comment #2 from b. <[email protected]> --- hello Telesto, nice to see you alive and active ... > It will be hard to address this without sample file Yes, I know, but I don't see the point in investigating, providing better info, with the only reaction being asked two years later to check if the issue vanished in the meantime. The post is more a warning to users and a demand to programmers ... try to produce stable code. > There a plethora of possible causes. Yes, and each "I think it helps" instable patch doubles them. > For > example tables splitting wrongly to image anchor being at the wrong spot. > Aside from the file format being of influence. All these shouldn't come up in stable programs, and we can't blame innocent unwitting users about it. > The only advice is; > * resetting user profile > * using older version or trying a more recent version. > * using alternative Office Suite > * trying the same file on a different system (including virtual machine) And all that is quite poor "poking in the fog" ... > ---------- > Yes, LibreOffice is kind of a minefield. There are risk using LibreOffice > for complicated documents and delicate work. However that's my personal > opinion. And regular updates doesn't mean that incremental improvement. Old > problems get fix, new issues are introduced. If LibreOffice being the proper > tool surely depends on use-case. Apparently it works for majority of the > users.. Yes, it's not useless, however a better coding discipline and some rework might be beneficial. An idea to help people who have saved older states ... provide an option for side by side compare of the old and new version, with highlighting differences and easy transfer would save a lot of time in the experimenting you proposed. Just my two cents ... -- You are receiving this mail because: You are the assignee for the bug.
