Bug 74338 - Consider including JS port of LanguageTool in the future
Summary: Consider including JS port of LanguageTool in the future
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
(earliest affected)
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-02-01 19:33 UTC by Alexander Wilms
Modified: 2015-04-01 14:52 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Wilms 2014-02-01 19:33:18 UTC
Lightproof only covers a few languages and I heard it's also inferior to LanguageTool, which is not included since it needs Java.

However, there are plans to port LT to Javascript (http://wiki.languagetool.org/missing-features#toc2 and http://stackoverflow.com/questions/19902556/llvm-cannot-get-vmjc-to-work [asked by the LT author])

It'd be nice to have that functionality by default
Comment 1 Owen Genat (retired) 2014-07-18 08:43:34 UTC
Anything that reduces the Java-dependency of LO is worth pursuing IMO. Having said that I am not clear what the statement on the wiki page about extensions means in terms of LT development:


> Supported programming languages are Basic, Python, JavaScript and Java. 
> For the higher level of integrity and possibilities you can use C++, 
> Python and Java languages to develop UNO complements based extensions.

Is LT a "UNO complements based extension"? Status set to NEEDINFO. Please set back to UNCONFIRMED once this information is provided.
Comment 2 QA Administrators 2015-02-19 04:42:20 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

Message generated on: 2015-02-18
Comment 3 QA Administrators 2015-04-01 14:52:24 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team This NEEDINFO Message was generated on: 2015-04-01

Warm Regards,
QA Team