Back to LanguageTool Homepage - Privacy - Imprint

LanguageTool for Sublime Text


(Ghaith Tarawneh) #1

Hey everybody,

Am working on a LanguageTool plugin for Sublime Text 2/3. I've got the basic functionality nailed down (I think) but I wanted to get some feedback on usability plus any other thoughts on how you think LanguageTool should be used with Sublime? It would be great if any Sublime users can have a look and let me know what do you think. Thanks!

Plugin package page and source code:

https://packagecontrol.io/packages/LanguageTool

https://github.com/gtarawneh/languagetool-sublime


(Daniel Naber) #2

Thanks, looks promising. What's the license of the plugin?


(Ghaith Tarawneh) #3

I haven't decided yet but I was thinking maybe GPL-2 or later (to keep it in the spirit of LanguageTool).


(Daniel Naber) #4

Actually LT is LGPL, but both are fine.


(Daniel Naber) #5

Could you please add a useragent parameter with a value of sublime to the requests the plugin sends? This way we can create statistics about where the queries to our server come from.

Also, from looking at the code it seems you're using the old LT API (it returns XML). This will be turned off in a few months. Please see https://languagetool.org/http-api/migration.php for migration instructions.


(Ghaith Tarawneh) #6

Sure, will queue both changes for the next release.


(Daniel Naber) #7

Please let me know when you have decided about the license - I'd like to announce your add-on on our social media channel, but I'd prefer to do that once the license has been selected.


(Ghaith Tarawneh) #8

I've just added licensing information - the plugin is now available under GPLv2 or later.


(Daniel Naber) #9

Thanks, I've posted this to twitter and Facebook. One more idea: as you use the public server by default, you might want to link our privacy policy: https://languagetool.org/privacy/. Also, you could show a message on first start, explaining users that their texts will be sent to languagetool.org with the default settings. This is what we do in our Firefox/Chrome add-on.


(Ghaith Tarawneh) #10

Sure - am still trying to sort out migration to the new API but will make these changes soon afterwards.


(Atiqur Sumon) #11

Hi, I am new in this forum I see your Language tool plugin it's working well. I will see everyone like that. My suggest is that keep it going.


(havel Contreras) #12

the keyboard shortcut is being used by colorpicker package, and was not able customize the package in preferences> package settings.