Date: prev next · Thread: first prev next last
July 2017 Archives by date, by thread · List index


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

Nick Levinson <Nick_Levinson@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
         Resolution|WORKSFORME                  |---

--- Comment #5 from Nick Levinson <Nick_Levinson@yahoo.com> ---
No, that's the wrong use case. I'm not talking about erroneous spellings but
about correct-but-rare spellings that probably don't belong in current
contexts. In those cases, users should be asked to confirm that they intend to
use the spelling that's present. Most of the time, they'll see it as an error
and correct it, but, because the spelling is sometimes (rarely) correct,
they'll sometimes want to leave it as is.

I think this can be done by adding a Boolean (true/false) field to every entry
in every dictionary. The default entry would be false (as in 'false spelling').
But if a user could supply a file of rare-but-correct spellings or could edit a
single entry, the status of true would mean 'true spelling albeit rare'.

That leaves how the UI should inform users of likely-misapplied rare spellings.

An extension would seem appropriate for the UI once the rarities are
recognizable but probably not to the necessary hooks in LibreOffice, especially
the additional field. Since the hooks would need something in LO itself, I'm
restoring this report's status.

-- 
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.