[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-08-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

Heiko Tietze  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #8 from Heiko Tietze  ---
Thinking again this might be not fixable. Consider a situation when reviewer1
complained about some word, you change it, and reviewer2 comments on the same
word. No way to align all input unless you make sure the source is not touched.

And since merging documents works as expect, with some quirks, let's close the
ticket as wontfix.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

--- Comment #7 from Bella vGFH  ---
(In reply to Heiko Tietze from comment #6)
> (In reply to Bella vGFH from comment #4)
> > [!!!] ACCEPT/ REJECT window comes up. Document owner *DOES NOT* ACCEPT OR
> > REJECT ANYTHING BUT JUST HITS *CLOSE*.
> 
> Merging documents is a different action than managing changes. Your comment
> sounds as if you take this dialog as a confirmation for the merge operation.
> 
> So the actual request is not a bug neither requires enhancement. It might be
> a documentation gap. Do you agree, Bella?
> 
> Laszlo, can we improve the situation at combining documents from comment 5?

Hi Heiko,
Sorry, not that much into nomenclature, just trying to get a job done ;)
But yes, I do indeed see managing changes as something different than merging
documents. Then again, I did notice, playing around with this, that merging
documents can also mean "just gluing them together", which in my use case would
lead to a multiplication of the same text.
In addition, there is I mentioned earlier; if a reviewer takes a (later)
version of one of the other reviewers who shared their comments earlier, the
"just hit close" work around does not work. This means bottom line that:
[] Yes, LO can combine the documents *with* their comments if all reviewers
start/ work in the original document (original.odf) exclusively.
[] However, if reviewers work in one of the later versions, adding their
changes/ comments to a later version of one of the other reviewers, then LO
throws an error (and I have to resort to the COMBINE" function of MS Word).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

Heiko Tietze  changed:

   What|Removed |Added

 CC||nem...@openoffice.org
 Blocks||83946

--- Comment #6 from Heiko Tietze  ---
(In reply to Bella vGFH from comment #4)
> [!!!] ACCEPT/ REJECT window comes up. Document owner *DOES NOT* ACCEPT OR
> REJECT ANYTHING BUT JUST HITS *CLOSE*.

Merging documents is a different action than managing changes. Your comment
sounds as if you take this dialog as a confirmation for the merge operation.

So the actual request is not a bug neither requires enhancement. It might be a
documentation gap. Do you agree, Bella?

Laszlo, can we improve the situation at combining documents from comment 5?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83946
[Bug 83946] [META] Tracking changes issues
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

--- Comment #5 from Bella vGFH  ---
...although playing with this further, I do notice this only works if reviewers
change the original, base document (original.odf).
When, as frequently happens in practice, one of the reviewers picks a version
of one of the other reviewers and starts changing, adding to that, then LO
comes back with a "Can't merge documents".
Executing this scenario with "Combine" function in Word does succeed, and
results again in a document with all alterations and comments combined into one
final document.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

--- Comment #4 from Bella vGFH  ---
I've been playing around with this during the weekend, and think I found that
LO 7.3 can do this, but you have to know how and fight your reflexes.

The way I managed it is (see attached examples):
[] The owner of the document (original.odf) writes the doc and sent it out to
reviewers.
[] Reviewer 1 deleted something and added a comment (reviewer_001.odf)
[] Same thing for reviewer_002.odf
[] Having received the reviewed docs back, document owner opens the original,
base document (original.odf) and turns on TRACKS CHANGES (if not ON already).
[] Then EDIT > TRACK CHANGES > MERGE DOCUMENT
[] Document owner selects reviewer_001.odf to merge with original.odf.
[!!!] ACCEPT/ REJECT window comes up. Document owner *DOES NOT* ACCEPT OR
REJECT ANYTHING BUT JUST HITS *CLOSE*.
[] Result: changes from reviewer_001.odf are added to original.odf. A SAVE AS
under a new name would be wise (result.odf).
[] Document owner repeats this process, now adding the changes of
reviewer_002.odf to the (new) result.odf, again hitting *CLOSE*.
[] Document owner saves result.odf, which now holds the original base text, and
all changes and comments from reviewer 1 and 2.

So thank you gentlemen for thinking with me on this! Like I wrote, it's
possible, although perhaps not clear in the GUI, and by fighting your reflexes
to "go for the obvious" (ACCEPT/ REJECT). Whether the devs want to hard code
this procedure and put it under a menu option/ button as a (cheap and easy ;)
new feature, I leave to those smarter than me...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

--- Comment #3 from Bella vGFH  ---
Created attachment 178834
  --> https://bugs.documentfoundation.org/attachment.cgi?id=178834=edit
Example of COMBINE of different document versions

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

Heiko Tietze  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #2 from Heiko Tietze  ---
How about a confirmation dialog asking "Keep comments from both documents?
[Yes] [No]" after picking the file via merge documents?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 147528] [FEATURE REQUEST] LibreOffice Writer - Review > Combine multiple documents with comments function (MS Word similar)

2022-03-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147528

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
   Keywords||needsUXEval
 CC||dgp-m...@gmx.de,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #1 from Dieter  ---
Thank you for your request. I add desing-team for further input and decision

-- 
You are receiving this mail because:
You are on the CC list for the bug.