Changelog

18.7.0 (upcoming)

• 🔧 Change: Disable LanguageTool’s internal per-sentence result cache by default: the ltex.sentenceCacheSize default changes from 2000 to 0. The new per-paragraph fragment cache supersedes it for the edit loop and, unlike the in-process cache, also covers the remote HTTP backend — so keeping the sentence cache around only added CPU/memory overhead and another point of failure. A value of 0 is the natural floor of the capacity setting (2000 → … → 1 sentence → 0 = nothing cached), not a separate on/off flag; internally any non-positive value maps to a null ResultCache, so LanguageTool takes its genuine no-cache code path rather than allocating a zero-capacity cache that would still run its eviction machinery on every lookup. Set ltex.sentenceCacheSize to a positive value to re-enable it. — Andrea Alberti (@alberti42)
• ✨ New: Incremental checking: re-check only the paragraph you edited instead of the whole document on every change. Each document is sliced into paragraph-sized fragments after parsing, and each fragment’s LanguageTool result is cached (keyed by its text and the relevant settings); on the next check, unchanged paragraphs are served from the cache and their diagnostics reprojected to their new positions, while contiguous changed paragraphs are batched into a single LanguageTool request. This also benefits the remote HTTP backend, where only changed paragraphs are re-sent — making large documents practical on the free public API’s per-request and per-minute limits. New optional settings tune it: ltex.paragraphCacheEnabled (default true; set false to disable the cache and check whole regions as before), ltex.maxRequestSize (default 20000, the largest text sent per request), and ltex.paragraphCacheTtlMinutes (default 30, how long idle cached results are kept). — Andrea Alberti (@alberti42)
• ✨ New: Recognize the Emacs / Emacs-Lisp ``name’ quoted-identifier convention (backtick opener, straight-apostrophe closer, inherited from Texinfo) in ;;-style comments so LanguageTool stops flagging the trailing ’ as an unpaired quote and stops spell-checking the wrapped symbol name. The substitution rewrites the closing ’ to a matched backtick before flexmark parses the comment, so the region is recognized as inline code and surfaced to LanguageTool as a Dummy token. Length-preserving (one char for one char), so source-position arithmetic and the shadow-markup mapping that maps diagnostics back to the original file are unchanged; the markup string sent to LanguageTool retains the original apostrophe, so quickfixes and code actions on real LanguageTool matches elsewhere in the same comment still resolve to the user's literal source. Enabled only for codeLanguageId in {elisp, emacs-lisp} where the convention is canonical — Common Lisp has no standardised convention and Clojure uses Markdown-style matched backticks, so both keep the previous behaviour. Plain Markdown documents are also unaffected because the gate is opt-in from ProgramAnnotatedTextBuilder`. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Fix Premium diagnostics whose squiggly range extends past the offending word into surrounding code (visible in editors as a 14-line highlight on a one-word misspelling, and a quickfix that replaces all that intervening content). LanguageTool Premium’s QB_NEW_*_ORTHOGRAPHY and AI_* rule families sometimes extend an orthography match span past the misspelled word — through any intervening markup — up to the start of the next TEXT segment in the annotated text, in an attempt to enforce sentence termination. Because each TEXT segment maps to a contiguous run of source prose separated by code/markup, the resulting LT-reported offset+length could cover hundreds of source characters spanning multiple comment blocks. Clamp toPos to the end of the TEXT segment containing fromPos in LanguageToolRuleMatch.fromLanguageTool, gated on the same isPremiumPunctuationAdjacentSpanRule(ruleId) predicate that governs dictionary-entry normalization, so non-Premium traffic (local Java backend, free HTTP tier) is bit-for-bit unchanged. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Fix silent server hang when checking source files whose line-comment blocks end with a bare comment marker (e.g. an Emacs Lisp block ending with a ;; line that has no content, or any C/Java/Kotlin/etc. block ending with a bare //). Such blocks produced an empty trailing code segment in MarkdownAnnotatedTextBuilder.addComment; the subsequent addMarkup(code.length) call consumed the trailing shadow markup but then bumped newPos past code.length, producing a StringIndexOutOfBoundsException on code.substring(pos, newPos). The exception was raised on the executor thread inside LtexTextDocumentService.didOpen, whose try only catches ExecutionException and InterruptedException, so it was silently dropped and publishDiagnostics was never sent — leaving the LSP server idle and the client waiting indefinitely. addMarkup(Int) now clamps newPos to code.length after consuming a shadow markup, restoring the invariant that the position never exceeds the buffer length. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Fix StringIndexOutOfBoundsException crash when checking comments inside source files with CRLF line endings or certain multi-line content. Two independent off-by-one bugs in MarkdownAnnotatedTextBuilder — a stray trailing \n in addComment’s reconstructed clearCode, and removeComment only detecting \n boundaries while ignoring \r — combined to push a substring index two characters past the end of the source comment, aborting the whole document’s check. Applies to every programming language routed through ProgramAnnotatedTextBuilder (C, Java, Kotlin, Rust, Go, JS/TS, Lisp/Clojure, Lua, Haskell, …); Python comments go through a different path and were not affected. Plain Markdown, L<sup>A</sup>T<sub>E</sub>X, BibT<sub>E</sub>X, etc. were never affected. — Andrea Alberti (@alberti42)
• ✨ New: Accept elisp and emacs-lisp as codeLanguageIds alongside the existing lisp. Editors and LSP clients that natively label .el buffers with one of these names (modern lsp-mode, Neovim’s built-in LSP, some VS Code Elisp extensions) now work out of the box without users having to remap to lisp. Behavior is identical to lisp — same ; / ;; line-comment regex, no block comments — so this is purely an ergonomic alias. The standalone CLI (lsp-cli-plus) also maps the .el file extension to elisp when checking files by path. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Fix silent spell-check disable when ltex.language = "auto" is used with an HTTP LanguageTool backend (including the free and premium public servers). Previously, LT<sub>E</sub>X resolved "auto" locally using LanguageTool’s lightweight SimpleLanguageIdentifier, which returns only bare codes like en, de, pt. For three LT-registered bases (en, de, pt) the bare Language subclass is a grammar-only umbrella with no spell dictionary, so spell-check was silently skipped for English/German/Portuguese text — other LT bases like es, fr, it are full checkers in their bare form and were not affected. Now "auto" is forwarded to the HTTP server together with a new ltex.preferredVariants setting (default ["en-US", "de-DE", "pt-BR"], specifically covering those three bare-insufficient bases), so the server’s own ngram/fasttext detector picks a concrete variant and spell-check runs. Other LT bases are deliberately omitted from the defaults because adding their variants would silently enable regional grammar rules (e.g. Argentinian voseo for es-AR) for everyone writing that language. The response’s language.code is recorded on the code fragment so per-language code actions (add-to-dictionary, disable-rule, hide-false-positive) key correctly. For the local Java backend, bare detected codes are promoted to the first matching ltex.preferredVariants entry before the LanguageTool interface is built. Word completion (CompletionListProvider) applies the same promotion so the bundled completionList.<variant>.txt resource is found. If the HTTP response code is itself still bare — which can happen on a self-hosted languagetool-server deployed without the ngram language-data download, since the server then falls back to a weaker detector — the same ltex.preferredVariants promotion is applied to the response before it is recorded on the code fragment, so spell-check activates against self-hosted instances as well, mirroring the local Java backend’s behavior. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Fix per-language ltex.dictionary, ltex.disabledRules, and ltex.hiddenFalsePositives entries being silently ignored when ltex.language = "auto" is used with an HTTP LanguageTool backend. On the HTTP path, settings.languageShortCode stays at the literal "auto" for the whole session (only the per-fragment code gets back-filled from the server response), but match-filtering looked up the per-language maps with settings.languageShortCode as the key — so the lookup always hit the empty "auto" bucket and entries stored under the concrete variant (e.g. ltex.dictionary["en-US"]) were never applied. Clicking “Add to dictionary” persisted correctly but every subsequent recheck re-flagged the word. Lookups now key on the fragment’s resolved language code, so per-language settings take effect on the first check. The Java backend was unaffected because it rewrites settings.languageShortCode to the resolved variant before the check. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Normalize ltex.language input so regional variants (e.g. fr-FR, it-IT, es-ES) are mapped to the registered LanguageTool tag rather than silently disabling checking. Also accepts case variants of the "auto" sentinel ("Auto", "AUTO") and trims leading/trailing whitespace. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Fix spelling errors for Polish dummies — vscode-ltex-plus#170
• 🐛 Bug fix: Fix several parsing issues in Typst documents — vscode-ltex-plus#169, vscode-ltex-plus#171, ltex-ls-plus#122, ltex-ls-plus#129
• ✨ New: Spell check content blocks in Typst — ltex-ls-plus#128
• ✨ New: Add code language aliases for neovim support — ltex-ls-plus#131, @demenik
• ✨ New: Create official docker images on release#142 — ltex-ls-plus#142, Malik Tuwebti (@Tuwebti)
• 🐛 Bug fix: Fix: spell-check text in org-mode #+CAPTION affiliated keyword — ltex-ls-plus#149, Andrea Alberti (@alberti42)
• 🐛 Bug fix: Offer the “Add to dictionary” code action for spell-check matches produced by LanguageTool’s QB_NEW_*_ORTHOGRAPHY_*, AI_*_GGEC_REPLACEMENT_ORTHOGRAPHY_*, and ES_SIMPLE_REPLACE_* rule families (Premium/HTTP tier plus Spanish common-typo rules). — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Trim surrounding punctuation from “Add to dictionary” entries and from the check-path lookup key for matches from rule families known to emit punctuation-adjacent spans (LanguageTool Premium’s QB_NEW_* / AI_*), so a span like amazng! (length 7) is persisted as the bare word amazng and every later occurrence — amazng,, "amazng", (amazng) — suppresses against the same single entry. Free LT, the bundled Java backend, and the Spanish _SIMPLE_REPLACE_ / Slovak gender-suffix rules always emit bare single-word spans and bypass the normalization entirely; no behavior change for those users. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Markdown: accept spaces and backslashes inside angle-bracketed link destinations (e.g. [text](<path with spaces.pdf>) or Windows-style [text](<C:\Users\My Documents\file.pdf>)), so the link is recognized and surrounding punctuation does not leak into spell-checked text. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Set CompletionItemKind.Text on dictionary completion items. Previously items carried only a label, leaving kind null; clients that map kinds to icons (VS Code, lsp-mode + Corfu, others) fell through to a generic placeholder icon, making LTEX+ word completions look distinct from every other text-based completion source. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Allow textDocument/completion at the very last position of a document. The fragment lookup and prefix scan both used a strict < against code.length, so a cursor sitting one past the last character (an unterminated document with no trailing whitespace) produced an empty list. Loosened both checks to treat the position immediately after the last character as a valid completion site. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Make the markup parser linear instead of quadratic in document length. The shared character-driven loop in CharacterBasedCodeAnnotatedTextBuilder tries on the order of 20–25 anchored regexes per character; the previous implementation called regex.find(this.code.substring(pos)) on every attempt, allocating a fresh String of (code.length − pos) bytes solely to give the leading ^ a position-0 to anchor against. On large documents this byte-copying cost dominated parse time. Replaced the substring with Matcher.region(pos, code.length).lookingAt(), which anchors at pos directly via the JDK’s region API, and wrapped the result in a small adapter that preserves the existing MatchResult semantics so no caller had to change. Measured on a 135 KB org file with all fragments enabled: warm latency drops from ~3.1 s to ~0.23 s (~14× faster). Every fragmentized language (L<sup>A</sup>T<sub>E</sub>X, Markdown, HTML, AsciiDoc, reStructuredText, Typst, org, …) shares the base class and benefits. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Don’t parse regions of the document the user has disabled with a magic comment (e.g. # ltex: enabled=false in org, % ltex: enabled=false in L<sup>A</sup>T<sub>E</sub>X, etc.). Previously the language-specific parser ran over every fragment, including disabled ones, and the result was discarded just before the LanguageTool check. On documents where most of the body sits behind such a directive this dominated request latency: a 135 KB org file with ~130 KB hidden behind enabled=false took ~3 s warm and now takes ~25–55 ms — about the same as if the disabled tail weren’t there at all. The optimization lives in the shared check pipeline and benefits every fragmentized language (L<sup>A</sup>T<sub>E</sub>X, Markdown, HTML, AsciiDoc, reStructuredText, Typst, org, gitcommit, BibT<sub>E</sub>X, …). — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Org: don’t flag the wrapped half of a list item for “first letter not uppercase”. Previously every list-item line emitted a paragraph break at end-of-line, so a continuation line indented to the bullet body (e.g. + A long sentence that wraps\n onto the next line.) was sent to LanguageTool as a fresh paragraph and its lowercase first word was flagged. The parser now tracks the bullet body column and, when the next line is a true wrap (indented past the bullet and not itself a new bullet), suppresses the paragraph break so the wrap stays in the same paragraph. — Andrea Alberti (@alberti42)
• 🐛 Bug fix: Org: spell-check the term in description lists. The prefix of a description-list item (e.g. - Apple :: a red fruit) used to be consumed as one chunk of markup, which silently dropped the term (“Apple”) on the floor — typos in it went unnoticed. The parser now splits the prefix into bullet, term (text), and ` :: separator, so the term reaches LanguageTool and is spell- and grammar-checked like any other word. A single \n` separator keeps the term in the same LanguageTool paragraph as the description, so the description’s lowercase first word (“a red fruit”) is not flagged. — Andrea Alberti (@alberti42)
• 🔧 Change: Update to lsp-cli-plus 2.2.2. See lsp-cli-plus release notes.
• 🔧 Change: Update bundled Java runtime from 21.0.8+9 to 21.0.10+7
• 🔧 Change: Update to LanguageTool 6.8 (see LT release notes)

18.6.1 (October 19, 2025)

• 🐛 Bug fix: Fix Hidden False Positives in vscode-ltex-plus — vscode-ltex-plus#165
• 🐛 Bug fix: Fix magic comments: Allow multiple settings per comment — ltex-ls-plus#119, @Nils1729

18.6.0 (October 13, 2025)

• 🔧 Change: Update to LanguageTool 6.7 (see LT release notes)
• 🔧 Change: Update to lsp-cli-plus 2.2.1. See lsp-cli-plus release notes.
• 🔧 Change: Update bundled Java runtime from 21.0.5+11 to 21.0.8+9
• ✨ New: Add support comprehensive magic comments — ltex-ls-plus#102, @Nils1729
• ✨ New: Add support for various L^AT_EX commands — ltex-ls-plus#100, Dominik Peters (@DominikPeters)
• 🐛 Bug fix: Fix spelling errors for Dutch dummies — vscode-ltex-plus#145
• 🐛 Bug fix: Remove incorrect babel language mapping for estonian — ltex-ls-plus#103, Simmo Saan (@sim642)
• 🐛 Bug fix: ltex.hiddenFalsePositives rules should be JSON, not strings — ltex-ls-plus#105, Jonathan Chan (@ionathanch)
• 🐛 Bug fix: Fix spell checking in square brackets for Typst documents — vscode-ltex-plus#142
• 🐛 Bug fix: Fix Typst parsing. E.g. the statement #set text(lang: "en") caused the entire document not to be checked. — vscode-ltex-plus#157

18.5.1 (April 9, 2025)

• 🐛 Bug fix: Fix slash issue in HTTP URI — ltex-ls-plus#85

18.5.0 (April 4, 2025)

• 🔧 Change: Update LanguageTool 6.6 (see LT release notes)
• 🔧 Change: Update to lsp-cli-plus 2.2.0. See lsp-cli-plus release notes.
• 🔧 Change: Update bundled Java runtime from 21.0.4+7 to 21.0.5+11. No separate beta Java runtime build is required anymore for Windows aarch64.
• ✨ New: Add support for Neorg (LSP language ID neorg) — ltex-ls-plus#55
• ✨ New: Add support for \NewDoumentCommand, \NewDocumentEnvironment, \NewExpandableDocumentCommand, \NewCommandCopy, \NewEnvironmentCopy, \IfNoValueTF, \IfValueTF, \IfBlankTF, \IfBooleanTF and many more (L^AT_EX) — ltex-ls-plus#69
• ✨ New: Add support for AsciiDoc (LSP language IDs asciidoc) — vscode-ltex-plus#128
• 🐛 Bug fix: Fix false positives in Typst — ltex-ls-plus#72
• 🐛 Bug fix: Ignore code blocks and raw text in Typst — ltex-ls-plus#74

18.4.0 (December 23, 2024)

• ✨ New: Add support for apacite commands — valentjn/ltex-ls#268, Benoît Pasquier (@briochemc)
• ✨ New: Add support for \cpageref, \labelcref and variants — valentjn/ltex-ls#266, Loïc Reynier (@loicreynier)
• 🐛 Bug fix: Improved comment parsing and Rust support — valentjn/ltex-ls#238, valentjn/ltex-ls#224, Andrii Savytskyi (@qRoC)
• 🐛 Bug fix: Fix spelling errors for Spanish dummies — vscode-ltex-plus#105

18.3.0 (November 27, 2024)

• ✨ New: Add support for Typst (LSP language ID typst) — ltex-ls-plus#39, vscode-ltex-plus#49
• ✨ New: Add support for MDX (LSP language ID mdx) — vscode-ltex-plus#88
• ✨ New: Add Dockerfile
• 🐛 Bug fix: Bundled ltex-cli-plus did not start due to a wrong setting .lsp-cli.json — ltex-ls-plus#40
• 🔧 Change: Update ltex-cli from https://github.com/valentjn/lsp-cli to https://github.com/ltex-plus/lsp-cli-plus
• 🐛 Bug fix: Fix spelling errors for Swedish dummies — vscode-ltex-plus#89

18.2.0 (October 19, 2024)

• 🔧 Change: Update to most recent Adoptium Java runtimes for Windows aarch64.
• 🔧 Change: Use repository ltex-plus/languagetool-build for building ltex-ls-plus
• ✨ New: Add support for magic comments in (X)HTML files. — ltex-ls-plus#32, Jonas Wischeropp (@JonasWischeropp)
• 🐛 Bug fix: Shorten JSON sent to HTTP server in order to HTTP 413 errors. — valentjn/ltex-ls#228, valentjn/ltex-ls#215, vscode-ltex-plus#49, Tim Ruffing (@real-or-random)

18.1.0 (September 28, 2024)

• 🔧 Change: Update LanguageTool from 6.0 to 6.5. See LT release notes of 6.1, 6.2, 6.3, 6.4 and 6.5.

18.0.0 (September 17, 2024)

• 🔧 Change: Update from Java 11 to 21. Be aware: Starting from LT_EX+ LS 18.0.0, Java 21 or higher is required!
• ✨ New: Add arm64/aarch64 Java runtimes for Linux (e.g. Raspberry Pi), macOS (Apple M1 SoC and its successors) and Windows on ARM.

17.0.1 (August 29, 2024)

• 🐛 Bug fix: Silence output to stdout caused by LanguageTool. This issue caused a crash of LT_EX+ LS on Linux systems. It’s a similar issue to https://github.com/valentjn/vscode-ltex/issues/68

17.0.0 (August 24, 2024)

• 🔧 Change: Rename to LT_EX+ LS
• 🔧 Change: Update bundled Java runtime to 11.0.24+8

16.0.0 (March 19, 2023)

• 🔧 Change: Update LanguageTool to 6.0 (see LT release notes of 5.6, 5.7, 5.8, 5.9, and 6.0)
• ✨ New: Add support for Git commit messages (LSP language IDs git-commit and gitcommit) — valentjn/ltex-ls#132
• ✨ New: Add support for Quarto and R Markdown (LSP language IDs quarto and rmd) — valentjn/ltex-ls#170, valentjn/ltex-ls##172, valentjn/ltex-ls##180, Alexandre Sonderegger (@sondalex)
• ✨ New: Add workaround for Pandoc-style inline display math (Markdown) — valentjn/ltex-ls#131
• ✨ New: Add support for diacritical commands when enclosed in braces (L^AT_EX) — valentjn/ltex-ls#130
• ✨ New: Add support for \newcaptionname etc. from KOMA-Script and \DefineBibliographyStrings from BibL^AT_EX (L^AT_EX) — valentjn/vscode-ltex#490
• 🐛 Bug fix: Fix false positives when using siunitx (L^AT_EX) — valentjn/ltex-ls#134
• 🐛 Bug fix: Fix unquoted languages in YAML front matter not parsed correctly (Markdown) — valentjn/ltex-ls#156
• 🐛 Bug fix: Fix optional argument of Beamer’s frame environment not ignored (L^AT_EX) — valentjn/ltex-ls#161
• 🐛 Bug fix: Fix plural dummy in German languages — valentjn/ltex-ls#178, Stanley F (@sfo)
• 🐛 Bug fix: Add support for \import and \subimport (L^AT_EX) — valentjn/ltex-ls#207
• 🐛 Bug fix: Fix Babel languages austrian, naustrian, swissgerman, and nswissgerman not recognized (L^AT_EX) — valentjn/ltex-ls#213, valentjn/ltex-ls#214, @casenull

15.2.0 (November 28, 2021)

• ✨ New: Add support for ConT_EXt — valentjn/ltex-ls#120
• ✨ New: Add support for strikethrough as in GitHub Flavored Markdown — valentjn/ltex-ls#123
• ✨ New: Always check selected text when running _ltex.checkDocument, even non-comment parts of programs — valentjn/vscode-ltex#457
• ✨ New: Add support for the minted package (L^AT_EX) — valentjn/vscode-ltex#463
• ✨ New: Add support for the Pandoc language variable lang in YAML front matter (Markdown) — valentjn/vscode-ltex#465

15.1.0 (November 5, 2021)

• ✨ New: Add support for some aliases of LSP language IDs: bib for bibtex, plaintex for latex, xhtml for html
• 🐛 Bug fix: Fix LT_EX LS sometimes not properly terminated when using LT_EX CLI — valentjn/ltex-ls#117
• 🐛 Bug fix: Fix error when running ltex-cli from a different directory than bin/

15.0.0 (October 30, 2021)

• 🔧 Change: Add ltex.completionEnabled to disable completion by default — valentjn/vscode-ltex#443
• 🐛 Bug fix: Fix StringIndexOutOfBoundsException in AnnotatedTextFragment.getSubstringOfPlainText — valentjn/vscode-ltex#442
• 🐛 Bug fix: Fix handling of multiple subsequent whitespace characters in XHTML (e.g., CRLF)

14.1.0 (October 19, 2021)

• 🔧 Change: Rename ltex.ltex-ls.languageToolHttpServerUri → ltex.languageToolHttpServerUri; the previous name is deprecated
• 🔧 Change: Rename ltex.ltex-ls.languageToolOrgUsername → ltex.languageToolOrg.username; the previous name is deprecated
• 🔧 Change: Rename ltex.ltex-ls.languageToolOrgApiKey → ltex.languageToolOrg.apiKey; the previous name is deprecated
• ✨ New: Add support for completion requests for English and German — valentjn/vscode-ltex#409
• 🐛 Bug fix: Fix Add '...' to dictionary quick fix missing for Austrian and Swiss German — valentjn/vscode-ltex#431
• 🔧 Change: Move documentation to https://valentjn.github.io/ltex

14.0.0 (October 14, 2021)

• 🔧 Change: Update LanguageTool to 5.5 (see LT 5.5 release notes)
• 🔧 Change: Refactor CLI into ltex-cli; --input-documents and --setings-file are deprecated and will be removed in a future release
• ✨ New: Add support for automatic language detection via language short code auto; language variants like en-US are not detected, only generic languages like en; this will result in spelling errors not being reported — valentjn/ltex-ls#103
• ✨ New: Provide ID of LanguageTool rule via diagnostics code, not as part of diagnostics message
• ✨ New: Link diagnostics to LanguageTool website with more information
• ✨ New: Add support for the main option of the babel package (L^AT_EX) — valentjn/vscode-ltex#391
• ✨ New: Add setting ltex.ltex-ls.languageToolOrgUsername to set username on languagetool.org for Premium API access — valentjn/vscode-ltex#398
• ✨ New: Add setting ltex.ltex-ls.languageToolOrgApiKey to set API key on languagetool.org for Premium API access — valentjn/vscode-ltex#398
• ✨ New: Add support for ltex.dictionary when using a LanguageTool HTTP server
• 🔧 Change: Handle disabled rules ourselves to prevent reinitialization of LanguageTool when running the Disable rule quick fix — valentjn/vscode-ltex#390
• 🐛 Bug fix: Fix LanguageTool reinitialized when running the Add '...' to dictionary quick fix — valentjn/vscode-ltex#390
• 🐛 Bug fix: Fix wrong parsing of inline math formulas in Markdown when using dollar signs as delimiters and containing only one character (e.g., $a$)
• 🐛 Bug fix: Fix used i18n keys removed
• 🐛 Bug fix: Fix fallback from German to English i18n
• 🔧 Change: For binary archives, migrate from AdoptOpenJDK JREs to own Java runtime generated from Eclipse Adoptium JDKs
• 🔧 Change: Update bundled Java runtime to 11.0.12+7 (see list of OpenJDK fixes)

13.0.0 (August 11, 2021)

• 🔧 Change: Migrate from Java to Kotlin
• ✨ New: Add support for checking comments in many popular programming languages — valentjn/vscode-ltex#350
• ✨ New: Add non-server batch mode via --input-documents — valentjn/ltex-ls#71
• ✨ New: Add support for rule-dependent diagnostic severities in ltex.diagnosticSeverity — valentjn/ltex-ls#95
• ✨ New: Add support for vowel dummies in L^AT_EX ("vowelDummy" in ltex.latex.commands) and Markdown ("vowelDummy" in ltex.markdown.nodes) — valentjn/vscode-ltex#366
• ✨ New: Add support for more L^AT_EX commands (\mathop, \overline, \tilde, \alpha, etc.) for automatic vowel detection in formulas in L^AT_EX — valentjn/ltex-ls#92, Shuhao Cao (@scaomath)
• ✨ New: Add support for \counterwithin, \counterwithout, and \numberwithin in L^AT_EX — valentjn/ltex-ls#87, Alexander Zeilmann (@AlexanderZeilmann)
• 🐛 Bug fix: Don’t ignore second argument of \setkomavar in L^AT_EX — valentjn/vscode-ltex#373
• ✨ New: Add support for InitializeParams.locale when using LSP 3.16 or later, deprecate CustomInitializationOptions.locale
• 🗑 Removal: Remove support for magic comments in XHTML
• 🔧 Change: Change format of changelog

12.3.0 (July 12, 2021)

• 🔧 Change: Update LanguageTool to 5.4 (see LT 5.4 release notes)
• ✨ New: Add support for XHTML — valentjn/vscode-ltex#342
• 🐛 Bug fix: Fix diagnostics contain markup before actual error — valentjn/vscode-ltex#349
• 🐛 Bug fix: Fix error when checking L^AT_EX documents ending with specific commands — valentjn/vscode-ltex#341
• ✨ New: Fix name of Portuguese babel language names, add support for Brazilian Portuguese babel language names — valentjn/ltex-ls#72

12.2.0 (June 5, 2021)

• ✨ New: Add support for \setplength (L^AT_EX)
• ✨ New: Add --log-file option to tee server/client communication and server log to a file
• 🐛 Bug fix: Fix LT_EX LS not terminating if input stream is end-of-file — valentjn/vscode-ltex#325
• 🔧 Change: Bundle Java for platform-dependent, standalone archives — valentjn/ltex-ls#70

12.1.0 (May 1, 2021)

• ✨ New: Add support for cancellation of checking requests — valentjn/vscode-ltex#253
• 🔧 Change: Show Use ... quick fixes before other quick fixes — valentjn/vscode-ltex#297
• 🔧 Change: Limit number of Use ... quick fixes to 5 — valentjn/vscode-ltex#297
• ✨ New: Add isChecking and documentUriBeingChecked fields to result of _ltex.getServerStatus
• ✨ New: Add support for \phantom, \hphantom, and \vphantom (L^AT_EX)
• 🐛 Bug fix: Fix wrong underlining of words starting with markup — valentjn/ltex-ls#69

12.0.0 (April 18, 2021)

• 🔧 Change: Prefix all command names with an underscore to mark them as internal (for hiding them from the user in some clients)
• 🔧 Change: Rename ltex.addToDictionary → _ltex.addToDictionary
• 🔧 Change: Rename ltex.disableRules → _ltex.disableRules
• 🔧 Change: Rename ltex.hideFalsePositives → _ltex.hideFalsePositives
• 🔧 Change: Rename ltex.checkDocument → _ltex.checkDocument
• 🔧 Change: Rename ltex.getServerStatus → _ltex.getServerStatus
• ✨ New: Add support for Org; use the code language ID org — valentjn/vscode-ltex#277
• ✨ New: Add basic support for reStructuredText; use the code language ID restructuredtext — valentjn/vscode-ltex#32
• ✨ New: Add --server-type=tcpSocket option to communicate over a TCP socket
• ✨ New: Add --host and --port options to control host and port of the TCP socket
• ✨ New: Add --[no-]endless option to keep the server alive when the client terminates the connection
• ✨ New: Add -h and --help options to show help message
• ✨ New: Add -V option as alias for --version
• 🗑 Removal: Remove support of single CR characters as line endings
• 🐛 Bug fix: Fix .Rnw not recognized for R Sweave documents when running _ltex.checkDocument
• 🐛 Bug fix: Fix newlines accepted as whitespace in magic comments
• 🔧 Change: Use picocli for parsing of command-line arguments

11.0.0 (April 5, 2021)

• 🔧 Change: Update LanguageTool to 5.3 (see LT 5.3 release notes)
• 🔧 Change: Update LSP4J to 0.12.0
• ✨ New: Enhance support of accents in L^AT_EX by using Unicode combining diacritical marks, normalized via Unicode Normalization Form C — valentjn/vscode-ltex#269
• ✨ New: Add support for many accents in L^AT_EX: double acute (e.g., \H{O}, Ő), line below (e.g., \b{h}, ẖ), dot below (e.g., \d{A}, Ạ), ogonek (e.g., \k{A}, Ą), breve (e.g., \u{A}, Ă), and caron (e.g., \v{C}, Č) — valentjn/ltex-ls#56, valentjn/ltex-ls#57, @ed359
• ✨ New: Add support for special characters in L^AT_EX: \L (Ł), \SS (ẞ), \i (ı), \j (ȷ), and \l (ł) — valentjn/ltex-ls#56, valentjn/ltex-ls#57, @ed359
• ✨ New: Add FR_SPELLING_RULE as a rule for unknown words — valentjn/ltex-ls#47, Nicolas Sicard (@biozic)
• 🔧 Change: Use L^AT_EX parser for documents with code language ID tex — valentjn/ltex-ls#53, valentjn/ltex-ls#54, Lucas Alber (@LDAP)
• ✨ New: Add support for Markdown Extra definition lists — valentjn/vscode-ltex#268
• 🔧 Change: Ignore non-object values for InitializeParams.initializationOptions — valentjn/ltex-ls#65

10.0.0 (February 12, 2021)

• 🗑 Removal: Remove support for settings that are deprecated since 8.0.0: ltex.ignoreInRuleSentence, ltex.commands.ignore, ltex.commands.dummy, ltex.environments.ignore, ltex.markdown.ignore, and ltex.markdown.dummy
• 🔧 Change: Replace ltex/serverStatus request with ltex.getServerStatus command
• ✨ New: Add support for magic comments inside HTML comments in Markdown (<!-- ltex: SETTINGS -->)
• 🔧 Change: Check frame title in argument of L^AT_EX Beamer frames — valentjn/vscode-ltex#239
• ✨ New: Add range argument to ltex.checkDocument
• ✨ New: Check documents even if their code language is not supported
• 🐛 Bug fix: Fix comment sign before babel commands not recognized — valentjn/vscode-ltex#245
• 🐛 Bug fix: Fix removing items in settings with a hyphen prefix sometimes not working
• 🐛 Bug fix: Fix space not added between two arguments of L^AT_EX commands
• 🐛 Bug fix: Fix manually checking BibT_EX documents not working
• 🐛 Bug fix: Fix words in dictionary containing markup not recognized

9.2.0 (January 29, 2021)

• ✨ New: Add support for Pandoc-style inline math ($...$) and display math ($$...$$ with $$ being at the beginning/end of a Markdown block) to Markdown parser — valentjn/vscode-ltex#210
• 🐛 Bug fix: Fix false positives for words added by Add to dictionary for Slovak rule IDs MUZSKY_ROD_NEZIV_A, ZENSKY_ROD_A, and STREDNY_ROD_A — valentjn/vscode-ltex#221
• 🐛 Bug fix: Fix BibT_EX field seealso not ignored, ignore category and parent — valentjn/vscode-ltex#211
• 🔧 Change: Disable UPPERCASE_SENTENCE_START in BibT_EX files — valentjn/vscode-ltex#211
• 🔧 Change: Move rule ID to the end of diagnostic messages as VS Code truncates the messages if the Problems panel is narrow — valentjn/vscode-ltex#233
• 🐛 Bug fix: Fix regression that messages of possible spelling mistakes are not prepended with the respective unknown words — valentjn/vscode-ltex#161
• 🐛 Bug fix: Fix crash when using \begin or \end without an argument — valentjn/vscode-ltex#236
• 🔧 Change: Change $/progress tokens to include a UUID instead of a counter

9.1.0 (January 24, 2021)

• ✨ New: Add support for BibT_EX files (language code bibtex) — valentjn/vscode-ltex#211
• ✨ New: Add setting ltex.bibtex.fields to control which BibT_EX fields should be checked
• ✨ New: Add support for GitLab Flavored Markdown, especially inline math (e.g., $`E = mc^2`$) — valentjn/vscode-ltex#210
• ✨ New: Add support for Markdown tables as in GitHub Flavored Markdown — valentjn/vscode-ltex#218
• ✨ New: Add support for more commands of the glossaries L^AT_EX package
• 🔧 Change: Enable Add to dictionary quick fix for Slovak rule IDs MUZSKY_ROD_NEZIV_A, ZENSKY_ROD_A, and STREDNY_ROD_A — valentjn/vscode-ltex#221
• 🗑 Removal: Remove superfluous spaces in messages of diagnostics
• 🐛 Bug fix: Fix handling of \r\n (Windows) line terminators in Markdown
• 🔧 Change: Use Flexmark’s YAML Front Matter extension to ignore YAML front matter in Markdown instead of own handling
• 🔧 Change: Print Flexmark AST of Markdown documents to log when ltex.ltex-ls.logLevel is "finest"

9.0.1 (January 13, 2021)

• 🔧 Change: Ignore \pgfmathsetmacro, \setmainfont, and \theoremstyle
• 🐛 Bug fix: Fix accent commands such as \O in math mode resulting in diagnostics — valentjn/vscode-ltex#216

9.0.0 (January 3, 2021)

• 🔧 Change: Make versioning independent of vscode-ltex; LT_EX LS now adheres to Semantic Versioning 2.0.0
• ✨ New: Require support of LSP 3.15
• 🔧 Change: Update LanguageTool to 5.2 (see LT 5.2 release notes)
• ✨ New: Add ltex.additionalRules.enablePickyRules to still be able to detect false friends after the update of LanguageTool (default: false)
• 🔧 Change: Replace ltex/progress with $/progress — valentjn/ltex-ls#34
• ✨ New: Add customCapabilities in InitializeParams.initializationOptions
• 🗑 Removal: Remove unneeded command arguments type and command
• 🔧 Change: Replace \dots with Unicode ellipsis … instead of three dots ... to fix some false positives
• ✨ New: Add documentation

8.1.1 (November 24, 2020)

• 🔧 Change: Migrate from Travis CI to GitHub Actions

8.1.0 (November 15, 2020)

• 🔧 Change: Prepend messages of possible spelling mistakes with the respective unknown words — valentjn/vscode-ltex#161
• ✨ New: Add support for optional arguments of \newtheorem
• 🐛 Bug fix: Fix wrong position of diagnostics when using a recognized L^AT_EX command with a non-recognized set of arguments due to an infinite loop — valentjn/vscode-ltex#167
• 🔧 Change: Update LSP4J to 0.10.0

8.0.0 (November 1, 2020)

• 🔧 Change: Upgrade from Java 8 to Java 11 (see announcement) — valentjn/vscode-ltex#39
• ✨ New: Add workaround to eliminate the need for workspace-specific setting names; ltex.dictionary, ltex.disabledRules, and ltex.enabledRules can now be used in multiple setting scopes (user settings, workspace settings, and workspace folder settings) at the same time without overriding each other; instead, the settings of the different scopes will be properly merged (see documentation)
• 🔧 Change: Rename ltex.workspaceDictionary, ltex.workspaceFolderDictionary → ltex.dictionary
• 🔧 Change: Rename ltex.workspaceDisabledRules, ltex.workspaceFolderDisabledRules → ltex.disabledRules
• 🔧 Change: Rename ltex.workspaceEnabledRules, ltex.workspaceFolderEnabledRules → ltex.enabledRules
• 🔧 Change: Rename ltex.ignoreInRuleSentence → ltex.hiddenFalsePositives
• 🔧 Change: Rename ltex.commands.ignore, ltex.commands.dummy → ltex.latex.commands
• 🔧 Change: Rename ltex.environments.ignore → ltex.latex.environments
• 🔧 Change: Rename ltex.markdown.ignore, ltex.markdown.dummy → ltex.markdown.nodes
• 🔧 Change: Change format of ltex.latex.commands, ltex.latex.environments, ltex.markdown.nodes to be objects (with key = command and value = action, e.g., "ignore", "dummy", etc.) instead of arrays
• 🔧 Change: Rename addToDictionary → dictionary in ltex.configurationTarget
• 🔧 Change: Rename disableRule → disabledRules in ltex.configurationTarget
• 🔧 Change: Rename ignoreRuleInSentence → hiddenFalsePositives in ltex.configurationTarget
• ✨ New: Add userExternalFile, workspaceExternalFile, and workspaceFolderExternalFile enumeration values to ltex.configurationTarget, which enables saving settings to external files (see documentation) — valentjn/vscode-ltex#144, valentjn/vscode-ltex#145
• 🔧 Change: Change default of ltex.configurationTarget for dictionary, disabledRules, and hiddenFalsePositives to workspaceFolderExternalFile
• ✨ New: Add ltex.checkFrequency to control when LT_EX checks documents — valentjn/vscode-ltex#142
• ✨ New: Add LTeX: Show Status Information command to show information about the status of LT_EX
• ✨ New: Add support for \usepackage[LANGUAGE]{babel} if in the same file as the text to be checked — valentjn/vscode-ltex#140
• ✨ New: Add support for more BibL^AT_EX commands such as \autocite, \citeauthor, etc. — valentjn/vscode-ltex#143
• ✨ New: Add support for overriding hard-coded command signatures — valentjn/ltex-ls#27
• 🔧 Change: Move handling of external setting files from ltex-ls to vscode-ltex
• 🔧 Change: Increase duration before sentences expire in the result cache to 60 minutes
• 🐛 Bug fix: Fix many settings changes cleared sentence cache, which led to performance issues, e.g., changing the ltex.enabled setting via magic comments — valentjn/vscode-ltex#134
• 🗑 Removal: Remove dependency on org.apache.httpcomponents:httpclient by using the HTTP client that comes with Java 11 when connecting to an HTTP LanguageTool server

7.3.1 (October 12, 2020)

• 🐛 Bug fix: Fix delayed publication of diagnostics by adding workaround to guess the caret position
• 🐛 Bug fix: Fix recheck being triggered when generating list of quick fixes; this should improve speed

7.3.0 (October 10, 2020)

• ✨ New: Add support for \ell as well as \mathcal, \mathfrak, etc. to vowel detection — valentjn/vscode-ltex#131
• ✨ New: Add setting ltex.ltex-ls.logLevel to control the verbosity of the server log
• 🐛 Bug fix: Fix diagnostics sometimes not lined up with the text with switching back from incremental to full document updates; unfortunately, this disables the delayed publication of diagnostics at the caret position
• 🔧 Change: Restructure and simplify internal quick fix and command structure, removing the need for pseudo-telemetry notifications

7.2.0 (September 27, 2020)

• 🔧 Change: Update LanguageTool to 5.1 (see LT 5.1 release notes)
• ✨ New: Add support for HTML entities such as ä and © in Markdown
• 🐛 Bug fix: Fix missing tilde expansion for external dictionary files
• 🔧 Change: Improve logging

7.1.2 (September 22, 2020)

• 🐛 Bug fix: Fix performance issue with multiple languages in one document via magic comments due to LanguageTool being reinitialized on each keystroke — valentjn/vscode-ltex#124

7.1.1 (September 20, 2020)

• 🐛 Bug fix: Fix NullPointerException when supplying relative paths to external dictionary files
• 🐛 Bug fix: Fix German log messages

7.1.0 (September 20, 2020)

• ✨ New: Add support for external dictionary files — valentjn/vscode-ltex#118
• ✨ New: Add support for enabling/disabling LT_EX only for specific file types via ltex.enabled — valentjn/vscode-ltex#19
• ✨ New: Add support for acro commands such as \DeclareAcronym and \ac — valentjn/vscode-ltex#19
• ✨ New: Add support for \addcontentsline — valentjn/vscode-ltex#19
• ✨ New: Add support for \printbibliography and \printglossary without argument
• 🔧 Change: Ignore parenthesis arguments of textblocks — valentjn/vscode-ltex#19
• 🐛 Bug fix: Fix optional argument of heading commands such as \section parsed incorrectly — valentjn/vscode-ltex#123
• 🔧 Change: Include stack traces when logging exceptions

7.0.0 (September 13, 2020)

• 🔧 Change: Change scope of ltex.dictionary, ltex.disabledRules, and ltex.enabledRules to application; these are now user-specific settings that can only be configured in user settings
• ✨ New: Add settings ltex.workspaceDictionary, ltex.workspaceDisabledRules, and ltex.workspaceEnabledRules with window scope to amend the corresponding user-specific settings; these are workspace-specific settings that should be configured in workspace settings
• ✨ New: Add settings ltex.workspaceFolderDictionary, ltex.workspaceFolderDisabledRules, and ltex.workspaceFolderEnabledRules with resource scope to amend the corresponding user-specific and workspace-specific settings; these are workspace-folder-specific settings that should be configured in workspace folder settings
• 🔧 Change: Rename global → user in ltex.configurationTarget
• 🗑 Removal: Remove deprecated settings ltex.javaHome, ltex.performance.initialJavaHeapSize, ltex.performance.maximumJavaHeapSize, ltex.performance.sentenceCacheSize, ltex.*.dictionary, ltex.*.enabledRules, and ltex.*.disabledRules (deprecation since 5.0.0)
• 🔧 Change: Update LanguageTool to 5.0.2 (see LT 5.0.2 release notes)
• 🐛 Bug fix: Fix skipping of YAML front matter — valentjn/vscode-ltex#104

6.3.0 (August 22, 2020)

• ✨ New: Add support for an article when before a formula starting with a vowel (e.g., an $n$-dimensional problem) — valentjn/vscode-ltex#92
• ✨ New: Add support for ~/ and ~\ in settings — valentjn/vscode-ltex#99

6.2.0 (August 7, 2020)

• ✨ New: Add commands LTeX: Check Current Document and LTeX: Check All Documents in Workspace — valentjn/vscode-ltex#84
• ✨ New: Add setting ltex.clearDiagnosticsWhenClosingFile
• 🔧 Change: Skip front matter in Markdown
• 🔧 Change: Ignore more L^AT_EX preamble commands (e.g., \automark, \color, \DeclareSIUnit, \directlua, \setuptoc)
• ✨ New: Add support for German babel hyphenation commands "-, "", "|, "=, "~
• 🔧 Change: Use non-breaking space for ~

6.1.1 (July 26, 2020)

• 🐛 Bug fix: Fix another problem with spaces in paths on Windows — valentjn/vscode-ltex#80

6.1.0 (July 26, 2020)

• ✨ New: LT_EX LS support for Java 8 will end on November 1, 2020 (see documentation) — valentjn/vscode-ltex#39
• ✨ New: Add support for babel commands (see documentation) — valentjn/vscode-ltex#81
• 🐛 Bug fix: Fix problems with spaces in paths on Windows — valentjn/vscode-ltex#80

6.0.2 (July 11, 2020)

• 🔧 Change: Make Windows startup script (ltex-ls.bat) honor JAVA_HOME — valentjn/vscode-ltex#75

6.0.1 (July 2, 2020)

• 🐛 Bug fix: Fix freezes when checking German text by working around languagetool-org/languagetool#3181 introduced by LanguageTool 5.0 — valentjn/vscode-ltex#68

6.0.0 (June 28, 2020)

• 🔧 Change: Update LanguageTool to 5.0 (see LT 5.0 release notes)
• 🔧 Change: Delay diagnostics at the current caret position (e.g., incomplete word or sentence) until the user has finished typing — valentjn/vscode-ltex#46
• ✨ New: Add enabled to magic comments — valentjn/vscode-ltex#67
• 🐛 Bug fix: Fix \todo couldn’t be ignored — valentjn/vscode-ltex#63
• 🐛 Bug fix: Fix wrong language-dependent settings used for magic comments
• 🐛 Bug fix: Fix add to dictionary and disable rule quick fixes using wrong language when used with magic comments
• 🐛 Bug fix: Improve code quality by fixing hundreds of Checkstyle, SpotBugs, and Checker Framework warnings
• 🔧 Change: Migrate from Gradle to Maven
• 🔧 Change: Update Maven dependencies

5.0.0 (June 1, 2020)

• ✨ New: Include all languages in LT_EX LS; this removes the need for language support extensions — valentjn/vscode-ltex#6
• 🔧 Change: Adhere to semantic versioning. This means that the version of LT_EX LS is not tied to the version of LanguageTool anymore, as the version of LanguageTool is not a semantic version. LT_EX LS 5.0.0 uses LanguageTool 4.9.
• 🔧 Change: Rename ltex.<LANGUAGE>.dictionary → ltex.dictionary (object with <LANGUAGE> keys)
• 🔧 Change: Rename ltex.<LANGUAGE>.disabledRules → ltex.disabledRules (object with <LANGUAGE> keys)
• 🔧 Change: Rename ltex.<LANGUAGE>.enabledRules → ltex.enabledRules (object with <LANGUAGE> keys)
• 🔧 Change: Rename ltex.javaHome → ltex.java.path
• 🔧 Change: Rename ltex.performance.initialJavaHeapSize → ltex.java.initialHeapSize
• 🔧 Change: Rename ltex.performance.maximumJavaHeapSize → ltex.java.maximumHeapSize
• 🔧 Change: Rename ltex.performance.sentenceCacheSize → ltex.sentenceCacheSize
• ✨ New: Add support for external LanguageTool HTTP servers — valentjn/vscode-ltex#36
• ✨ New: Add support for magic comments, enables changing the language in the middle of documents — valentjn/vscode-ltex#21
• 🐛 Bug fix: Check \footnote and \todo contents separately, preventing “double period” warnings — valentjn/vscode-ltex#42
• ✨ New: Add support for more BibL^AT_EX citation commands, add support for plural dummies, add support for \eg, \egc, \ie, \iec — valentjn/vscode-ltex#43
• ✨ New: Add visual feedback in status bar during startup and checks that take a long time
• 🗑 Removal: Remove null types and default values from settings, use empty string/array/object instead — valentjn/vscode-ltex#41
• 🔧 Change: Use proper server/client model for language server/client
• 🔧 Change: Make documentation of vscode-ltex more extensive, put it on own website

4.9.3 (May 7, 2020)

• 🔧 Change: Revert to Java 8
• 🗑 Removal: Remove support for external LanguageTool HTTP servers

4.9.2 (May 6, 2020)

• 🔧 Change: Update required version of Java (now 11 or newer)
• ✨ New: Add support for external LanguageTool HTTP servers — valentjn/vscode-ltex#36
• ✨ New: Add support for \autoref, \pageref, \autopageref — valentjn/vscode-ltex#37

4.9.1 (May 1, 2020)

• 🐛 Bug fix: Fix sentence cache was invalidated when a single ignore sentence rule was present — valentjn/vscode-ltex#29
• 🔧 Change: Use thin non-breaking space for \, — valentjn/vscode-ltex#35

4.9.0 (March 28, 2020)

• 🔧 Change: Update LanguageTool to 4.9 (see LT 4.9 release notes)
• 🔧 Change: Update other Java dependencies
• 🔧 Change: Reduce file size (omitting unneeded dependencies)

4.7.10 (March 12, 2020)

• 🐛 Bug fix: Fix spelling errors for French dummies — valentjn/vscode-ltex#27
• 🐛 Bug fix: Fix \dots in math mode being interpreted as ...

4.7.9 (February 29, 2020)

• 🔧 Change: Update Markdown parser Flexmark to 0.60.2; this increases the speed of parsing Markdown
• ✨ New: Add possibility to ignore Markdown elements or replace them by dummy words via ltex.markdown.ignore and ltex.markdown.dummy — valentjn/vscode-ltex#26
• 🔧 Change: Ignore Markdown code blocks by default
• 🔧 Change: Replace auto-links and inline Markdown code with dummy words by default
• 🐛 Bug fix: Fix match positions were sometimes off by one, especially in Markdown documents
• 🔧 Change: Rewrite MarkdownAnnotatedTextBuilder

4.7.8 (February 16, 2020)

• ✨ New: Add support for R Sweave .rnw files — valentjn/vscode-ltex#22
• 🔧 Change: Enable fixing multiple diagnostics at once — valentjn/vscode-ltex#23
• ✨ New: Add support for \euro — valentjn/vscode-ltex#25

4.7.7 (November 23, 2019)

• 🔧 Change: No changes, dummy release

4.7.6 (November 10, 2019)

• ✨ New: Add ltex.performance settings to give users more control over Java’s RAM usage
• 🔧 Change: Change default initial Java heap size to 64 MB
• 🔧 Change: Change default maximum Java heap size to 512 MB
• 🔧 Change: Change default sentence cache size from 10000 to 2000 sentences

4.7.5 (October 22, 2019)

• 🔧 Change: Enable ignoring environments such as lstlisting and verbatim
• ✨ New: Add ltex.environments.ignore setting for defining own environments to ignore

4.7.4 (October 15, 2019)

• ✨ New: Add disabledRules and enabledRules settings (requires update of language extensions)
• ✨ New: Add disable rule quick fix
• 🐛 Bug fix: Fix a bug where the codeAction request gets stuck in infinite loop
• 🐛 Bug fix: Fix another NullPointerException for word2vec

4.7.3 (October 7, 2019)

• 🐛 Bug fix: Fix null pointer error for word2vec quick fixes — valentjn/vscode-ltex#12

4.7.2 (October 2, 2019)

• ✨ New: Add missing error message if legacy false friends could not be loaded

4.7.1 (October 2, 2019)

• ✨ New: Add ltex.additionalRules.motherTongue setting to enable detection of false friends — valentjn/vscode-ltex#11
• 🔧 Change: Change defaults for ltex.additionalRules settings from "" to null

4.7.0 (October 1, 2019)

• 🔧 Change: Update LanguageTool to 4.7 (see LT 4.7 release notes)
• ✨ New: Support multi-root workspaces, all configuration settings except ltex.enabled are now resource-specific — valentjn/vscode-ltex#7
• 🔧 Change: Save dictionary settings under full language short code (e.g., en-US instead of en). If you already have a dictionary under ltex.en.dictionary and use en-US as language (not en), you have to rename the settings name to ltex.en-US.dictionary (similarly for other languages).
• 🗑 Removal: Remove diagnostics when a file is closed
• 🐛 Bug fix: Prevent insertion of text in TikZ mode
• ✨ New: Add support for more commands such as \newenvironment, \newgeometry, and \pagenumbering

4.6.13 (September 26, 2019)

• 🐛 Bug fix: Fix LT_EX LS not reinitialized after a language extension has been installed (which was missing during initialization)

4.6.12 (September 25, 2019)

• 🐛 Bug fix: Patch LanguageTool’s AnnotatedText with linear interpolation to hopefully fix the fromPos must be less than toPos LT errors for good
• 🐛 Bug fix: Fix \footnote in math mode messed up text mode and math mode
• 🔧 Change: Increase robustness in case locale or settings are not provided
• 🔧 Change: Ignore all brace and bracket arguments after \begin{environment} (tabular, array, etc.)
• ✨ New: Add support for some more commands and environments such as \pagestyle and eqnarray

4.6.11 (September 23, 2019)

• 🐛 Bug fix: Detect and prevent infinite loops in LatexAnnotatedTextBuilder
• 🐛 Bug fix: Fix infinite loop with other line endings than \n
• 🐛 Bug fix: Fix some more fromPos must be less than toPos LT errors
• 🔧 Change: Check for interrupts to avoid 100% CPU usage on timeout (this doesn’t fix any bugs though)
• ✨ New: Add support for \email, \href, and \verb|...|
• ✨ New: Add support for more citation commands (\citep, \citet, etc.)
• ✨ New: Add support for float/theorem definition commands and starred sectioning commands

4.6.10 (September 18, 2019)

• 🐛 Bug fix: Fix NullPointerException if LanguageTool has not been initialized — valentjn/ltex-ls#1

4.6.9 (September 8, 2019)

• 🐛 Bug fix: Fix NullPointerException in main

4.6.8 (September 7, 2019)

• ✨ New: Initial release