Comment 5 for bug 1667914

2. Thanks for the correction. Somewhat huge misspelling there! :D
3. I find it a benefit to see the domain specific words pop up in the
misspelled section. Three days ago I even learned a new proper word that
the dictionary didn't recognize, via that way: "adit"=entry.

2017-02-26 12:43 GMT+00:00 Eli Schwartz <email address hidden>:

> > 2. Domain specific word can be a misspelled word in another domain, so I
> > would hesitate to add to the user directory
>
> domain-specific *user dictionaries*. :)
>
> > 3. Ignoring misspelled domain specific words is hardly an option.
>
> The suggestion was to ignore the properly-spelled word, so I don't know
> why you are objecting to the idea of ignoring misspelled words instead.
> Ignoring the -properly-spelled word will mean only the misspelled form
> will show as an error, without the side effect of persistence in a user
> dictionary.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1667914
>
> Title:
> Suggesting always the assumed misspelled word in the spellchecker
>
> Status in calibre:
> New
>
> Bug description:
> While I applaud the resolution to ticket 1664284, I often come across
> situations where a misspelled word cannot be found in the dictionary
> (e.g. misspelled words, or fantasy world words created by the author),
> but the spell checker suggests a lot of alternatives. I suggest that
> the assumed misspelled word should be one of the options by default,
> thus resolving ticket 1664284 and improve the functionality.
>
> I'm using Calibre version 2.80.0, both 64 and 32 bit, running on
> Windows 10 in both cases.
>
> Thank you ever so much for the product, it only gets better.
>
> Ómar
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/calibre/+bug/1667914/+subscriptions
>

--
mbkv.
Ómar