Bug 34355 - Option to show track changes in margin is missing
Summary: Option to show track changes in margin is missing
Status: CLOSED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: high enhancement
Assignee: László Németh
URL:
Whiteboard: target:7.1.0
Keywords:
: 47298 79420 118660 (view as bug list)
Depends on:
Blocks: Track-Changes tracked-changes-in-margin
  Show dependency treegraph
 
Reported: 2011-02-16 11:40 UTC by Guilherme
Modified: 2022-02-04 06:48 UTC (History)
36 users (show)

See Also:
Crash report or crash signature:


Attachments
Printscreen of the two softwares (100.19 KB, image/jpeg)
2011-02-16 11:40 UTC, Guilherme
Details
really good one keep it up (4.06 KB, text/plain)
2019-10-24 10:31 UTC, atim jha
Details
Hot and sexy call girls in Ajmer from top Escorts Agency in Ajmer. (deleted)
2020-03-09 06:50 UTC, Anjali Singh
Details
spam (91.67 KB, text/spam)
2020-03-12 09:35 UTC, Riya Mittal
Details
<spam> (72.22 KB, image/jpeg)
2020-04-30 18:20 UTC, lyricsmin
Details
<spam> (21.08 KB, image/jpeg)
2020-05-30 05:14 UTC, thelyricsnepal
Details
mere sohneya lyrics-kabir singh (192.87 KB, image/jpeg)
2020-06-08 15:29 UTC, Muna deep
Details
screenshot (145.14 KB, image/png)
2020-10-21 18:55 UTC, BogdanB
Details
Screenshot running master (99.72 KB, image/png)
2020-10-22 08:29 UTC, Heiko Tietze
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guilherme 2011-02-16 11:40:39 UTC
Created attachment 43448 [details]
Printscreen of the two softwares

The revision tool in Word XP places all comments, deletions, and formatting
changes in text balloons on the margin of the document (with the Print View enabled).  Each text balloon is colored differently for each author and type of change.  Since deletions are removed from the body of the document, the impact of changes on pagination and document length can easily be determined, and text reading is easier.
Comment 1 gleppert 2011-05-02 02:58:07 UTC
Improved track changes in LO is crucial for most users in professional environments. Particularly in academic teams, where reviewing articles is a standard procedure, people reject using OOo/LO due to this lacking feature. For more information on this, please see:

Entry in the Documentfoundation WIKI:
http://wiki.documentfoundation.org/Development/Enterprises_nice-to-have#Need_for_improved_collaboration_tools:_better_.22track_changes.22.2C_better_.22compare_documents.22.2C_better_.22printing_of_comments.22_needed

Quite comprehensive overview of this problem and comparisons to other office suites:
http://wiki.services.openoffice.org/wiki/Track_changes

Related bug in OpenOffice issue tracker:
http://openoffice.org/bugzilla/show_bug.cgi?id=9661
Comment 2 Rainer Bielefeld Retired 2011-06-10 02:58:33 UTC Comment hidden (off-topic)
Comment 3 Christoph 2011-06-13 12:57:48 UTC
There have been some ideation iterations within the OOo Notes2 implementation, see "Change Tracking Integration" at:
http://wiki.services.openoffice.org/wiki/Notes2_OtherIdeas

The mockup I've created that time:
http://wiki.services.openoffice.org/wiki/File:Notes2_GeneralMockups_RoughIdeas_ReviewTools_ForIdeasList.png
Comment 4 Björn Michaelsen 2011-12-23 11:53:03 UTC Comment hidden (obsolete)
Comment 5 Leo H 2012-01-11 06:18:44 UTC
This issue remains unresolved in LibreOffice 3.5.0 (tested and confirmed with beta2 prerelease).
Comment 6 Leo H 2012-01-11 06:51:09 UTC
The key issue is that the "Compare Document" functionality of LibreOffice Writer is woefully inadequate. For example, type (without quotes):

"LibreOffice Writer. Compare Document."

Save as version1.odt.  Then add one space at the start and one paragraph marker after the first period, as follows (again without the quotes):

" LibreOffice Writer.
 Compare Document."

Save as version2.odt. Now use "Compare Document" to identify the changes in version2.odt relative to version1.odt:  We simply get the full text twice, and EVERYTHING is marked as changed, either as inserted or as deleted.

Now try editing and version comparison not of a page with just four words, but of a 40-page report or of a 250-page book:  This is simply a catastrophe with whole coloured swathes of repeated identical or near-identical text, but all identified and marked by LibreOffice as completely different.

CONCLUSION: "Compare Document" in LibreOffice Writer at the moment is completely clueless and completely useless.

Yet fine-grained comparison of versions of a document is an absolutely essential function, eg in editing, in collaborative projects, and similar.

The way is which the results of good fine-grained version comparison are presented (eg, in the main text, in a margin, in balloons, or otherwise) is less relevant than the very ability itself to compare and identify precisely and exclusively all true changes.

And this also applies to footnotes, endnotes, fields, headers, footers, frames, etc, which are currently completely ignored by LibreOffice Writer "Document Compare".
Comment 7 Renato Mendes 2012-01-11 10:42:06 UTC
tested and confirmed with beta2 prerelease
Comment 8 Cyril 2012-08-21 23:26:58 UTC
Yes changes are a real need, and LO 3.5.5 is not good enough.

For me, this simple step would already be a good improvement:
- to be able to display Writer document with changes only with Margin Marks

