I’ve recently discovered LanguageTool, great product and execution!
I’m trying to see what I can do to get the macOS app to use my local self-hosted server instead of the default public one.
Note that I know how to do this in the Safari extension, but ultimately I’d like to configure this system-wide to make sure that not even when I use the editor or the future Apple apps integration (now in beta) my text is being sent to the languagetool.org API.
How can this be done? If it cannot be done, can we add support for it?
Likewise, do we have a way to configure Google LanguageTool to work with a local self-hosted server?
Since you mentioned this is not possible for the non-beta app, may I ask if it is feasible in any way for the beta one? I have it installed from Grammar Checker for macOS - LanguageTool and there is no option to specify own server URL. Would appreciate the advice, thanks.
I’m going to throw this out there. I’m coming from a perspective of having worked on open source teams at a couple of organizations.
I completely understand the need to make Language Tool a viable commercial success.
As an end user, I’d be more than willing to pay to “unlock” the Mac app such that I could use my self-hosted, and open source, language-tool server; I’m fully willing to accept the operational support burden doing so would cause.
I came here looking for the same answer. This article here explains what permissions are needed for languagetool to operate, but it addresses the official desktop app only. I have the self-hosted languagetool installed with Homebrew on a MacBook Pro M1 running macOS Sonoma. I’m guessing that I need to grant the primary languagetool executable the permissions it needs, but do languagetool-gui and languagetool-server require it, as well?
BTW: @jvican , @dnaber & others cominf here for the same purpose: Homebrew self-hosted languagetool is showing up for all of my apps if they have a plugin. Like you, I am looking to get it to work with Desktop tools without a plugin. I think that, as a security measure, the same may be required for macOS itself. That way, languagetool itself isn’t installed with massive permissions it may not require; the addon app could limit the permissions to a scope needed only for correct function of the tool and nothing more.
Ultimately, I’m looking for self-hosted languagetool to be availble to macOS system-wide, as discussed here regarding LT for Desktop.