https://bugs.freedesktop.org/show_bug.cgi?id=39178
stfhell <stfh...@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Hardware|x86 (IA32) |All
OS|Linux (All) |All
Status|RESOLVED |REOPENED
Resolution|INVALID |---
Severity|normal |enhancement
CC| |stfh...@googlemail.com
Summary|FILESAVE =long time while |Make "record/track changes"
|recording changes |in Writer more efficient
--- Comment #7 from stfhell <stfh...@googlemail.com> ---
I am reopening this bug because the problem is there, actually. I'm aware that
there is no easy solution for it and that one has to be prepared to go on
living with the issue for still a while, but it _is_ a problem for some usage
scenarios.
Problem:
If you edit a large document in Writer (200+ pages) and use the "record/track
changes" function (redlining) a lot to have revisions recorded, Writer will
become more and more inefficient to work with due to the growing number of
revisions recorded.
(1) Disabling "show changes" is explicitly discouraged by LO (the dialogue that
says: Hiding changes makes everything slow, would you not rather prefer to show
them again?) because hiding changes makes editing a pain in larger documents.
(2) Saving a file takes _much_ longer (rough guess: 3-10 times) with many
changes recorded - and, I'm sorry, you cannot discuss that away with a Comment
#2 like, "Hey, 18 secs to save is not that long, and you can go and have a cup
of coffee while LO is saving". Saving is not done in the background, and you
have to wait for it to finish. And this does not only concern regular file
saves via Ctrl-S, but also the auto-saves, of course. (And you need auto-save!)
(3) For some reason, normal text editing isn't slowed down that much, but
inserting a new paragraph is excessively so. Depending on the number of
recorded changes, it can take 5-10 seconds to have it inserted. Interestingly,
it's much faster to do the same thing by using the clipboard: Copy an empty
paragraph and insert it where you want a new paragraph instead of hitting
Return.
Of course, all this concerns only people who edit large texts (200+ pages) and
actually use "record changes" heavily (say, some hundreds of changes in the
doc). But if this scenario covers your usage of LO, you _do_ have a problem.
You have to split the document in 50-page units or disable "record changes" as
much as possible.
I think, with modern hardware in mind, editing a 400-page document with 10
recorded changes per page should be possible without a word processor becoming
virtually unusable. But it's probably more of an enhancement than a bug...
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
