Why does LTeX check in a different language than ltex.language?

[mykappa]

I have a problem when using LTeX:

Although I have specified "ltex.enabled": true, "ltex.language": "en-US", in my general VScode settings, I still get GERMAN_SPELLER_RULE spell checker warnings in my English LaTeX text. My system language (Windows) is German. How can I stop LTeX from doing this? I just want it to do the spell check in English...

Thanks in advance for any suggestions!

[valentjn]

Your system language should not be related to this. There are some reasons why LT_EX checks in a different language than what ltex.language says in the user configuration, see the docs:

• You set ltex.language in the settings.json of a workspace or a workspace folder.
• You use magic comments.
• You use the babel package.

If it's none of these, then you should open a bug report with the necessary info.

[mykappa]

Thank you for the quick reply!

Indeed, babel seems to be the culprit. I started with a template where babel was included. After some adjustments (and several compilation runs) I deleted the command, since the document language will be English. However, LTeX seems to somehow retain the language settings and continues to display German spelling errors even when I reload VScode and delete all auxiliary LaTeX files.

I don't know if this is a bug or if I'm missing something...

[valentjn]

If the problem persists when reloading the VS Code window, I suspect you still have some babel commands in there. Do a global search for the four commands/environments listed in the docs and delete (not comment out) all occurrences. (Currently, LT_EX is not smart enough to see if a babel command is commented out. I guess this should be fixed soon. This is fixed in the next release.)

LT_EX only uses the T_EX code of the file in which the errors are displayed. No other T_EX files, no auxiliary files.

[mykappa]

Thanks for the clarification. I actually found that one of the commands mentioned was just commented out. Now it works. Great that LTeX will be able to recognize when babel is commented out in the future.

And in general, thank you for providing such a great tool and quick support!

[valentjn]

Fix for commented out babel commands released in 9.0.0.