Back to LanguageTool Homepage - Privacy - Imprint

New browser add-on released for Chrome

(Andriy) #3

Ok, it seems to work on some other web-pages. So maybe those couple of pages were just not supported.

(Daniel Naber) #4

That page uses spellcheck=false and the add-on currently accepts that and doesn’t appear. We’ll add a better UI for that soon, so the user understands the issue or can overwrite the page setting.

(Andriy) #5

Cool, thanks!

(Daniel Naber) #6

Maybe I misunderstood you: when you said it doesn’t work, didn’t it work for you at all, i.e. didn’t you even see the underlines for errors? Have you tested in the source code view on the left or the rendered HTML on the right?

(Andriy) #7

So I’ve tried it quickly on two pages and both of them didn’t show any signs of LT in the text fields. So I checked button at the top and checked context menu but found nothing to perform the check.
I must say on pages that it works on everything is cool, I see pretty visible indicator and results (although I would go for different color for grammar errors, it’s a bit too subtle now - but that’s my personal preference).
If we add some indication for cases when checking is off that would be very helpful.
Otherwise, looks great, thanks for the upgrade!

P.S. just noted one thing - it checks Ukrainian wikipedia page properly but language stays English, if I switch to Ukrainian it again checks properly but after check is done resets back to English.

(Daniel Naber) #8

Are the pages you tested public, so I can try them? Also, if your add-on version is not 2.0.3, please uninstall and re-install to get the update. In the future, updates will be automatic again.

(Andriy) #9

I’ve updated to 2.0.3 and the language is now showing properly.
The two sites I’ve tried had spellcheck=“false” (e.g.
The other that didn’t work is comment field on this page (I didn’t find spellcheck attribute there though).

(jaumeortola) #10

The add-on is auto-detecting the language on every sentence, isn’t it?

That’s fine, but there are some undesired results. I don’t know how frequent they are. For example, the Catalan short sentence “Uns quants exemples.” is analyzed as Portuguese (with two spelling errors!).

(Daniel Naber) #11

Please let me know what version you have. If it’s < 2.0.4, please uninstall and reinstall. You should get 2.0.4 then, where this issue is supposed to be fixed. If it’s not, please let me know.

(jaumeortola) #12

It was 2.0.2.

With 2.0.4, there is auto-detect, but only one language for the whole text.

(Daniel Naber) #13

That’s on purpose for now to avoid the issue you had with 2.0.2. I’m not sure yet how to get the best of both worlds. Maybe just use per-paragraph language detection if the paragraph exceeds a certain length so the detection becomes very reliable?

(Andriy) #14

I’ve tried new Chrome addon (2.0.4) on comment field in Facebook for Ukrainian and for some reason only grammar errors are highlighted, spelling errors are ignored.
E.g. for “Десь там прійшов матеріял.” only 4th word is highlighted (alternative spelling), 3rd one should be caught by speller module.

(Daniel Naber) #15

Thanks for the report. I can reproduce and have added it to our to do list. (It’s not limited to Facebook, BTW).

(Josep Bofarull Gallés) #16

At the moment I only tried it in Catalan language, it looks fine and works better. I understand that in short sentences it confuses language but its not big a problem for me.
My version is 2.0.2
Good job Daniel.

(Josep Bofarull Gallés) #17

Now I just installed 2.0.4 version and tried the short sentence “uns quants exemples” and is analyzed as Portuguese. Tried “Ara poso uns quants exemples” and is analyzed as French. Finally, I write “Catalan: Ara poso uns quant exemples” and checks OK in Catalan.

(Daniel Naber) #18

This is now fixed in 2.0.5. You might get it automatically, otherwise you’ll need to uninstall and re-install.

(Andriy) #19

It works great now, thanks!

(Konstantin Ladutenko) #20

New plugin is awesome! However, there are two problems:

  1. It conflicts with Grammarly plugin. So I opted out to turn LT plugin off, in general Grammarly detects more problems in English. It would be nice if they could work simultaneously. Note that Grammarly plugin has more that 10M of users, while for LT it is just 140k. However, LT is the best available choice for my native language for in-browser writing.
  2. Now LT does not work in Overleaf online editor (the previous version was OK). Overleaf is a major online tool for scientific writing (>600k users), they had promoted LT plugin in their blog
  3. LT plugin doesn`t work in the text input of these forum :slight_smile:

(Daniel Naber) #21

Thanks for the feedback.

Overleaf has an editor that uses neither contenteditable nor textarea, so similar to Google Docs we’ll need to rely on Overleaf to add an integration.

It works for me, are you sure you’re using the latest version (2.0.5) of the add-on?

(Konstantin Ladutenko) #22

Yep. I had to enable LT plugin back and to restart the browser to make it work in the input form of this forum.

So, the main problem is the conflict with Grammarly.

Is it possible to add an option to select any text and check it with LT via plugin? May be, without being able to correct errors in text, however, at least a convenient way to list them. There is always an option to copy text to LT website and check it this way, however, this leads to a lot of additional actions.