Suggestion:
- add an Attribute "Hidden" in Deletions Attributes (th
Comment 9 Gerry 2013-01-12 11:42:54 UTC
For your information: "Use margins to track changes" is the *Number 2* of the TopTen for Enhancement Requests on the Documentfoudation Wiki. 

Please see the votes on: http://wiki.documentfoundation.org/Vote_for_Enhancement#Top_Ten_of_Requests
Comment 10 bugquestcontri 2013-05-16 00:56:22 UTC
Triggered by question http://ask.libreoffice.org/en/question/8809/track-changes/?answer=8812#post-id-8812 in AskLibO I looked into bugzilla and found there is an enhancement request for printing of comments at the page margin. (https://bugs.freedesktop.org/show_bug.cgi?id=36815) . Maybe these to request can be dealt together.
Comment 11 samwichse 2014-02-02 01:23:32 UTC
The poor handling of editing comments is basically the only feature keeping me from deploying LO at my work (researchers), please pretty please add this.
Comment 12 Johannes Rohr 2014-02-14 10:41:00 UTC
The original OpenOffice.org bug report was submitted twelve (!) years ago: https://issues.apache.org/ooo/show_bug.cgi?id=9661

Are there patent issues preventing this from being addressed or is no developer considering this an issue needed to be dealt with? 

In my professional context, this is /the/ major showstopper preventing many of my colleagues from abandoning MS Office. Everyone is used to changes being visualised in bubbles on the margins. (And everyone is use to being able to print draft documents out this way for on-paper review, but that's another issue).

I would really like to warmly recommend to make this a priority!!!
Comment 13 chljl 2014-04-19 00:54:52 UTC
Extremely important for me. Probably the most important reason to shift to LibreOffice since I need to collaborate with other people and use track change all the time. Showing changes in balloons is the prefer way for edition.
Comment 14 chljl 2014-04-19 00:55:55 UTC Comment hidden (obsolete)
Comment 15 Jorendc 2014-07-02 21:43:16 UTC
*** Bug 47298 has been marked as a duplicate of this bug. ***
Comment 16 Gerry 2015-02-10 22:16:42 UTC
Update on vote for enhancements: "Use margins to track changes" is with 11 votes *Number 1* of the TopTen for Enhancement Requests on the Documentfoudation Wiki. 

Please see the votes on: http://wiki.documentfoundation.org/Vote_for_Enhancement#Top_Ten_of_Requests

If this enhancement is important for you, consider adding your vote to the wiki page.

----
P.S. Of course, if there are many votes, there is no guarantee that developers start working on this enhancement, but still it shows the relevance of this enhancement.
Comment 17 Jean-Baptiste Faure 2015-02-21 20:08:07 UTC
Not so good idea for me. In the attached printscreen it is very difficult to see the deleted text. You can't read the text as it was before deletion, that is very inconvenient when you have to decide to accept or refuse the change.
I would prefer an easy way to switch on/off the viewing of changes.

Best regards. JBF
Comment 18 Daniel Jenk 2015-03-14 23:34:19 UTC
Just to follow on from the other comments, the presentation of deleted text with tracked changes as underline or strikethrough, etc. in the main body of the text makes it unusable for me. Others may be more tolerant, but with many changes it is not possible for me to both monitor my changes and read the intended meaning of the modified sentence if the deleted text remains. The ability to move the tracking of deletions to the margin or possibly just a place marker on the outside of the main lines of text would make this program an easy choice over MS Office. Of course, one could track changes and not show them in the present version of Writer, but this does not allow the editor to do his or her work without flipping back and forth between different versions. Balloons work well, but maybe just a mark of where the text was deleted and the ability to maybe mouseover the area and get a bubble of the deletion would be a good halfway point. Happy to help if there is some way to contribute.
Comment 19 Jean-Baptiste Faure 2015-03-15 08:07:29 UTC
What about if we had a button in the track changes dialog allowing to apply/removing a set of changes *temporarily*. Such a function could allow to see a change in situation and see what the text is without the change.

Best regards. JBF
Comment 20 whynot 2015-06-08 09:56:28 UTC
I just checked the list of new features for LO 5.0 beta, and unfortunately, no mention of an improved way to show track changes. 
I am doing a lot of collaborative writing in an academic environment, and I agree with many others here that the current way of displaying the changes is not really usable. Keeping all the deleted text crossed-out will also give a completely wrong impression of the actual length of the text after the edits. In many cases, one targets a particular word or page limit, where this is totally misleading. 
What could be done in order to bring this to the attention of more developers? Is this really to difficult to implement? Apparently, there is already a mechanism to place comments as balloons on the margins. So shouldn't it also be possible to display deleted text like this, like MS Word does? Only the display colors, etc., of the actual balloon would have to be a bit different to distinguish it from a comment.
Comment 21 whynot 2017-02-02 14:36:25 UTC
Does anyone have an idea whether this is being worked on? It's not in the just-released v5.3, and the developers are only starting to populate the 5.4 release notes. 
I heard rumors that this will be included (or perhaps has already been implemented?) for the online version of Libreoffice (where, of course, it would make a lot of sense for optimized collaborative editing).
Comment 22 strata_ranger 2017-02-12 23:34:20 UTC
I agree, LO's implementation of (particularly in displaying) tracked changes is still decidedly inferior to MS Word 97/2003, which was my first exposure to such options.

In my case, I downloaded LO for some of the perks it offers over OO (including having a review toolbar shipped by default; I had to build one manually in OO).

One big thing that LO should have is the concept of 'original' vs. 'final' views of a document with tracked edits.  Currently the only two views we have are "show markup" (original + markup) and "hide markup (final + no markup).  This is insufficient; it should be expanded to match Word's level of functionality where original v. final and with/without markup are separate options.  This gives us a combination of four view modes:

- "Original"
- "Original with markup" forces deletions to be displayed inline; insertions can be displayed inline or as margin balloons.
- "Final with markup" forces insertions to be displayed inline; deletions can be displayed inline or as margin balloons.
- "Final"

One big issue I have run into is that LO's handling of tracked linebreak edits is that when markup is shown, the document is displayed reflecting *ALL* linebreaks in the file, even ones that were inserted or deleted.  This impacts how the display is paginated, not cool...
Comment 23 Heiko Tietze 2017-02-20 10:39:12 UTC
*** Bug 79420 has been marked as a duplicate of this bug. ***
Comment 24 Heiko Tietze 2017-02-20 10:40:55 UTC
Being duped by bug 79420 it's better to have all discussion at this place.
Comment 25 whynot 2017-03-17 15:13:32 UTC
@Heiko:
In the Bug 79420 report, you mentioned that this is being implemented on (Comment #5). Do you have any additional insight in this regard? Any idea for what release of LO this is targeted?
Comment 26 Heiko Tietze 2017-03-17 16:04:23 UTC
(In reply to whynot from comment #25)
> @Heiko:
> In the Bug 79420 report, you mentioned that this is being implemented on
> (Comment #5).

As announced in the release notes [1], the sidebar deck "Manage Changes" was implemented with 5.3 as an experimental feature (don't remember why). If you are a brave user enable experimental features per Tools > Options > LibreOffice: Advanced.

[1] https://wiki.documentfoundation.org/ReleaseNotes/5.3#Sidebar_2
Comment 27 whynot 2017-03-17 16:33:16 UTC
Oh, my goodness! That is so exciting! Thank you so much for this information. I usually pay quite close attention to the LO release notes, but I must have missed this one because it was under "Experimental" (without a lot of explanations) and not under "Writer").
Definitely, the possibility to sort comments by date and other features will be extremely powerful! I am not even aware that this functionality exists in MS Word. 
(And yes, I am usually a "brave user" of LO experimental features...)
That said, while this sidebar is wonderful to display and manage the changes, it does not address the main thread of this bug: to display the changes on the margins. Also, as far as I can see, the sidebar only shows "metadata" of the changes (date, author, kind of change). Correct?
Comment 28 Heiko Tietze 2017-03-17 16:50:07 UTC
(In reply to whynot from comment #27)
> ...it does not address the main thread of this bug: to display the
> changes on the margins. Also, as far as I can see, the sidebar only shows
> "metadata" of the changes (date, author, kind of change). Correct?

The sidebar has limited capabilities today, yes. We discussed the requirements at https://user-prompt.com/de/tracking-changes-with-libreoffice/ mainly with focus on bug 87695. But there is also an alternative solution to the margin issue included.
Comment 29 Benoît Robin 2017-06-04 06:01:07 UTC
I personally gave up using LO for novels, short stories and RPG editing just because of that blatant lack of an essential feature.

So each time Ubuntu gives me a LO update (so far 1:5.2.5~rc1-0ubuntu1~xenial0), I check that, but there's no usable change-tracking, and I go back to Windows and Word, infuriated.

IMHO, this is a no-brainer : anyone professionally using a text editor needs to track changes, and displaying changes in the text itself makes the text unreadable, and therefore the whole change-tracking feature unusable.
Comment 30 Johannes Rohr 2017-06-15 14:06:32 UTC
(In reply to Heiko Tietze from comment #26)

> 
> As announced in the release notes [1], the sidebar deck "Manage Changes" was
> implemented with 5.3 as an experimental feature (don't remember why). If you
> are a brave user enable experimental features per Tools > Options >
> LibreOffice: Advanced.

Unfortunately, this just moves the changes dialogue into a sidebar, but it does not add new functionality, or even implement what the reporter of this bug has asked for (and what MS Word has been having now for a decade)
Comment 31 Heiko Tietze 2017-06-15 15:23:00 UTC
(In reply to Johannes Rohr from comment #30)
> Unfortunately, this just moves the changes dialogue into a sidebar...

That's true. It's only a small step, nothing else.
Comment 32 Edmund Laugasson 2017-08-17 22:00:12 UTC
Would propose to keep current version and possibly add a configuration option to switch onto MS Office version of track changes and support also importing while opening MSO document in LO with track changes made in MSO.

At least by my humble opinion I am satisfied with current track changes logic and design in LO and would like to use it also in future like now.

Certainly this is fundamental difference how the track changes is solved in MSO and LO - therefore it would be nice to have similar or same behaviour in LO like in MSO.

There could be different options how to enable such behaviour like in MSO. One option would be to add an effect that changes will not shown in text. Then there could be an option while accepting/denying changes, allow to show them. Another option would be to just switch completely to MSO way to track changes.

Currently there is a button to  show/hide changes (on appropriate toolbar without turning on experimental features) - so if showing track changes disturbs anybody - these can be just switched off and you will always see the latest text with all changes as in MSO. At the same time there remains ability to accept/deny changes whenever there would be needed to decide it.
Comment 33 Edmund Laugasson 2017-08-17 22:18:16 UTC
Basically as there is already a button to show/hide track changes, there would be nice to have a button "Show track changes on edge" (optionally allow also choose either right or left edge) or "Switch to MSO track changes mode". Then it would be easy to switch between two track changes mode. The only missing feature seems to be to show these different color bubbles with changes on edge. Hiding changes already exist which makes the result actually comparable with MSO. Instead of these colorful bubbles there is a track changes management dialog where all changes with names, date/time and comments are shown and can be actually managed in a very compact and fast way.
Comment 34 Edmund Laugasson 2017-08-17 22:26:13 UTC
(In reply to Christoph from comment #3)
> There have been some ideation iterations within the OOo Notes2
> implementation, see "Change Tracking Integration" at:
> http://wiki.services.openoffice.org/wiki/Notes2_OtherIdeas
> 
> The mockup I've created that time:
> http://wiki.services.openoffice.org/wiki/File:
> Notes2_GeneralMockups_RoughIdeas_ReviewTools_ForIdeasList.png

This mockup looks actually very nice. I guess this could be an option to turn such feature on but leave also an option to use current version of track changes. I guess there could be different modes of track changes and then users can decide which one to use.
Comment 35 Edmund Laugasson 2017-08-18 12:14:48 UTC
To conclude I would say as follows. I tested track changes also in MS Word 2016. There is default mode exactly as in LO Writer currently - nothing is displayed on right edge as there is simple mode by default. Only changed lines will be marked on left as in LO Writer. I used other language version than English and choice names here are not exactly as they might be in MS Word - it's my free translation.

If to turn on track changes "full mode" then by default only attribute changes will be shown as bubbles on right edge. If to turn on "show corrections in bubbles" then you will see all corrections on right edge bubbles. There is also a mode "show only corrections and comments in bubbles" which is also missing on LO.

In my humble opinion managing changes in compact track changes management window is very compact and comfortable way. But it would be nice to have also a MS Word way as MS Word already has a LO Writer way.

These three bubble displaying modes (only attributes, all corrections, only corrections and comments) are missing in LO and what people want. Implementing these three modes into LO would be the first challenge for developers.

In addition in MS Word 2016 there is possible to choose what type of corrections (bubbles) will be shown on edge (these three modes).

Also there is possible to choose persons, who's corrections will be shown. In LO there is filtering in track changes management window but it works only for filtering results in management window and not directly in text. This would be the second challenge for developers.

in MS Word 2016 there is also a mode "show corrections inline" - this is exactly the mode LO Writer is currently using.

In MS Word there is also an option to show only comments and attribute changes in bubbles on right. That is feature I could not find in LO Writer. The most important are comments and these can be managed currently in LO only in track changes management window. This is certainly very compact and quick way and I like it but it would be nice to have also that way as MS Word does. This could be the third challenge for developers.

So I mentioned three challenges for developers by my humble opinion in order to bring track changes onto level people probably want and why this bug report has been created already so long time ago.
Comment 36 Edmund Laugasson 2017-08-18 12:22:30 UTC
As I cannot edit a comment I need to post a new one.

I wanted instead of "In addition in MS Word 2016 there is possible to choose what type of corrections (bubbles) will be shown on edge (these three modes)."

... to say:

In addition in MS Word 2016 there is possible to choose what type of corrections (bubbles) will be shown on edge:
* comments
* ink text
* added, deleted parts
* formatting

in LO Writer such filtering can be done only inside track changes management window but not directly in text. Current way is great but in "display in text" would be a good addition to track changes management window for all of previously described features that are currently only available in that track changes management window.
Comment 37 Cor Nouws 2017-08-18 13:10:37 UTC
(In reply to Edmund Laugasson from comment #34)

> This mockup looks actually very nice. I guess this could be an option to
> turn such feature on but leave also an option to use current version of
> track changes. I guess there could be different modes of track changes and
> then users can decide which one to use.

Indeed. Also because with a lot of changes, the margin could become over-populated.

@Edmund: thanks for the write-up of possible improvements. (comment #35 and comment #36). Those are good for one (more?) separate issues, I guess.
Comment 38 Gerry 2017-08-18 15:29:03 UTC
@Edmund @Cor:

I really look forward to seeing improvements in Track Changes in Writer. This is an area, where LibreOffice does not shine compared to the competition. Due to these limitations, it is difficult to convince people who are used to collaborative editing to use Writer. 

Do you know the "Track Changes" page in the documentfoundation wiki? There are links to related bugs and there is also the start of a competitive analysis:
https://wiki.documentfoundation.org/Track_changes

Please feel free to add/update the competitive analysis there and also new ideas/mockups!

And please don't just copy MS Word's track changes feature. It is far from perfect either.
Comment 39 Sherilyn 2018-06-25 01:44:17 UTC Comment hidden (me-too)
Comment 40 Benoît Robin 2018-07-10 09:34:57 UTC
Hi all,

Just filed bug #118660, didn't have the right seach keywords, then I changed keywords and found this one, which is basically the same. This is my second time in the LO Bugzilla, 1st time was years ago for the same reason, and I still use only MS Word instead of LO Writer for writing novels and short stories.

I just want to understand why this feature, which has already been demanded many times along the years, hasn't been done yet, particularly as its lack is steadily reported, year after year, as a major roadblock for LOW adoption in place of MSW...

Upon reading some comments, it seems it's linked with a global refit of the Change Rendering System, whose full feature set is still undecided. As the major blocking issue for MS replacement with LO is dealing with deleted text, shouldn't it be possible to display only deleted texts in balloons, leaving further elaborations on the Change Rendering System for when the topic matures ?

Apart from that, is there a technical issue ? Some other undecided questions with conflicting opinions that block the decision process ? A patent somewhere making the balloons unusable ? I just can't figure what could be that blocking on such an important feature !

Thanks in advance if anyone has a clear vision of the situation about this issue ^-^
Comment 41 Benoît Robin 2018-07-10 09:54:32 UTC
Still seems not to be there in 6.1.RC1
Comment 42 V Stuart Foote 2018-07-10 11:50:09 UTC
*** Bug 118660 has been marked as a duplicate of this bug. ***
Comment 43 whynot 2018-08-06 10:56:07 UTC
I also still can't believe we've had to wait forever. 

However, there may be a silver lining. I have the online version of LibreOffice installed on a server of mine (LOOLWSD 3.3.1, LOKit Collabora Office 5.3-53, the CODE implementation). It turns out that it shows both insertions and deletions next to the document (together with information about the time, the user who did the edit, and buttons to accept/reject and even a comment function). In the document, however, it is still showing all the edits as well, notably the deletions in strikethrough font. 

Now, this is not exactly what we are looking for, but at least it shows that it is possible to implement this functionality in a quite straightforward way. What it does is that it shows both insertions and deletions in the document AND on the side (essentially showing every edit in two different ways). I guess what most of us want would be to show the insertions in the document (in a different color) and the deletions on the side. 

Unfortunately, LibreOffice online does not provide a lot of ways to change the settings; nothing is offered to change the display of changes. But the observation suggests that it should not be all that difficult to implement it. After all, LibreOffice usually only implements a subset of what full LO is capable of. Is there any way this could be brought to the attention of the developers, especially if this is perhaps not a huge deal to do?
Comment 44 Benoît Robin 2018-08-09 07:18:17 UTC
Yes, the idea is basically to display the final text in readable form, show insertions by using another colour, and display deletions apart from the main text.

This evolution shows it can be done quite easily. Next logical step seems to add display options for controlling what is shown or not. It's the logical path : first show everything you can, then fine-tune the display.

So at last there is some hope !
Comment 45 Jean-Baptiste Faure 2018-08-10 20:49:15 UTC
(In reply to Benoît Robin from comment #40)
> [...]
> Apart from that, is there a technical issue ? Some other undecided questions
> with conflicting opinions that block the decision process ? A patent
> somewhere making the balloons unusable ? I just can't figure what could be
> that blocking on such an important feature !

I see several reasons:
1/ it is a bad idea: balloons make the original text unreadable thus the comparison between old and new text is more difficult. That is my opinion and I guess I am not alone.

2/ nobody is motivated enough to implement this change.

3/ LibreOffice is not a clone of MS-Office and it is not motivating to ask for cloning existing software: we should search for something that would be better than current LO and better than MSO.

Best regards. JBF
Comment 46 Benoît Robin 2018-08-17 07:21:15 UTC
Thanks JF for answering my questions.

As for (1), I can well understand people would sometimes want to read the original text, that's why the feature should include toggles for different display modes.

I can also understand (2) and I'm afraid I lack both skills and time to lend a hand.

(3) seems to me much more debatable. As a final user, I would say I won't care a damn if the chosen solution is already used elsewhere. I just want to read the final text unhindered while still having access to the changes. If that specific feature isn't available, I just won't be able to use LO for my writing usage, period, and I'll be forced to use MS, even while I'm a LO supporter at heart. If balloons do the job, so be it... If there was another solution available, so be it... But I can't understand stalling the issue just because no NEW solution has yet been found, while an evident one already exists, but is already used elsewhere.

Just to write something positive ^-^ if we absolutely want to be different from MS, we could offer display modes (original+changes) or (final+changes), with a one-click inline/balloons toggle for insertions, if I remember well there is no such thing in MS.
Comment 47 Benoît Robin 2018-08-17 07:22:17 UTC Comment hidden (obsolete)
Comment 48 Benoît Robin 2018-08-17 07:23:16 UTC
And sorry for JF instead of JBF, malfunctioning neurons, sure...
Comment 49 elisa wise 2018-10-02 02:27:11 UTC Comment hidden (spam)
Comment 50 whynot 2018-12-13 18:41:35 UTC
@Jean-Baptiste: 

I appreciate sharing that a balloon view is not your preference. However, many have a completely different preference. I suppose that further suggests that this should be a changeable setting. 

I personally agree with many, many in this thread that the balloon visualization of changes is a "must-have" feature. I spend the majority of my day writing, and I professionally depend on it. For me this feature is so critical and important that I simply cannot use LibreOffice for collaborative writing with my entire team. 

I use the mode in MS Word where it shows the final version of the document, but highlights the deleted text in balloons on the border. Personally, I think that having the cross-out text in the middle of the remaining text makes it visually very challenging, and in many cases unreadable. The other disadvantage of keeping the deleted text and showing it in "cross-out" letters is that it bloats the length of the document. What I find so beautiful about the "balloon mode" is that the document looks very similar to the final version, but the deleted stuff is still visible on the sidelines. For many things we write, the length of the document is very critical. If you keep the deleted text in there (cross-out), the document will appear to get longer and longer, the more changes there are (and it becomes less readable). This will mess up a lot of things in the document, for instance how text flows around figures, etc. 

A few years ago, someone maintained a "wish list" web page with the Top 10 most desired features for LibreOffice/OpenOffice. This particular request was solid #1 pretty much the entire time. So there are A LOT of people who really, really want and need this feature. I think some of the comments on this thread also reflect this. Based on this background, commenting that this is simply a "bad idea" is not helpful. I understand that people have different preferences, and FOSS is all about choice. Telling users that there need and wish of having this feature is a bad idea is not really appreciative of their feedback.
Comment 51 blargh 2018-12-13 21:17:18 UTC
(In reply to whynot from comment #50)
> @Jean-Baptiste: 
> 
> I appreciate sharing that a balloon view is not your preference. However,
> many have a completely different preference. I suppose that further suggests
> that this should be a changeable setting. 
> 
> I personally agree with many, many in this thread that the balloon
> visualization of changes is a "must-have" feature. I spend the majority of
> my day writing, and I professionally depend on it. For me this feature is so
> critical and important that I simply cannot use LibreOffice for
> collaborative writing with my entire team. 
> 
> I use the mode in MS Word where it shows the final version of the document,
> but highlights the deleted text in balloons on the border. Personally, I
> think that having the cross-out text in the middle of the remaining text
> makes it visually very challenging, and in many cases unreadable. The other
> disadvantage of keeping the deleted text and showing it in "cross-out"
> letters is that it bloats the length of the document. What I find so
> beautiful about the "balloon mode" is that the document looks very similar
> to the final version, but the deleted stuff is still visible on the
> sidelines. For many things we write, the length of the document is very
> critical. If you keep the deleted text in there (cross-out), the document
> will appear to get longer and longer, the more changes there are (and it
> becomes less readable). This will mess up a lot of things in the document,
> for instance how text flows around figures, etc. 
> 
> A few years ago, someone maintained a "wish list" web page with the Top 10
> most desired features for LibreOffice/OpenOffice. This particular request
> was solid #1 pretty much the entire time. So there are A LOT of people who
> really, really want and need this feature. I think some of the comments on
> this thread also reflect this. Based on this background, commenting that
> this is simply a "bad idea" is not helpful. I understand that people have
> different preferences, and FOSS is all about choice. Telling users that
> there need and wish of having this feature is a bad idea is not really
> appreciative of their feedback.

I could not agree more with this comment.
It is probably the most mentioned missing feature when it comes to collaborative writing and the reason many groups use MS Word for anything that requires input from several users, be it a one-page letter or a long report.
Comment 52 Linda Rose 2018-12-21 06:57:36 UTC Comment hidden (spam)
Comment 53 alicetaylor 2019-03-07 06:30:44 UTC Comment hidden (spam)
Comment 54 Linda Rose 2019-04-01 01:57:12 UTC Comment hidden (spam)
Comment 55 linapham 2019-04-02 05:03:40 UTC Comment hidden (spam)
Comment 56 phamyen94 2019-04-02 05:34:11 UTC Comment hidden (spam)
Comment 57 minianna1234567 2019-04-03 04:41:46 UTC Comment hidden (spam)
Comment 58 samy 2019-04-25 07:36:59 UTC Comment hidden (spam)
Comment 59 Sara Taylor 2019-06-20 11:56:44 UTC Comment hidden (spam)
Comment 60 dipsha35a 2019-06-27 05:21:03 UTC Comment hidden (spam)
Comment 61 dipsha35a 2019-06-27 05:22:35 UTC Comment hidden (spam)
Comment 62 dipsha35a 2019-06-27 05:24:09 UTC Comment hidden (spam)
Comment 63 dipsha35a 2019-06-27 05:24:53 UTC Comment hidden (spam)
Comment 64 dipsha35a 2019-06-27 05:30:05 UTC Comment hidden (spam)
Comment 65 mariabraga 2019-06-27 09:41:31 UTC Comment hidden (spam)
Comment 66 dipsha35a 2019-07-06 13:40:24 UTC Comment hidden (spam)
Comment 67 arpita 2019-07-29 11:52:47 UTC Comment hidden (spam)
Comment 68 arpita 2019-07-29 11:53:37 UTC Comment hidden (spam)
Comment 69 arpita 2019-07-29 11:54:04 UTC Comment hidden (spam)
Comment 70 Pinky Bansal 2019-08-30 07:55:08 UTC Comment hidden (spam)
Comment 71 Pinky Bansal 2019-08-30 07:55:43 UTC Comment hidden (spam)
Comment 72 jameslite123 2019-09-05 06:17:48 UTC Comment hidden (spam)
Comment 73 theLYRICALLY Lyrics 2019-09-05 15:04:21 UTC Comment hidden (spam)
Comment 74 macpipfzr 2019-09-26 13:42:11 UTC
I can confirm that this required new feature is critical for many production environments where many people work together on the same document.
I also can confirm that I know cases where the entire company cannot migrate to LO just because of the lack of this feature 

In order to the required implementation of the new feature, I recommend to keep in mind all those environments where many people does not use the LO source document but "printed" copies of its releases, either physical print-out copies of the document or images of it (eg. tiff, pdf, jpg ...).
Here, the user of the printed copy NEEDS to know which parts the document had been modified since the previous revision, but each revision NEEDS to appear as similar as possible to the final document. Generally, the last released revision is the final one until an if a change is required.
So previous releases may have been the final one for a long time.

For these cases, to me, the solution should be something like:

The "Show Changes" menu should present two independent options:

  - "Show changes marker" option:
if enabled the side marker (the thin black line generally on the left of the modified text), meaning that those lines have been affected by changes, is shown. The marker should be printable as it is today.

  - "Show previous text" option:
if enabled the modified text should be shown in-line the same way it is shown today

This way, if both these options are enabled the behaviour is exactly the same as today.

About balloons, that's good idea. The "Show previous text" option could be split in "... as in-line test" or "... as balloons".

The "Manage Changes" tool should permit to change the previous options. 

Everywhere in this comment: Should => I'd like :)
Comment 75 Benoît Robin 2019-09-26 15:19:26 UTC
Simple and nice solution, I would vote for it if I knew how to vote for a proposal ^-^
Comment 76 Cor Nouws 2019-09-28 21:55:48 UTC
(In reply to macpipfzr from comment #74)
> I can confirm that this required new feature is critical for many production
> environments where many people work together on the same document.
> I also can confirm that I know cases where the entire company cannot migrate
> to LO just because of the lack of this feature 
Thanks for your ideas on how to implement the features.

As for the need of this in production environment: a reliable and relatively easy way to do is, is getting professional support from (a) certified developer(s).
On this page you can find them
  https://www.libreoffice.org/get-help/professional-support/
It would be considerably helpful if you give a hint to the relevant cases you know.
Thanks, Cor
Comment 77 Domino 2019-10-02 02:37:48 UTC Comment hidden (spam)
Comment 78 Alex Jacob 2019-10-05 06:18:48 UTC Comment hidden (spam)
Comment 79 Amit Singh 2019-10-08 20:08:28 UTC Comment hidden (spam)
Comment 80 Thiago Sueto 2019-10-09 13:42:49 UTC
Hello, as a translator/proofreader, balloons would be incredibly helpful.

I typically proofread academic articles.

On average, a very well-written paper have 10 corrections per page, whereas usual papers would have around 30 corrections per page, bad ones will range between 40 and 60, and exceedingly bad ones range at around 70 to 90.

Usual papers are mildly/really annoying to check with inline changes, while bad or exceedingly bad ones can be borderline unreadable.

At work, I tried using multiple office suites, including WPS Office, Softmaker Office, OnlyOffice, even MSOffice 2010.

My colleagues stick to WPS Office for mainly two reasons: balloons, ribbon and change scrolling (namely, when the document is terribly filled with corrections and the side area where they usually lie gains a scrollbar to navigate through changes.

The ribbon got pretty good with version 6.3 and while the scrollbar is incredibly useful too, it would be more useful if balloons were there too, which makes balloons a priority compared to scrollbars.

In addition, for other users, a new way to check popularity of bugs is this page:

https://wiki.documentfoundation.org/QA/Stats/MostCCBugs

Where the present bug report lies in #11 place in general and third place in LibreOffice Writer, so this continues to be a very requested feature.
Comment 81 Jeff 2019-10-11 05:41:35 UTC Comment hidden (spam)
Comment 82 diljitdosanjh 2019-10-24 02:38:13 UTC Comment hidden (spam)
Comment 83 atim jha 2019-10-24 10:31:53 UTC Comment hidden (spam)
Comment 84 mohit08 2019-10-29 03:11:11 UTC Comment hidden (spam)
Comment 85 Simhadri 2019-11-22 10:30:10 UTC Comment hidden (spam)
Comment 86 Xisco Faulí 2019-11-29 13:30:10 UTC Comment hidden (off-topic)
Comment 87 RTEUA 2019-11-30 05:48:27 UTC Comment hidden (spam)
Comment 88 LyricsMama1530 2019-11-30 12:45:26 UTC Comment hidden (spam)
Comment 89 Xisco Faulí 2019-12-02 12:53:52 UTC Comment hidden (off-topic)
Comment 90 Dpbin 2019-12-22 12:04:41 UTC Comment hidden (spam)
Comment 91 Jatin 2019-12-25 04:56:21 UTC Comment hidden (spam)
Comment 92 renzy mehtha 2019-12-26 10:59:13 UTC Comment hidden (spam)
Comment 93 renzy mehtha 2019-12-26 11:00:18 UTC Comment hidden (spam)
Comment 94 renzy mehtha 2019-12-26 11:00:48 UTC Comment hidden (spam)
Comment 95 emilysmith 2019-12-28 12:55:34 UTC Comment hidden (spam)
Comment 96 swastik angar 2020-01-02 01:50:41 UTC Comment hidden (spam)
Comment 98 gaon 2020-01-03 09:39:47 UTC Comment hidden (spam)
Comment 99 feelmusiclyrics 2020-01-03 17:50:48 UTC Comment hidden (spam)
Comment 100 Parth chavda 2020-01-04 01:05:13 UTC Comment hidden (spam)
Comment 101 swastik angar 2020-01-04 01:29:26 UTC Comment hidden (spam)
Comment 102 Ge 2020-01-04 11:49:38 UTC Comment hidden (spam)
Comment 103 Dua Specialist 2020-01-05 07:47:46 UTC Comment hidden (spam)
Comment 104 aram malik 2020-01-07 12:55:32 UTC Comment hidden (spam)
Comment 105 Deepak 2020-01-09 14:01:06 UTC Comment hidden (spam)
Comment 106 swastik angar 2020-01-10 01:58:00 UTC Comment hidden (spam)
Comment 107 swastik angar 2020-01-11 02:22:10 UTC Comment hidden (spam)
Comment 108 swastik angar 2020-01-12 02:11:51 UTC Comment hidden (spam)
Comment 109 mani 2020-01-13 03:41:19 UTC Comment hidden (spam)
Comment 110 Mcart Shopee 2020-01-15 12:34:50 UTC Comment hidden (spam)
Comment 111 swastik angar 2020-01-17 00:22:36 UTC Comment hidden (spam)
Comment 112 swastik angar 2020-01-17 01:39:15 UTC Comment hidden (spam)
Comment 113 jv001 2020-01-22 15:49:40 UTC Comment hidden (spam)
Comment 114 hiren 2020-01-22 19:29:39 UTC Comment hidden (spam)
Comment 115 naa songs 2020-01-24 10:17:03 UTC Comment hidden (spam)
Comment 116 MostMags 2020-01-25 09:53:01 UTC Comment hidden (spam)
Comment 117 John Cruyf 2020-01-25 13:49:56 UTC Comment hidden (spam)
Comment 118 Rohan 2020-01-26 11:19:22 UTC Comment hidden (spam)
Comment 119 Rohan 2020-01-26 11:21:48 UTC Comment hidden (spam)
Comment 120 Rohan 2020-01-26 11:23:58 UTC Comment hidden (spam)
Comment 121 Deepak 2020-01-27 13:49:48 UTC Comment hidden (spam)
Comment 122 Harnoor Kaur 2020-01-29 10:39:19 UTC Comment hidden (spam)
Comment 123 Harnoor Kaur 2020-01-29 10:40:02 UTC Comment hidden (spam)
Comment 124 Harnoor Kaur 2020-01-29 10:40:33 UTC Comment hidden (spam)
Comment 125 MostMags 2020-01-30 04:13:30 UTC Comment hidden (spam)
Comment 126 SHUBHAM 2020-01-31 11:48:12 UTC Comment hidden (spam)
Comment 127 Lyrics 2020-01-31 17:01:09 UTC Comment hidden (spam)
Comment 128 MostMags 2020-02-01 04:37:37 UTC Comment hidden (spam)
Comment 129 Deepak 2020-02-01 09:01:33 UTC Comment hidden (spam)
Comment 130 Bibhu Prasanna Mohanty 2020-02-05 07:46:58 UTC Comment hidden (spam)
Comment 131 santosh 2020-02-29 17:43:43 UTC Comment hidden (spam)
Comment 132 Manoj Mehta 2020-03-04 08:45:10 UTC Comment hidden (no-value)
Comment 133 Anjali Singh 2020-03-09 06:50:09 UTC Comment hidden (spam)
Comment 134 Anjali Singh 2020-03-09 06:51:22 UTC Comment hidden (spam)
Comment 135 Xisco Faulí 2020-03-09 11:05:21 UTC Comment hidden (off-topic)
Comment 136 Riya Mittal 2020-03-12 09:35:40 UTC Comment hidden (spam)
Comment 137 Heiko Tietze 2020-03-16 17:00:40 UTC
This honey pot for spammers need a solution, not least to get rid of the spam.

Luckily it's more or less implemented, though as experimental feature. Check Tools > Options > Advanced > Experimental to get the changes in the sidebar. This list needs some refinement to become an equivalent to the inline tracking (that you would switch off). In particular the actual change needs to be shown. But I would go a step further and make the type of information variable, eg. per dropdown menu as we have for toolbars. There are different use cases to solve with this sidebar and some may need the change, other the author.

We could, of course, introduce a completely different solution with TC in the document margin. But I wouldn't do so as it weakens our main interaction element, the sidebar. And it is a lot additional effort.
Comment 138 lyricsnona 2020-04-03 12:22:16 UTC Comment hidden (spam)
Comment 139 mani 2020-04-20 10:58:19 UTC Comment hidden (no-value)
Comment 140 techiibug 2020-04-20 15:02:39 UTC Comment hidden (spam)
Comment 141 kartik 2020-04-21 10:50:35 UTC Comment hidden (spam)
Comment 142 Abhishek 2020-04-28 07:17:36 UTC Comment hidden (spam)
Comment 143 Jack Son 2020-04-28 10:09:46 UTC Comment hidden (spam)
Comment 144 lyricsmin 2020-04-30 18:15:11 UTC Comment hidden (spam)
Comment 145 lyricsmin 2020-04-30 18:20:41 UTC Comment hidden (spam)
Comment 146 Shivam 2020-05-03 14:32:02 UTC Comment hidden (spam)
Comment 147 Satyam 2020-05-13 07:16:06 UTC
For your information: "Use margins to track changes" is the *Number 2* of the TopTen for Enhancement Requests on the Documentfoudation Wiki. \
Comment 148 Johannes Rohr 2020-05-13 12:35:48 UTC
(In reply to Heiko Tietze from comment #137)
> This honey pot for spammers need a solution, not least to get rid of the
> spam.
> 
> Luckily it's more or less implemented, though as experimental feature. Check
> Tools > Options > Advanced > Experimental to get the changes in the sidebar.

Actually, that's just the bad old "manage changes" dialogue now moved to the sidebar. And as you say, it does not actually show the changes, it just indicates date and author. So I can't see the improvement in it. (checked with LO 6.4.4 from Debian backports)
Comment 149 Thiago Sueto 2020-05-13 14:14:01 UTC
(In reply to Heiko Tietze from comment #137)
> This list needs some refinement to become an equivalent to the inline
> tracking (that you would switch off). In particular the actual change needs
> to be shown.

There are at least four more issues with the sidebar:

It needs to have a distinct separation between pages. Track changes in margin (let's call it TCM for now) shows only the changes done *in each page*. The sidebar as currently implemented shows a list of changes done in the *entire document*, which can be fine *if* once the user scrolls or clicks a certain page the sidebar immediately shows that page's contents.

It needs some sort of highlighting or indication of where the change was done. One of the advantages of TCM is that you can either search for the change on the side and follow where it is, or search for the location of the change and then follow what was changed. With a sidebar, it doesn't seem possible to implement a colored line linking the location and the change like the TCM does, but perhaps there's an alternative to that. Not having that kind of defeats the purpose of an alternative to TCM. The implementation varies, but usually it's a thicker line for the selected change and a dotted line for non-selected changes.

It needs better use of vertical and horizontal space. The current implementation is a box whose size does not extend to the max allowed for the user's screen. In a 1920x1080 screen, it does not even use half of the vertical space. Additionally, text size is the same as the rest of the interface and all information is densely packed, which is bad, since one of the advantages of TCM is being able to quickly distinguish each change. Each implementation does it a little different, but some ways to visually distinguish information easier is by using different colors (each author has an assigned color), different font weights (author name can be bold while the content of the text is regular), line spacing, boxes (the outline of baloons), a button to show the entire change if it's big... If I recall correctly, MS Word has approximately 3 lines minimum for each change and it will display all information if there's empty space, WPS Office has only 2 but a click on the change expands the balloon.

It needs reasonable automatic default behavior. Like mentioned above, immediately show page changes once the user scrolls or clicks the page; expand the content of the change shown in the sidebar if the user selects text containing or contained within the change or if they click the sidebar change; return the sidebar change to its original size if the user clicks elsewhere; show the entire content of the change on mouse hover.

Whereas there are two advantages of the sidebar:

> But I would go a step further and make the type of information
> variable, eg. per dropdown menu as we have for toolbars.

One is precisely that, the ability to filter which changes are displayed and which are not.

The other is the ability to scroll through the list of changes. I honestly believe the WPS Office implementation of TCM works better and is more visually pleasing than that of Microsoft Word, for instance, precisely because it does highlighting, scrolling, and good use of vertical and horizontal space (2 lines suffices). While the sidebar is quite different, it achieves the same result.

> There are different use cases to solve with this sidebar and some may need the change, other the author.

I fully agree. When I proofread text, I almost never need to see the author of the change (since I'm usually the only one to add changes to the document), only the change itself. I can imagine a peer-reviewer would need to see the author, change, comments, and date, that a company employee working collaboratively would need to see the comments, author, and change, that a school/university student would only like to see the comments, etc.
Comment 150 Benoît Robin 2020-05-13 14:53:08 UTC Comment hidden (me-too)
Comment 151 Benoît Robin 2020-05-13 15:50:36 UTC Comment hidden (me-too)
Comment 152 Benoît Robin 2020-05-13 15:55:45 UTC Comment hidden (me-too)
Comment 153 Heiko Tietze 2020-05-13 17:49:25 UTC
(In reply to Thiago Sueto from comment #149)
> There are at least four more issues with the sidebar:

Thanks for the elaborated assessment. Just to complete the sidebar argument, the design team put together some aspects into a mockup at https://design.blog.documentfoundation.org/2015/02/19/tracking-changes-with-libreoffice/. Not so sure anymore that inline balloons are a good solution and the filtering feels over-engineered in this context. But basically I'd stick to the sidebar and pick you input to make this solution shiny.
Comment 154 thelyricsnepal 2020-05-30 05:14:59 UTC Comment hidden (spam)
Comment 155 Muna deep 2020-06-08 15:29:12 UTC Comment hidden (spam)
Comment 156 Aafrin khan 2020-06-12 06:18:46 UTC Comment hidden (no-value)
Comment 157 Benoît Robin 2020-06-12 06:41:00 UTC
Hi all,


Thanks for the work folks ^-^ Countless thanks to you all, the dream of having a proper text display with tracked changes out of the way is coming true.

However, no need to make it shiny from the start. Releasing it as is, with changes displayed, but not in the main text, will satisfy most people who, like me, are complaining about year-long lack of this basic feature. Polishing can come further down the road.

Of course, the threat is to forget polishing, but I don't think that will happen, because the devs who did it will want to get it shine ^-^

How long for it to make its way into Ubuntu's default updates ? I'll look at how to get it asap from more advanced ppa's...

Anyway, many thanks to all who delved into it and are making it exist !
Comment 158 Benoît Robin 2020-06-12 06:56:13 UTC
(In reply to Heiko Tietze from comment #137)
> This honey pot for spammers need a solution, not least to get rid of the
> spam.
> 
> Luckily it's more or less implemented, though as experimental feature. Check
> Tools > Options > Advanced > Experimental to get the changes in the sidebar.
> This list needs some refinement to become an equivalent to the inline
> tracking (that you would switch off). In particular the actual change needs
> to be shown. But I would go a step further and make the type of information
> variable, eg. per dropdown menu as we have for toolbars. There are different
> use cases to solve with this sidebar and some may need the change, other the
> author.
> 
> We could, of course, introduce a completely different solution with TC in
> the document margin. But I wouldn't do so as it weakens our main interaction
> element, the sidebar. And it is a lot additional effort.

I tried it on 6.2.8.2 on Ubuntu 18.0.4.LTS and does not appear. This is what I did :
- Go to Tools > Options (Outils > Options in French)
    It opens the options popup
- Go to LibreOffice > Advanced (LibreOffice > Avancé)
    It displays the "Options - LibreOffice - Advanced" page
- Check the box "Activate experimental features (Activer les fonctionnalités expérimentales"
    It pops up a "Restart LibreOffice" box
- Restart LibreOffice
- Open a random file and save it with a TEST name to be sure not to override anything
- Activate changes recording
- Replace a word with another in the text
    The replaced word still appears as strikethrough in the text, making the text unreadable and LibreOffice unsuitable for my needs

Could you please check if I did something wrong and tell me how to activate the feature ? Thanks a lot in advance !
Comment 159 Heiko Tietze 2020-06-12 07:24:00 UTC
(In reply to Benoît Robin from comment #158)
> ...The replaced word still appears as strikethrough in the text

If you switch View > Track Changes off (or the left-most button at the toolbar) the item is gone in the document but the change will be listed in the Manage Changes tab of the sidebar (that appears only in advanced mode).
Comment 160 Benoît Robin 2020-06-12 07:41:48 UTC
(In reply to Heiko Tietze from comment #159)
> (In reply to Benoît Robin from comment #158)
> > ...The replaced word still appears as strikethrough in the text
> 
> If you switch View > Track Changes off (or the left-most button at the
> toolbar) the item is gone in the document but the change will be listed in
> the Manage Changes tab of the sidebar (that appears only in advanced mode).

Hi Heiko Tietze,


Thanks for your reply.

However, the main point of this issue is about readability of the main text :

     DISPLAYING DELETED TEXT WITHIN THE MAIN TEXT BODY MAKES MAIN TEXT UNREADABLE

It's that issue that prevents many people from using LibreOffice and so, fixing that issue is enough.

I admit a side point of the bug might be about how the "manage changes" sidebar box appear and prompt devs to improve the box.

These cosmetic changes might be well and good, but they won't do anything for convincing people to use LibreOffice despite that they can't grok the main text anymore whenever they delete a word and changes display is on !!!!!!

That's what I and some other commenters have been saying for years, and invariably the topic keeps going off-track to the appearance of the box, filtering, authors, dates and so on, instead of just solving the actual, simple issue...
Comment 161 Heiko Tietze 2020-06-14 11:33:59 UTC
(In reply to Benoît Robin from comment #160)
>      DISPLAYING DELETED TEXT WITHIN THE MAIN TEXT BODY MAKES MAIN TEXT
> UNREADABLE

Please read my comment carefully. Advice was to hide the changes (View > [ ] Track Changes off). If you are not interested in showing the changes at all, just ignore the sidebar tip.
Comment 162 Benoît Robin 2020-06-17 08:56:47 UTC
(In reply to Heiko Tietze from comment #161)
> (In reply to Benoît Robin from comment #160)
> >      DISPLAYING DELETED TEXT WITHIN THE MAIN TEXT BODY MAKES MAIN TEXT
> > UNREADABLE
> 
> Please read my comment carefully. Advice was to hide the changes (View > [ ]
> Track Changes off). If you are not interested in showing the changes at all,
> just ignore the sidebar tip.

Hello Heiko Tietze,


Sorry for our mutual misunderstanding ^-^ I do want to have the changes displayed, otherwise the whole issue is irrelevant.

So I'll try to be clearer :

- So the changes must be displayed :
    - In the current implementation, inline deletions impair reading;
    - so they must not be displayed inline;
    - which means they must be displayed elsewhere.

- the choice of the "elsewhere" seems to divide so much :
    - Actually it's of no importance at all in a first step;
    - if multiple places can exist, I'd say first implemented wins ^-^

- afterwards, it'll be time to refine :
    - Ask the question of where it's best to display deletions;
    - there could even be multiple places and let the user choose;
    - and also the question of displaying user/time/version or other information along with the changes;
    - all that can only be done once deletions are displayed in a place where they do not impair reading...

I just wanted to stress that "what elsewhere is chosen" can't be allowed to be blocking for "having a working elsewhere"...
Comment 163 secretfun 2020-07-05 12:19:45 UTC Comment hidden (spam)
Comment 164 Vicky 2020-07-14 10:33:50 UTC Comment hidden (spam)
Comment 165 Vicky 2020-07-14 10:34:53 UTC Comment hidden (spam)
Comment 166 ankita takur 2020-08-15 12:52:38 UTC Comment hidden (spam)
Comment 167 ankita takur 2020-08-16 03:56:17 UTC Comment hidden (spam)
Comment 168 Cosmin Saveanu 2020-08-19 08:51:37 UTC
It's been said several times in the comments, this is a "must have" option for LibreOffice. One of the reasons I do not often use the "track changes" feature was exactly the loss in readability resulting from keeping chunks of deleted text in the main window. I tested the solution explained in comments 158-160 and it is good to have at least a way to see that there were some changes made. For additions, it is even possible to see what text was added (it becames selected when selecting in the sidebar the modification).

Maybe the first implementation of this highly demanded feature could be, for example, adding the modification in the sidebar along the date. There is space there.
Comment 169 Riya Pant 2020-09-26 18:49:15 UTC Comment hidden (no-value)
Comment 170 Amrita Hengde 2020-10-05 11:27:58 UTC Comment hidden (spam)
Comment 171 Venkatesh 2020-10-07 14:29:16 UTC Comment hidden (spam)
Comment 172 Dhruba 2020-10-13 09:57:51 UTC Comment hidden (spam)
Comment 173 Dhruba 2020-10-13 09:59:35 UTC Comment hidden (obsolete, spam)
Comment 174 Commit Notification 2020-10-15 13:11:37 UTC
László Németh committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/1e383097aa929176bac33f46787e16d945a0a98b

tdf#34355 sw,offapi,officecfg: show track changes in margin

It will be available in 7.1.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 175 László Németh 2020-10-15 13:43:53 UTC
See "See also:" for remaining tasks and improvements.

Full commit description:

tdf#34355 sw,offapi,officecfg: show track changes in margin

In ShowTrackedChanges mode, hide tracked deletions
in text optionally and show their shortened text
in margin next to the vertical "Changed line" mark
(showing only the first deletion of the line).

Add "Tracked deletions in margin" checkbox to Writer->View page.

Add "Display tracked changes" and "Outline View" sections to View, too.

Add property ShowChangesInMargin to com::sun::star::text::ViewSettings.

Add config setting:
    org/openoffice/Office/Writer/Content/Display/ShowChangesInMargin

Show more information in Manage Changes dialog window
about the tracked deletions with restricted visibility
in ShowChangesInMargin mode: show shortened text content
of a deletion in its (otherwise empty) Comment field.
Comment 176 Benoît Robin 2020-10-17 17:06:29 UTC
Thanks László Németh for handling this long-sought bugfix !

I'll try to get my hand on the daily built on my Ubuntu, this one is a life changer...
Comment 177 Heiko Tietze 2020-10-21 08:41:51 UTC
(In reply to László Németh from comment #175)
> Full commit description...

The patch adds a -<text> to the margin for the first deletion. It abbreviates with ellipsis in case a long portion was deleted (-<long te...>). Further deletions in this line are not added to the margin. I think so far it makes sense and is clear to users (and looks pretty nice, by the way). Replacements like when you change "And" to "Or" are annotated as deletion, which is okay.
What is missing from my point of view is the same if something is added. I expect something like +<text>.
Annotation for formattings is probably not need but could otherwise be a symbol.

Do you want new ticket(s), László?
Comment 178 BogdanB 2020-10-21 18:55:57 UTC
Created attachment 166600 [details]
screenshot

Under "Outline mode" there is no option...
See screenshot.

Tested in version
Version: 7.1.0.0.alpha0+
Build ID: f1d798151048dde3f48b124ef406416668d1e9c5
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 179 Heiko Tietze 2020-10-22 08:29:05 UTC
Created attachment 166614 [details]
Screenshot running master

Edit > Track Changes

Version: 7.1.0.0.alpha0+
Build ID: b16d11c9d85f60867f634f5049e38c1f62d8d412
CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 180 kalimantra 2020-10-25 08:11:41 UTC Comment hidden (spam)
Comment 181 Heiko Tietze 2020-10-26 08:45:15 UTC
Closing this honey pot for spammers. Please file new tickets for follow-up requests. Some issues, in particular regarding undo, have been reported and Laszlo is taking care.
Comment 182 Way To Lyrics 2020-11-10 09:05:01 UTC Comment hidden (spam)
Comment 183 pancard230189 2021-04-27 05:41:17 UTC Comment hidden (spam)
Comment 184 Ritik 2021-06-17 13:54:16 UTC Comment hidden (no-value)
Comment 185 sudarsan 2022-02-01 05:43:27 UTC Comment hidden (spam)