matze-dd

Hi, thanks for this great plug-in! When using it, I came across a very minor issue: LanguageTool returns in its XML reply a string with a collection of suggested replacements,...

Provide output option for single-line messages

1

There seems to be a Vim issue with handling of multi-byte characters, if Vim's `errorformat` is used to parse mult-line messages. [See here](https://github.com/vim/vim/issues/7145) for the bug description. This causes problems...

This problem may occur with LanguageTool 5.0 and 5.1, it has been fixed with the daily snapshot from 2020/10/26 ([see here](https://internal1.languagetool.org/snapshots/)). Versions 4.9.1 and below work well. Apparently, only German...

Message generation by the basic LaTeX filter

5

Currently, the basic filter `yalafi` provides the plain text and a map for character positions. In order to indicate certain problems as LaTeX-related errors, a special mark has to be...

This is due to the implementation of modules for certain LaTeX packages, for instance, `cleveref` and `glossaries`. It may lead to wrong filtering as in ``` \textbf@ ``` which is...

These macros are not related to LanguageTool, but to YaLafi. We should therefore change to `\YY...` which is inspired by the variable names of the great `yacc` compiler tool. We...

We use simple rotating replacements for maths material, as 'C-C-C'. Similarly, short foreign-language inclusions will be substituted this way in the surrounding text flow. This may cause false positives in...

For highlighting of errors in the source text buffer, vim-LanguageTool does not directly use the error location returned by the proofreader. Instead, it tries to identify the reported problematic text...

The delimiter \& in displayed equations will always create white space in the text output.

Since the function modifies members of the global objects 'defs' and 'parms', as well as function variables like 'text\_add\_frame', it may only be active once at each point in time.