I would like to be able to show where changes exist in a document by displaying the margin change bars, but only showing the current edit in the text itself (ie no underlying, strikethrough etc in the body text).
This is a common requirement for things like product manuals, where you want the reader to be able to quickly see where changes have occurred since the last version, but they don't need to see exactly what words were altered. It's also a common requirement for revisions to grant applications and scientific papers where you need to show the reviewers that changes have been made in response to their reviews, but again, you don't want a bunch of formatting marks in the text taking space and reducing readability.
In MS word this can be done by setting change attributes to 'hidden' (earlier versions of StarOffice also had this); in LibreOffice the closest is to set change attributes to 'none', which does not work as desired.
This feature was also requested in the OpenOffice bug tracker as far back as 2004: http://openoffice.org/bugzilla/show_bug.cgi?id=24845
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Issue partially resolved in 3.5.0 Beta 2. By 'accepting' deletions and/or changed attributes, insertions and edits can be marked by marginal bars only. However there is still no way to retain track changes for an in progress document by simply hiding deletions and/or changed attributes.
This is something I'd definitly would love to see too.
"Just the bars" is the only convenient way I know to let readers quickly browse a regularly updated document, chasing changes since the latest document update.
The specific use case for "just the bars" typically adresses readers of a "released" document, when the usual full fledge "track changes" is more aimed at writers / reviewers for a document still in the works.
Thanks for new idea
Please, attach screenshot to show how it should be
> This is a common requirement for things like product manuals
But manuals usually in PDF format. May be it should be specific option for pdf exporting?
Created attachment 57855 [details]
Example of a page with modification marks, as a PDF file
(In reply to comment #4)
> Created attachment 57855 [details]
> Example of a page with modification marks, as a PDF file
This attachment / example is a one-page PDF file, excerpt from an IBM technical manual.
Created attachment 57856 [details]
Another example of a page with modifications marks, as a PDF file
Both attachments excerpt from IBM technical manuals - IBM has been using this modification marking technique for as long as I can remember (and this is much longer than I'm willing to confess :P ).
Thanks for attachment.
So, as I undersand, we need 2 additional options: one for change mode in Writer and second for change mode in PDF exporter
(In reply to comment #8)
> Thanks for attachment.
> So, as I undersand, we need 2 additional options: one for change mode in Writer
> and second for change mode in PDF exporter
That sure would look good to me!
This feature is complete in LibreOffice 126.96.36.199.
(In reply to Darrell from comment #10)
> This feature is complete in LibreOffice 188.8.131.52.
Please disregard the previous comment; a bug in how change bars are displayed in 184.108.40.206 made it appear that this feature had been implemented.
Let's set back to NEW.
Is anyone thinking about how to do this?
I'll add my voice in saying that the changes mark-up, though useful for editors, is almost never acceptable for published documentation. Change-bars-only is really needed for published documentation.
This issue has been hanging around for at least 16 years...
See OO bug https://bz.apache.org/ooo/show_bug.cgi?id=24845
Can I add my vote for this important feature? It's pretty much essential for many types of professional document.