When hovering over a tracked-change (insertion/deletion), show, as part of text in the hover pop-up, not just the date and editor who affected the change, but also the comment regarding the change (with some cutoff for length perhaps). Suggested by Telesto in bug 166814 comment 6.
It makes sense to me. Hmm, I now see why '.uno:CommentChangeTracking' being a 'hidden' feature. Compatibility. Those '.uno:CommentChangeTracking' can't be saved in DOCX So there is not much of a use-case for CommentChangeTracking
(In reply to Telesto from comment #1) > Those '.uno:CommentChangeTracking' can't be saved in DOCX ... > So there is not much of a use-case for CommentChangeTracking I don't see how the second sentence follows from the first one. So, DOCX is missing a feature? Tough cookies for people who use that format. The typical use of LO is to edit ODF documents, and that's use case enough.
(In reply to Eyal Rozenberg from comment #2) > (In reply to Telesto from comment #1) > > Those '.uno:CommentChangeTracking' can't be saved in DOCX ... > > So there is not much of a use-case for CommentChangeTracking > > I don't see how the second sentence follows from the first one. > > So, DOCX is missing a feature? Tough cookies for people who use that format. > The typical use of LO is to edit ODF documents, and that's use case enough. I'm skipping couple thinking of steps. You're right in principle. The function is useful. However putting effort in showing CommentChangeTracking is a move into the direction of making CommentChangeTracking (more) productive. However there quite a bunch of people using LibreOffice to edit a DOCX. Or create the initial version in ODS and at some point start converting the file in DOCX. And that's an angry mob who will complain about data loss, I suspect.
(In reply to Telesto from comment #3) > However there quite a bunch of people using LibreOffice to edit a DOCX. Or > create the initial version in ODS and at some point start converting the > file in DOCX. And that's an angry mob who will complain about data loss, I > suspect. So, let's think about the mechanisms for avoiding such a complaint for a second. There's the warning about dataloss when saving to DOCX, right? What about... what happens when you've opened a DOCX, and you use a DOCX-unsupported feature for the first time? Do you get some sort of warning or notice?
(In reply to Eyal Rozenberg from comment #4) > what happens when you've opened a DOCX, and you use a > DOCX-unsupported feature for the first time? Do you get some sort of warning > or notice? There are no specific warnings using unsupported functions while editing a DOCX. Only the non-standard file-format warning when saving as DOCX. And well, if you edit a DOCX you likely want to save it back as DOCX. So you're put for impasse. Saving to ODS, while requiring a DOCX. Or saving to DOCX directly, taking the risk (how bad can it be...) Quite a number of incompatibility's are not even documented; And the documented part goes beyond comprehension for a normal user. --- The more aggressive approach would be to only open non-native formats as read-only. Requiring a save to ods (or one of the other file formats) for editing. Which would make it more obvious that LibreOffice not being alternative DOCX editor, but totally different Office Suite which happens to have import/export support for MSO formats to an certain extend
(In reply to Telesto from comment #5) Opened bug 166835 about this; the discussion probably belongs there. Anyway, no reason not to show the comment on hover...
Not against but the cut-off comments are likely not sufficient informative.