Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Writing a lot in cooperation, there are many occasions in which I have to
review or edit a paragraph full of changes. 
The best way, for me, to do this is to accept all changes in the paragraph
and review the updated version as a (new) whole. Then move to the next
paragraph and repeat the procedure. 
Now, since LO (I'm using version 3.3.2 on Ubuntu 10.4) allows to regard only
one change at a time this can be a tedious job. The same problem applies, of
course, also to cases where it is evident that all changes in a block should
be rejected, but for me there are much less cases like this. 

So, is it possible to add an option to consider (accept or reject) all
changes within a marked block? 

Thank you for the effort.
The product you produce is great, and getting better in every update!

btw-Is this the right place to ask for such feature additions / changes?

dror

--
View this message in context: 
http://nabble.documentfoundation.org/Accept-reject-changes-in-a-marked-block-Writer-tp3066246p3066246.html
Sent from the Design mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.