Rename to LTeX+

.github/label-commenter-config.yml

@@ -8,13 +8,13 @@ labels:
   - name: "3-fixed"
     labeled:
       issue:
-        body: "This issue is now fixed on `develop`. The fix will be included in the next release of LT<sub>E</sub>X.\n\nIf you don't want to wait, you can [try out the nightly pre-release](https://valentjn.github.io/ltex/ltex-ls/contributing.html#how-to-test-pre-releases) tomorrow. Nightly pre-releases are published every morning at around 4am UTC."
+        body: "This issue is now fixed on `develop`. The fix will be included in the next release of LT<sub>E</sub>X.\n\nIf you don't want to wait, you can [try out the nightly pre-release](https://ltex-plus.github.io/ltex-plus/ltex-ls-plus/contributing.html#how-to-test-pre-releases) tomorrow. Nightly pre-releases are published every morning at around 4am UTC."
         action: "close"
 
   - name: "3-invalid"
     labeled:
       issue:
-        body: "Hi! Per the [maintainer guidelines](https://github.com/valentjn/vscode-ltex/blob/develop/MAINTAINING.md#guidelines-about-issues), this issue is automatically closed because it is invalid. The most common reason is that it does not follow the issue template, or it misses vital information from the template. Please see the documentation to learn how to properly report [bugs](https://valentjn.github.io/ltex/ltex-ls/contributing.html#how-to-report-bugs) or [feature requests](https://valentjn.github.io/ltex/ltex-ls/contributing.html#how-to-request-features). Edit the issue description to follow the template or to include the missing information. Thank you!"
+        body: "Hi! Per the [maintainer guidelines](https://github.com/valentjn/vscode-ltex/blob/develop/MAINTAINING.md#guidelines-about-issues), this issue is automatically closed because it is invalid. The most common reason is that it does not follow the issue template, or it misses vital information from the template. Please see the documentation to learn how to properly report [bugs](https://ltex-plus.github.io/ltex-plus/ltex-ls-plus/contributing.html#how-to-report-bugs) or [feature requests](https://ltex-plus.github.io/ltex-plus/ltex-ls-plus/contributing.html#how-to-request-features). Edit the issue description to follow the template or to include the missing information. Thank you!"
         action: "close"
     unlabeled:
       issue:

.github/workflows/ci.yml

@@ -207,4 +207,4 @@ jobs:
           token: "${{ secrets.LTEX_LS_CREATE_GITHUB_RELEASE_TOKEN }}"
           prerelease: "${{ env.LTEX_LS_IS_PRERELEASE }}"
           body: "${{ env.LTEX_LS_CHANGELOG }}"
-          files: "target/ltex-ls-${{ env.LTEX_LS_VERSION }}.tar.gz\ntarget/ltex-ls-${{ env.LTEX_LS_VERSION }}-linux-x64.tar.gz\ntarget/ltex-ls-${{ env.LTEX_LS_VERSION }}-mac-x64.tar.gz\ntarget/ltex-ls-${{ env.LTEX_LS_VERSION }}-windows-x64.zip"
+          files: "target/ltex-ls-plus-${{ env.LTEX_LS_VERSION }}.tar.gz\ntarget/ltex-ls-plus-${{ env.LTEX_LS_VERSION }}-linux-x64.tar.gz\ntarget/ltex-ls-plus-${{ env.LTEX_LS_VERSION }}-mac-x64.tar.gz\ntarget/ltex-ls-plus-${{ env.LTEX_LS_VERSION }}-windows-x64.zip"

CONTRIBUTING.md

@@ -38,7 +38,7 @@ If you like LT<sub>E</sub>X, but are not able to contribute in any of these ways
 ### Known Issues and Limitations
 
 - The LaTeX parser is not perfect. False positives are sometimes reported as errors. However, it is impossible to fully parse LaTeX's output without compiling the source. This follows from the [Turing-completeness of TeX](https://en.wikipedia.org/w/index.php?title=TeX&oldid=979062806#Typesetting_system) and the [halting problem](https://en.wikipedia.org/w/index.php?title=Halting_problem&oldid=979261081).
