https://bugs.documentfoundation.org/show_bug.cgi?id=155839
Eyal Rozenberg <eyalr...@gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needsUXEval
CC| |libreoffice-ux-advise@lists
| |.freedesktop.org
--- Comment #2 from Eyal Rozenberg <eyalr...@gmx.com> ---
(In reply to Mike Kaganski from comment #1)
> LibreOffice only tells you the fact.
Notification bars are not about telling me facts; they're about drawing my
attention to a problematic situation which I may/should want to address.
> It has no way to know that *any* language's hyphenation data is available
> from *any* source (third party extension? maybe on OOo/AOO extension site?);
> or maybe in another product (MS Word that can generate ODT?).
Sure it has. If LO can know when an update is available, it can know whether
hyphenation patterns are available.
But even if you were to argue it shouldn't actively go look for the hyphenation
patterns for the locale(s) you use - it should still do so if you ask it to,
i.e. it will tell you you're missing patterns, and when you click, it will
either get them for you, or tell you they're missing. Not as great, but better
than what we have now.
> And it can't do that. And tells. Nothing wrong at all.
If this were an _error_ message, that would be a different matter. But it
isn't. It leads the user to believe that they can get those hyphenation
patterns.
> And - well, unless you require that all language modules are installed
> unconditionally (which I personally would welcome, but many would hate),
> there's no way to even point to downloads, because it may be not
> downloadable, but installable - from the MSI on Windows; from packages on
> Debian...
I'll again make the analogy regarding LO updates. Yes, this may be
difficult/impossible/distribution-specific. In those case, we should offer an
easy customization point for distributors, plus, we should make some effort to
help the user get what they need. That is, depending on how LO was installed
and/or what we know about the OS/DE, we should point the user to the closest
thing possible to a download link. If it's one of our packages - then it would
be to a corresponding package of the same kind for hyphenation patterns; if not
- the packagers will change this to something which suits them.
Anyway, let's see what the UX design, umm, ad-hoc per-meeting committee thinks
about this.
--
You are receiving this mail because:
You are on the CC list for the bug.
