Grammar and Spell Checker - LanguageTool에 대한 리뷰
Grammar and Spell Checker - LanguageTool 제작자: LanguageTooler GmbH
리뷰 4,617개
- 5점 만점에 4점Firefox 사용자 16290193 님, 7달 전
- 5점 만점에 1점Firefox 사용자 14782093 님, 7달 전
- 5점 만점에 2점Adam Baker 님, 7달 전Money-grubbing BS. Useless for anything longer than 1,000 words, unless you upgrade to the paid version.
Still better than Firefox's default dictionary, but not by much. - 5점 만점에 3점spootboot2 님, 7달 전I am just so sick of not having any spell check/grammar check software catch anything, even if it is behind a paywall like this one. Originally, I was just relying on the spell check on MS Word to catch things on my graduate papers before submitting them, but it that was useless. So I added a different extension add-on for Word and used both to no avail. They still missed stuff. So I downloaded the Language Tool extension and realized that it would catch more advanced mistakes if you paid for it... I am in the process of working on my Master's capstone, so I need all the help I can get. I pay for it and add it to MS Word. Tell me why all three of those spell checks don't catch when there is a duplicate word?? Or a missing period at the end of a sentence?? Or even when there is a jumble of words together that don't make sense like, 'before the in study was performed...". What is the point of me paying for the advanced version of LT if it still will not catch even the simplest mistakes? Maybe I am expecting too much.
- 5점 만점에 2점Firefox 사용자 18867700 님, 7달 전Dark mode for every website. Take care of your eyes, use dark theme for night and daily browsing.
- 5점 만점에 5점Firefox 사용자 17945149 님, 7달 전
- 5점 만점에 5점Firefox 사용자 18455663 님, 7달 전
- 5점 만점에 5점Firefox 사용자 17789848 님, 7달 전Ich bin total begeistert. Eine Super-Hilfe, die mich auf dem Weg zum fehlerfreien Schreiben sehr gut unterstützt. - Vielen Dank!
- 5점 만점에 5점Cootelette 님, 7달 전
- Getting the following error in Nextjs 15.1.7 app only due to this extension. Fixed when I disabled this extension. Please fix this asap:
Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used.
- A server/client branch `if (typeof window !== 'undefined')`.
- Variable input such as `Date.now()` or `Math.random()` which changes each time it's called.
- Date formatting in a user's locale which doesn't match the server.
- External changing data without sending a snapshot of it along with the HTML.
- Invalid HTML tag nesting.
It can also happen if the client has a browser extension installed which messes with the HTML before React loaded.
- data-lt-installed="true"