-- Initial checking might take a while (up to two minutes), depending on the length of the document. [This is a limitation of LanguageTool.](https://valentjn.github.io/ltex/faq.html#why-does-ltex-have-such-a-high-cpu-load)
+- Initial checking might take a while (up to two minutes), depending on the length of the document. [This is a limitation of LanguageTool.](https://ltex-plus.github.io/ltex-plus/faq.html#why-does-ltex-have-such-a-high-cpu-load)
 
 ## How to Request Features
 
@@ -51,7 +51,7 @@ If you like LT<sub>E</sub>X, but are not able to contribute in any of these ways
 
 ## How to Set Up the Project
 
-[As explained in the FAQ](https://valentjn.github.io/ltex/faq.html#whats-the-difference-between-vscode-ltex-ltex-ls-and-languagetool), LT<sub>E</sub>X consists of two components: [vscode-ltex](https://github.com/valentjn/vscode-ltex) and [ltex-ls](https://github.com/valentjn/ltex-ls). This guide is only about the ltex-ls part. If you want to change vscode-ltex as well, [be sure to read and follow the contribution guidelines of ltex-ls](https://valentjn.github.io/ltex/vscode-ltex/contributing.html).
+[As explained in the FAQ](https://ltex-plus.github.io/ltex-plus/faq.html#whats-the-difference-between-vscode-ltex-ltex-ls-and-languagetool), LT<sub>E</sub>X consists of two components: [vscode-ltex](https://github.com/valentjn/vscode-ltex) and [ltex-ls](https://github.com/valentjn/ltex-ls). This guide is only about the ltex-ls part. If you want to change vscode-ltex as well, [be sure to read and follow the contribution guidelines of ltex-ls](https://ltex-plus.github.io/ltex-plus/vscode-ltex/contributing.html).
 
 1. Install VS Code, Git, and Apache Maven.
 2. Fork ltex-ls on GitHub.
@@ -96,10 +96,10 @@ You can improve the [documentation](https://valentjn.github.io/ltex):
 
 | Page | Sources |
 | ---- | ------- |
-| [Settings](https://valentjn.github.io/ltex/settings.html) | [`package.json`](https://github.com/valentjn/vscode-ltex/blob/develop/package.json), [`package.nls.json`](https://github.com/valentjn/vscode-ltex/blob/develop/package.nls.json) |
-| [Code of Conduct](https://valentjn.github.io/ltex/code-of-conduct.html) | [`CODE_OF_CONDUCT.md`](https://github.com/valentjn/vscode-ltex/blob/develop/CODE_OF_CONDUCT.md) |
-| [ltex-ls → Changelog](https://valentjn.github.io/ltex/ltex-ls/changelog.html) | [`ltex-ls/changelog.xml`](https://github.com/valentjn/ltex-ls/blob/develop/changelog.xml) |
-| [ltex-ls → Contributing](https://valentjn.github.io/ltex/ltex-ls/contributing.html) | [`ltex-ls/CONTRIBUTING.md`](https://github.com/valentjn/ltex-ls/blob/develop/CONTRIBUTING.md) |
+| [Settings](https://ltex-plus.github.io/ltex-plus/settings.html) | [`package.json`](https://github.com/valentjn/vscode-ltex/blob/develop/package.json), [`package.nls.json`](https://github.com/valentjn/vscode-ltex/blob/develop/package.nls.json) |
+| [Code of Conduct](https://ltex-plus.github.io/ltex-plus/code-of-conduct.html) | [`CODE_OF_CONDUCT.md`](https://github.com/valentjn/vscode-ltex/blob/develop/CODE_OF_CONDUCT.md) |
+| [ltex-ls → Changelog](https://ltex-plus.github.io/ltex-plus/ltex-ls-plus/changelog.html) | [`ltex-ls/changelog.xml`](https://github.com/valentjn/ltex-ls/blob/develop/changelog.xml) |
+| [ltex-ls → Contributing](https://ltex-plus.github.io/ltex-plus/ltex-ls-plus/contributing.html) | [`ltex-ls/CONTRIBUTING.md`](https://github.com/valentjn/ltex-ls/blob/develop/CONTRIBUTING.md) |
 
 ## How to Translate the User Interface
 

MAINTAINING.md

@@ -18,7 +18,7 @@
   - *Examples:* Missing information is provided, bug occurs again due to a regression, etc.
 - Issue comments that do not contribute to the discussion (e.g., “I'm affected, too” on confirmed bug reports) may be hidden. Instead, reactions (e.g., thumbs-up) should be used to upvote issues.
 - Issues that don't follow the **template** may be closed immediately.
-- Issues may be **locked** if they violate the [code of conduct](https://valentjn.github.io/ltex/code-of-conduct.html).
+- Issues may be **locked** if they violate the [code of conduct](https://ltex-plus.github.io/ltex-plus/code-of-conduct.html).
 
 ## Guidelines About Versioning