Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for LanguageTool servers #197

Open
rpls opened this issue Jan 20, 2022 · 3 comments
Open

Support for LanguageTool servers #197

rpls opened this issue Jan 20, 2022 · 3 comments

Comments

@rpls
Copy link

rpls commented Jan 20, 2022

I can't find any option in textidote, or even if the current software architecture would allow for it, but support for LanguageTool Servers would be nice. LanguageTool apparently has some features that aren't included in the open-source version, but in their hosted service (or their paid on-site versions). Another simpler option would be to use textidote as a more intelligent TeX-Stripper (i.e., just to filter out TeX commands etc.) and push the result into ones own spellchecking solution (e.g., curl it with a script to a language tool server).

@sylvainhalle
Copy link
Owner

I prefer the second option (piping the output to the analysis tool of your choice) to the first one.

In this respect, part of what you suggest is already there: the --clean command-line option outputs a text stripped of its LaTeX markup. However, by doing this you won't be able to show whatever errors the checker gives you back into the original source file, as all locations within the file will be relative to the clear text.

This is the part that is missing: a way for TeXtidote to receive messages attached to locations in a file it has previously cleaned, and to produce a report where these messages are re-positioned at their corresponding locations in the source.

@MarkKoz
Copy link

MarkKoz commented Mar 17, 2022

I'd like this feature as well. It seems it's a matter of being able to pass a GlobalConfig to MultiThreadedJLanguageTool. Would it be possible to leverage textidote's existing config and CLI systems to forward the server options to such object?

Yes we can clean with textidote and manually invoke LanguageTool, but I prefer textidote's HTML reports.

This is the part that is missing: a way for TeXtidote to receive messages attached to locations in a file it has previously cleaned, and to produce a report where these messages are re-positioned at their corresponding locations in the source.

This is the ideal long-term, generic solution. But in the short term I do think it's reasonable to have better configuration for LanguageTool (at least being able to specify server info).

@hakova
Copy link

hakova commented Dec 25, 2023

Plus 1 for the ability to use a remote LanguageTool service. I would like to self-host my LanguageTool server, and be able to use it from my desktop and laptop, rather than installing everything on every PC I use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants