I use OnlyOffice to move away from GAFAM and toward greater sovereignty. In my opinion, one of OnlyOffice’s remaining weaknesses is its spelling correction. My preferred spell checker (my native language is French) is Antidote. Unfortunately, there is no integration available for OnlyOffice.
The documentation for integrating Antidote is provided here: Outils de développement | Antidote.info
Hello @Jojoffice
Just to clarify: do you suggest developing a stand-alone plugin for the editors similar to LanguageTool?
Hi @Constantine, I think the suggestion of @Jojoffice is more to create the integration of antidote in OnlyOffice. You can find a document of this kind of thing through this link Integration | User Guide
Personally, I work in a French research unit and I try to test the use of OnlyOffice with the objective to propose it to my entire unit. Have integration with antidotes (like you have for DeepL and Zotero) could be a very useful tool for us.
Cheers,
Mathieu
Hello @MathieuD
Thank you for the comment. I may assume that you are using Desktop Editors, is that correct?
As far as I know, they also have a browser extension, thus I wanted to know what kind of support users look forward to - an extension or a plugin (similar to DeepL, Zotero, LanguageTool etc.) for internal editor use.
Hi @constantine,
Personally, I use mainly the Desktop Editors, but among several institutes of my research unit, they use the server edition through their cloud services.
Regarding your question on the browser extension, I don’t use it but I’m assuming that this feature could be enough when you use OnlyOffice server edition type.
Below you will find an example of the integration of Antidote in Microsoft Office Word, directly in the software.
From my understanding, this is what @Jojoffice try to ask and myself too. So I think our suggestion of development is more a plugin and this is why @Jojoffice add initialy the link of the Antidote API
Thanks for clarifications. I have submitted your suggestion to the development, please await the feedback.
UPD: the suggestion has been registered in our internal bug tracker under the number 80458. Thank you for the suggestion.
