https://bugs.documentfoundation.org/show_bug.cgi?id=155839
--- Comment #9 from Eyal Rozenberg <[email protected]> --- (In reply to Mike Kaganski from comment #3) > There might be some *narrow* set of cases where LibreOffice > could know that *its own* distribution includes these This is what I would expect. The thing is, that if an app is telling you "I am missing FOO for locale LOC", your assumption as a user is that FOO is a part of the app, but distributed separately for different locales; and that you have likely neglected to also install FOO for LOC along with LO itself. Third-party extension and such would not make the app present a notification bar. > - but again: it needs > to know how to install these: on Windows, it would need admin to initiate > modification of existing installation; on Linux, each distro would have own > command and own package name for those... Ok, so it would need admin privileges, that's doable. Or it would need per-distribution customization - also doable, with the default suggesting the user seek a package for their distribution. And the version we let people download from our servers will be appropriately customized to download packages from our servers. > But *in general*, the problem of > knowing how to obtain a random fo-BAR language that user tagged their > hyphenated text with is unsolvable. So, not the general problem, just the problem of obtaining a very specific FOO for LOC. If there are other options for it - that's "not our problem" for the purposes of this notification bar. Or - a secondary button, "Learn More", could mention other options/sources/ideas. i.e. what we offer now is the other possibility for users to pursue, but the default one should just be to download the patterns. > It is a warning that the document looks differently. It is not an error > (like "the file is corrupt"), but still something needing to "draw user's > attention to". If it said that, it would be one thing. But LO is telling you its missing something, and hinting that it is missing a piece of itself. (In reply to Heiko Tietze from comment #6) > Rather than forwarding to a hopefully up-to-date wiki we could show the list > of extension directly (same as tools > options > language > writing aids: > Get more dictionaries online...). I agree with Mike - we should not refer user to extensions, certainly not in this situation; and If LO knows about it beforehand, then it's not an extension. Also, and even more importantly - if you can find the list, then - don't show any list, rather, on button press, let's just download and install the relevant file. I just don't understand the insistence on not doing that or the claim that we can't. -- You are receiving this mail because: You are the assignee for the bug.
