https://bugs.documentfoundation.org/show_bug.cgi?id=161516

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |stephane.guillou@libreoffic
                   |                            |e.org
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |needsUXEval

--- Comment #1 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
I agree this is confusing and is an issue that needs resolving.

(In reply to Jeff Fortin Tam from comment #0)
> "Compare Document with a Previous Version…"
> (if that's indeed what it does)
I feel like using terms that relate to recency or relative age is not the right
solution. A user might be comparing their version of a document with another
person's version, with diverging histories but no clear "before" and "after".

The help[1] does use "newer" vs "older":

> You should always start with opening the newer document and compare it with 
> the
> older document.

Maybe using a term like "reference" or "base" would be better?

But really, I feel like this feature should have an intermediate step that lets
the user choose which document is the base and which one is compared to the
base, because the current UX is very, very poor:

1. open base document
2. compare
3. see that direction is wrong
4. close document
5. open modified document
6. compare, now in the right direction

UX/Design team, opinions? Band-aid relabel, or more involved (but possibly a
interesting easyHack) intermediate step?

[1]:
https://help.libreoffice.org/latest/en-US/text/shared/guide/redlining_doccompare.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to