-
Notifications
You must be signed in to change notification settings - Fork 69
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
Comments
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 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. |
I'd like this feature as well. It seems it's a matter of being able to pass a Yes we can clean with textidote and manually invoke LanguageTool, but I prefer textidote's HTML reports.
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). |
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. |
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 usetextidote
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).The text was updated successfully, but these errors were encountered: