-
Thanks for the great extension! Just wondering whether it is possible to configure |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Thanks for the suggestion. Up to now, LTEX didn't treat tables specially and forwarded them directly to LanguageTool, which led to the false positives (which have annoyed me as well). Actually, it's surprising there were not more false positives with all the dashes and pipes. It's better to solve the problem at its root, i.e., support tables instead of disabling rules for the whole document, which might lead to false negatives elsewhere. I didn't know this, but there are lots of extensions for LTEX's Markdown parser Flexmark. One of them is for tables as in GitHub Flavored Markdown. I enabled that and I think the false negatives about too much whitespace in tables should be gone now/in the next release of LTEX 👍 Regarding the general question, I'm hesitating to (further) split settings for different markup languages (or enable users to apply them only for specific markup languages), as this will increase UX complexity, and when done consistently, all settings could be split up like that. Ideally, in my head, LTEX is a one-size-fits-all solution that does all the heavy lifting in the background, and users shouldn't have to worry too much about doing/configuring things differently for different markup languages. |
Beta Was this translation helpful? Give feedback.
Thanks for the suggestion. Up to now, LTEX didn't treat tables specially and forwarded them directly to LanguageTool, which led to the false positives (which have annoyed me as well). Actually, it's surprising there were not more false positives with all the dashes and pipes.
It's better to solve the problem at its root, i.e., support tables instead of disabling rules for the whole document, which might lead to false negatives elsewhere.
I didn't know this, but there are lots of extensions for LTEX's Markdown parser Flexmark. One of them is for tables as in GitHub Flavored Markdown. I enabled that and I think the false negatives about too much whitespace in tables should be gone now/in th…