Opened 5 years ago

Last modified 25 hours ago

#7810 new enhancement

TinyMCE Spell check doesn't recognise 'WordPress'

Reported by: DD32 Owned by: anonymous
Priority: normal Milestone: Future Release
Component: TinyMCE Version:
Severity: normal Keywords: has-patch-upstream
Cc:

Description (last modified by SergeyBiryukov)

I realise that its not WordPress itself which is responsible for the Spell Checking, However, I feel that if WordPress includes a spellcheck functionality, It would be good for it to actually recognise "WordPress" instead of "Word-Press" or "Word Press" (It even goes on to suggest "WarDress" and "Depress"

Does anyone have a contact (Or know who to contact) in order to get "WordPress into the dictionary used, Or maybe how to ignore the WordPress corrections on the result?

Change History (17)

Unfortunately this isn't as easy as adding a word to it. The default in the spell checker is to use Google, but it can also use pspell if installed on the server. Can probably try to hard-code "WordPress" in the js part, so it skips over it.

comment:2   DD325 years ago

The default in the spell checker is to use Google

Then chase up Google! They owe a lot of their indexed content to WP Blogs :P

I guess putting a ticket upstream for a "Custom Dictionary" ability for the plugin could be an idea as well.

I knew it wouldnt be a simple fix, but felt it at least needs to be made a note of :)

  • Milestone changed from 2.7 to 2.8

comment:4   ryan4 years ago

  • Milestone changed from 2.8 to Future Release
  • Keywords needs-testing added

I've added a respective patch to #9798 (Attachment 3).

  • Milestone changed from Future Release to 2.8.1
  • Keywords has-patch added
  • Keywords needs-patch added; has-patch needs-testing removed

The last patch on this ticket depended heavily on #9798. The patch on #9798 has been completely rewritten since 4 weeks ago therefore I think is not ready for testing at this point.
#9798 should to be implemented first and then we need a new patch for this ticket.

  • Milestone changed from 2.8.1 to Future Release
  • Type changed from defect (bug) to enhancement

punting to future then

Related #16285. It's very difficult to do this in TinyMCE.

2 years on, perhaps we should just get GoogleSpell to recognise 'WordPress' instead of handling it our end..

Duplicate: #20820

I've taken the time to patch this in TinyMCE upstream. Essentially, I've added a configurable option with a list of words to be excluded from the spell check. I've patched this for the core spellchecker plugin and submitted a pull request upstream:

https://github.com/tinymce/tinymce_spellchecker_php/pull/8

Whether or not it's adopted by the parent project is entirely up to them. Considering the spellchecker plugin hasn't been updated in over a year (last commit was 11/5/2011), maybe we should consider patching WP's version and just moving forward?

  • Keywords has-patch-upstream added; needs-patch removed

#23097 was marked as a duplicate.

  • Description modified (diff)
  • Severity changed from trivial to normal
  • Summary changed from TinyMCE Spell check doesnt reconise 'WordPress' to TinyMCE Spell check doesn't recognise 'WordPress'
Note: See TracTickets for help on using tickets.