Suggesting always the assumed misspelled word in the spellchecker

Bug #1667914 reported by Ómar S Harðarson on 2017-02-25
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Undecided
Unassigned

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

The problem with doing that is the question becomes, where to insert the
original word in the list? If you insert it at the top, it is
sub-optimal for words where the suggestions are useful, if you insert it
at the bottom, it becomes painful for the use case you describe -- of
the suggestions list having lots of incorrect entries.

Also, I'm not actually clear on the utility of this. For the use case
you describe -- using a spell checker in a book with lots of domain
special words -- wouldn't the most common operation be to add the word
to the ignored list or a user dictionary? This is not affected by the
suggestions list at all.

1. At the bottom, which will at least save a lot of typing, when only a
character or two needs to be corrected. In the special case when nothing is
found in the dictionary, this will automatically be on the top as the only
option.
2. Domain specific word can be a misspelled word in another domain, so I
would hesitate to add to the user directory
3. Ignoring misspelled domain specific words is hardly an option.

2017-02-26 4:23 GMT+00:00 Kovid Goyal <email address hidden>:

> The problem with doing that is the question becomes, where to insert the
> original word in the list? If you insert it at the top, it is
> sub-optimal for words where the suggestions are useful, if you insert it
> at the bottom, it becomes painful for the use case you describe -- of
> the suggestions list having lots of incorrect entries.
>
> Also, I'm not actually clear on the utility of this. For the use case
> you describe -- using a spell checker in a book with lots of domain
> special words -- wouldn't the most common operation be to add the word
> to the ignored list or a user dictionary? This is not affected by the
> suggestions list at all.
>
> --
> 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

Eli Schwartz (eschwartz) wrote :

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

2. You can have as many user specific dictionaries as you like and load
and save them when needed. Have as many domain specific dictionaries as
you like.

3. Ignoring a word simply ignores it for the current session. So you
lose nothing by ignoring them.

However, since you are satisfied with having the word at the end, I
dont have any problem with that (it will create a few bug reports from
people that will be surprised to see it, but I can bear the cost of
that).

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

Ómar S Harðarson (omarh) wrote :

2-3 Thank you for the guidance.

2017-02-26 12:57 GMT+00:00 Kovid Goyal <email address hidden>:

> 2. You can have as many user specific dictionaries as you like and load
> and save them when needed. Have as many domain specific dictionaries as
> you like.
>
> 3. Ignoring a word simply ignores it for the current session. So you
> lose nothing by ignoring them.
>
>
> However, since you are satisfied with having the word at the end, I
> dont have any problem with that (it will create a few bug reports from
> people that will be surprised to see it, but I can bear the cost of
> that).
>
> --
> 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

Eli Schwartz (eschwartz) wrote :

> 2. Thanks for the correction. Somewhat huge misspelling there! :D

That wasn't a misspelling alert, that was an answer. :)
(Truth be told, I glossed over the misspelling myself.)

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

You *could* just look at your domain-specific dictionary, which lets you
ignore those words while looking for *actual* misspellings, and also
gives you an overview of all domain-specific words in particular...

Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.

 status fixreleased

Changed in calibre:
status: New → Fix Released
woirin (jrwoirin) wrote :

When editing multiple books, the "delete format xxx" function has disappeared. I used this feature regularly after "converting" the books en masse.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers