https://bugs.documentfoundation.org/show_bug.cgi?id=54068
--- Comment #17 from Roman Riabenko <[email protected]> --- Hello. I would like to highlight some essential use cases for this missing feature if they are not obvious. First of all, in bilingual documents, where the texts in different languages must be presented side by side, for example in cross-border transactions. Many clients and counter-parties make changes without using the "Track Changes" mode. When continuing negotiations of a contract, it is important to see which changes were made by whom. Thus, it is necessary to run a comparison of a previous and a newer versions, then join the changes into a single document, and continue working in it with the changes shown. Another use case is in documents with long pares or rows of values, such as contracts with specifications of goods. When a modified version of the document is returned, it is often necessary to see what details changed, add your changes, and then pass it to somebody for review, where it is important to retain information about the side of negotiations that made particular changes even if somebody did not use the "Track Changes" in the same document. Finally, when a team worked on a document, there may be a lot of changes by different internal contributors, but it is necessary to present a unified position without revealing different internal opinions. Thus, it is necessary to run a comparison to attribute all changes to a single organization. Converting the table to text is not a viable workaround in any of those common use cases because it does not allow to continue working in a document with the changes remaining tracked and to present changes for further review. I hope that the above information is helpful for understanding how to implement the feature. Version: 25.2.5.2 (X86_64) / LibreOffice Community Build ID: 520(Build:2) CPU threads: 4; OS: Linux 7.0; UI render: default; VCL: gtk3 Locale: uk-UA (uk_UA.UTF-8); UI: en-US Calc: threaded Roman -- You are receiving this mail because: You are the assignee for the bug.
