New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spellcheck is pulling out all kinds of words that are spelled correctly #7

Closed
superkinz opened this Issue Jul 17, 2014 · 9 comments

Comments

Projects
None yet
4 participants
@superkinz
Copy link

superkinz commented Jul 17, 2014

When I run my build, it's alerting me to all kinds of words which are clearly properly spelled. See image. Any idea why it's identifying basically every word as misspelled?

screen shot 2014-07-17 at 2 21 09 pm

@minivan

This comment has been minimized.

Copy link
Owner

minivan commented Jul 18, 2014

Could you please show which version of aspell you're using? There might be some formatting differences with different versions.

@superkinz superkinz changed the title Spellcheck is pulling out all kinds of messages that are correct Spellcheck is pulling out all kinds of words that are spelled correctly Jul 18, 2014

@superkinz

This comment has been minimized.

Copy link

superkinz commented Jul 18, 2014

I did a brew install on that, and it gave me aspell6-en-7.1-0. However, when I do bundle show, it's not coming up. Do I need to reference the aspell in my gemfile and config?

@minivan

This comment has been minimized.

Copy link
Owner

minivan commented Jul 21, 2014

It looks like it's the dictionary version.

Could you please show the output of aspell --version ?

On 18 July 2014 20:26, Andrew Kinzer notifications@github.com wrote:

I did a brew install on that, and it gave me aspell6-en-7.1-0. However,
when I do bundle show, it's not coming up. Do I need to reference the
aspell in my gemfile and config?


Reply to this email directly or view it on GitHub
#7 (comment)
.

@superkinz

This comment has been minimized.

Copy link

superkinz commented Jul 21, 2014

Thanks for checking in. Here's what I got:

@(#) International Ispell Version 3.1.20 (but really Aspell 0.60.6.1)

@ukd1

This comment has been minimized.

Copy link

ukd1 commented Jul 30, 2014

I'm getting this too, looking at how to run a different dictionary (US eng)

@superkinz

This comment has been minimized.

Copy link

superkinz commented Aug 17, 2014

Any update on what's going on?

@olds22

This comment has been minimized.

Copy link
Contributor

olds22 commented Oct 20, 2014

I just submitted a pull request that solved this issue for me. Hopefully it works for you too. see: pull request #10.

minivan added a commit that referenced this issue Oct 21, 2014

Merge pull request #10 from torspark/inconsistent_word_array
fixed inconsistent word count issue (Github issue #7)
@minivan

This comment has been minimized.

Copy link
Owner

minivan commented Oct 21, 2014

Merged in, bumped up the version. Thanks a lot @olds22 !

@olds22

This comment has been minimized.

Copy link
Contributor

olds22 commented Oct 21, 2014

Thanks, @minivan for merging pull request #10 in so quickly.

@superkinz & @ukd1, I also had a similar issue on some posts where I'm using code blocks. My guess is the parser has a little trouble with complicated pieces of code. Plus, you'll get a lot of false positives in there anyway, with class names and abbreviated variables, etc. Therefore, I added this line in my config.rb file, which essentially covers most of my content, but skips any generic <div>, <pre>, <code>, & <table> tags:

activate :spellcheck, tags: [:p, :h1, :h2, :h3, :h4, :h5, :h6, :ul, :ol, :blockquote]

Maybe this will work for you too, depending on your site's layout. Note that it will still check tags that are nested within any of the list. So, if you write something like this, it will catch the misspelling in the nested code tag:

%p
  This code word is
  %code misspeled

@minivan minivan closed this in 0eda696 Jun 21, 2015

minivan added a commit that referenced this issue Jun 21, 2015

Merge pull request #12 from wkoszek/master
Fixes #7 and add some more functions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment