Date: prev next · Thread: first prev next last
January 2020 Archives by date, by thread · List index


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

--- Comment #5 from sdc.blanco@youmail.dk ---
(In reply to Heiko Tietze from comment #4)
there are people who claim buttons to have meaningful captions. 
Interesting article, good principles, but there are no rules until you break
them.

IMHO your proposal is still better than mine in terms of easy to understand,
shortness, translateability.
I think you are already inclined to keep “yes” and no” – which I support – but
here are additional arguments for this “habenero” choice.

1. Confirmation box only comes for modified documents (i.e., an intended action
is interrupted, which is not always interrupted).
2. User has already chosen to reload (with File▸Reload), and (critically) has
probably already decided why reload is wanted. In effect, the confirmation box
is asking to “confirm” a decision made BEFORE getting to that box. (a little
different than a typical Rule 1 situation, where a new choice is introduced)
3.  Two decisions are being made in this confirmation (saving/reloading). Hard
to reduce to “one (clear) action verb” (per Rule 1)
Will “Save Changes” also “Reload”? (violates Rule 3! “Users need to know the
result of their actions”)

With support from Rule 3, “yes” for “yes/no/cancel”

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.