| Summary: | UI Indicate change tracked formatting changes in readable format | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | NISZ LibreOffice Team <libreoffice> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | heiko.tietze, nemeth, varga.balazs3 |
| Priority: | medium | ||
| Version: | Inherited From OOo | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=50447 https://bugs.documentfoundation.org/show_bug.cgi?id=147169 |
||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 137770, 143050 | ||
| Attachments: |
Example file from Word with tracked character formatting changes
Screenshot of the original document side by side in Word and Writer |
||
|
Description
NISZ LibreOffice Team
2021-08-17 13:56:45 UTC
Created attachment 174358 [details]
Screenshot of the original document side by side in Word and Writer
I think this is welcome and may be put to New. UX part is how to make it useful, how to show that info. You can get TC in the margin (at least deletions), see bug 34355 and bug 137770 for what's missing. And based on [1] we have a sidebar for TC (requires experimental features) with bug 87695 for the missing pieces. So let's make this ticket a duplicate and improve what we have. [1] https://design.blog.documentfoundation.org/2015/02/19/tracking-changes-with-libreoffice/ *** This bug has been marked as a duplicate of bug 87695 *** (In reply to Heiko Tietze from comment #3) > You can get TC in the margin (at least deletions), see bug 34355 and bug > 137770 for what's missing. And based on [1] we have a sidebar for TC > (requires experimental features) with bug 87695 for the missing pieces. > Yes, but I think you misunderstood this bug: this is not about adding new UI pieces to show the CT information, but about showing more CT information (the changed formatting in writing) on the existing UI. Reopening: this issue is not covered in the duplicate. And this is specific, while other bug is general and needs a summary. So you suggest to show the actual formatting that was applied. Laszlo implemented the info at the document margin for bug 34355 but with some shortcomings, that is: one change only, no addition, no formatting. I believe the margin has its limit (wonder how MSO shows multiple TC in one line). The (experimental) sidebar deck shows all changes but with a details only for deletions. My take is to improve this, that's why I made it a duplicate of bug 87695. Some ideas, mostly about filtering and likely stretching the point, were proposed in https://design.blog.documentfoundation.org/2015/02/19/tracking-changes-with-libreoffice/. (In reply to Timur from comment #5) > And this is specific, while other bug is general and needs a summary. Maybe I still miss the point. What specific request is done here? I like this proposal. The changes in formatting could be shown either - on the right/left side, where Word shows, or - in the Manage Changes dialog, before or after the Comment column, or - both of the above. It is really annoying to know that the information is there, LO knows what was changing but I cannot access this info in an easy way. I like this proposal. The changes in formatting could be shown either - on the right/left side, where Word shows, or - in the Manage Changes dialog, before or after the Comment column, or - both of the above. It is really annoying to know that the information is there, LO knows what was changing but I cannot access this info in an easy way. So let's do it. Both, the margin but primarily the comment at the sidebar/dialog should tell what exactly has been changed. It works for deletions but only if the "track deletions in margins" option is checked. Unfortunately I cannot change these comments anymore, all input goes into the following non-deletion change. My take here is to add the action information to the comment and keep it editable. An alternative is to show the details in a tooltip. Similar request in bug 147169. This might be the easier and more flexible yet less obvious solution. |