-
-
Notifications
You must be signed in to change notification settings - Fork 116
Can not apply document dialect #362
Comments
I can confirm that this issue has appeared recently. The old configuration seems to be valid since a warning does not appear with: "grammarly.config.documentDialect": "british", |
Have you found a way around it @rayvburn ? |
Nope. I've tried to delete the VSCode's workspace configuration and set |
I'm also having this issue, would be great for it to be fixed! |
Same; did the dialect API change? |
I'm also having this issue despite "grammarly.config.documentDialect": "british". |
I have a feeling that the bug appears only in I'm also using LaTeX Workshop to work with |
I just copied the content of the .tex file into an .md file and it still complains about British spellings. |
I have this problem in markdown as well |
Another +1 to this issue. Id be happy to look into it, but is this extension still being maintained? I see a bunch of open PRs and I'm hesitant to dig through code if a change might sit as a PR for an indefinite amount of time. |
I am also affected. |
@znck is there a fix for this? |
Australian seems to work and at least it stops telling me that "minimize" is wrong ("color" is marked as wrong though, see this article: https://www.grammarly.com/blog/how-to-switch-dialects/) |
I have "British English" in Grammarly account preferences on their website. Yet when using from emacs, I am getting "organisation" highlighted, and it suggests changing to "organization". My |
As a workaround, I just added British spellings (colour, optimise, etc.) to my personal dictionary on the Grammarly account and it stopped highlighting them. |
@znck Hi! Is there a fix to this? Is this extension being maintained? Thanks |
I'm also having the same issue. |
I am writing a document with British English, and the settings have worked so far.
However, today I noticed that even by changing the dialect to
british
, it still mark errors regarding to theamerican
dialect.Is there something that I can try to make this work properly again? I already tried to restart the server multiple times.
The text was updated successfully, but these errors were encountered: