RE: LanguageTool for Chrome

Hi Daniel, Works fine now. Thanks. Mike -Original Message- From: Daniel Naber [mailto:daniel.na...@languagetool.org] Sent: 02 November 2015 11:28 To: development discussion for LanguageTool Subject: RE: LanguageTool for Chrome On 2015-11-02 11:25, Mike Unwalla wrote: > 247 MB, 225

RE: LanguageTool for Chrome

247 MB, 225 MB, 49 MB Regards, Mike Unwalla Contact: www.techscribe.co.uk/techw/contact.htm -Original Message- From: Daniel Naber [mailto:daniel.na...@languagetool.org] Sent: 01 November 2015 10:31 To: development discussion for LanguageTool Subject: RE: LanguageTool for Chrome

RE: LanguageTool for Chrome

ted to the Automatic Dictionary Switcher (problem occurs if the Automatic Dictionary Switcher is not installed). Regards, Mike -Original Message- From: Daniel Naber [mailto:daniel.na...@languagetool.org] Sent: 01 November 2015 11:59 To: development discussion for LanguageTool Subject: RE: LanguageT

RE: LanguageTool for Chrome

On 2015-11-02 11:25, Mike Unwalla wrote: > 247 MB, 225 MB, 49 MB Seems your Java assumes a limit of 255MB, which is sometimes not enough. I think the reason might be either you're still using a 32 bit machine or you're using a 32 bit Java. You can start LT from the command line like this to

RE: LanguageTool for Chrome

On 2015-11-02 11:25, Mike Unwalla wrote: Hi Mike, thanks for your feedback. > The analysis of the language is sometimes not correct. Refer to > dictionary-switcher.png. I know - we have to rely on an existing library that works well but precision decreases for short texts. You can increase

RE: LanguageTool for Chrome

On 2015-10-30 17:49, Mike Unwalla wrote: > Also, the Firefox Automatic Dictionary Switcher version 0.4 does not > operate correctly. Refer to the attachment (greater-than-symbol.png). A new version is available but not yet online on http://addons.mozilla.org. It would be great if you can test

RE: LanguageTool for Chrome

On 2015-10-31 11:36, Mike Unwalla wrote: Hi Mike, > I cannot make Chrome use a local server. This is what I did: thanks for the report. For some reason, LT doesn't seem to have enough memory. If you open the "About" menu in LT stand-alone, what values does it show after "Java max/total/free

RE: LanguageTool for Chrome

On 2015-10-30 17:49, Mike Unwalla wrote: > I tried a few sentences, and LT seems to work OK, except... > > I typed this into Chrome: > > > After I clicked Check Text, LT changed the greater than character to > It's a known issue that's tricky to fix and that I won't work on, as it's

RE: LanguageTool for Chrome

...@gmail.com] Sent: 28 October 2015 10:49 To: development discussion for LanguageTool Subject: Re: LanguageTool for Chrome 2015-10-28 11:42 GMT+01:00 Daniel Naber <daniel.na...@languagetool.org>: On 2015-10-27 19:03, Jaume Ortolà i Font wrote: > It wor

Re: LanguageTool for Chrome

On 2015-10-27 19:03, Jaume Ortolà i Font wrote: > It works for me! > > I just found that entities like or (not visible) are > detected as a spelling errors. Should be fixed now (version 0.8.3): https://chrome.google.com/webstore/detail/languagetool/oldceeleldhonbafppcapldpdifcinji Also,

Re: LanguageTool for Chrome

2015-10-28 11:42 GMT+01:00 Daniel Naber : > On 2015-10-27 19:03, Jaume Ortolà i Font wrote: > > > It works for me! > > > > I just found that entities like or & (not visible) are > > detected as a spelling errors. > > Should be fixed now (version 0.8.3): > > >

Re: LanguageTool for Chrome

On 2015-10-23 18:52, Jaume Ortolà i Font wrote: > The two first issues are solved. The last one not: composing a message > in gmail. In plain text mode, the line breaks disappear. In html mode, > all formatting disappears. There are still cases where replacement will not work, but they should

Re: LanguageTool for Chrome

2015-10-27 18:17 GMT+01:00 Daniel Naber : > On 2015-10-23 18:52, Jaume Ortolà i Font wrote: > > > The two first issues are solved. The last one not: composing a message > > in gmail. In plain text mode, the line breaks disappear. In html mode, > > all formatting

Re: LanguageTool for Chrome

It works for me! I just found that entities like or (not visible) are detected as a spelling errors. Regards, Jaume Ortolà 2015-10-27 18:48 GMT+01:00 Daniel Naber : > On 2015-10-27 18:29, Xavi Ivars wrote: > > > I just did som esmall tests in Gmail, and it

Re: LanguageTool for Chrome

On 2015-10-27 18:29, Xavi Ivars wrote: > I just did som esmall tests in Gmail, and it still broke the layout, > removing all the line breaks. I tested it in gmail and it worked for me. Are you sure you're using the updated version (0.8.2)? Can you send a screen shot of the input text before

Re: LanguageTool for Chrome

> > > Latest dictionary in LO5 comes with version 0.8. However in LT source > > code repository I see the version 0.2. > > So can't we just update the version in LT to improve support a lot, with > little work for us? > I guess so. However, since I was not directly involved in Hunspell

Re: LanguageTool for Chrome

On 2015-10-25 14:44, Juan Martorell wrote: > I guess so. However, since I was not directly involved in Hunspell > integration into LT I want to make sure that the upgrade introduces no > regression. Besides, the extension of the dictionary in LO and in LT > do not match -- I think that needs a

Re: LanguageTool for Chrome

On 2015-10-23 18:52, Jaume Ortolà i Font wrote: > The two first issues are solved. The last one not: composing a message > in gmail. In plain text mode, the line breaks disappear. In html mode, > all formatting disappears. I understand the problem now, but it will take some time to fix. Regards

Re: LanguageTool for Chrome

On 2015-10-24 16:52, Juan Martorell wrote: > Latest dictionary in LO5 comes with version 0.8. However in LT source > code repository I see the version 0.2. So can't we just update the version in LT to improve support a lot, with little work for us? > Extending the Spanish dictionary is an

Re: LanguageTool for Chrome

2015-10-23 16:40 GMT+02:00 Daniel Naber : > On 2015-10-22 11:21, Jaume Ortolà i Font wrote: > > I have tested it and I found some strange behavior when trying to > > replace errors with suggestions. > > thanks for your feedback, a new version (0.8.1) has just been

Re: LanguageTool for Chrome

On 2015-10-22 11:33, Juan Martorell wrote: > Plus, the extension is not configurable, so you're forced to the > default behaviour, which for Spanish is not optimal given the amount > of false spell check errors because of the lack of dictionary words -- > and you cannot add them to your local

Re: LanguageTool for Chrome

On 2015-10-22 11:21, Jaume Ortolà i Font wrote: Hi Jaume, > I have tested it and I found some strange behavior when trying to > replace errors with suggestions. thanks for your feedback, a new version (0.8.1) has just been released, could you test if it fixes the issues? Everybody else,

Re: LanguageTool for Chrome

On 2015-10-19 23:57, Daniel Naber wrote: > there's now an early version of a LT extension for Chrome available: > > https://chrome.google.com/webstore/detail/languagetool/oldceeleldhonbafppcapldpdifcinji?hl=de=DE As there was no feedback, I'm not sure if nobody has tested this or if everybody

Re: LanguageTool for Chrome

Hi Daniel, Good job! I have tested it and I found some strange behavior when trying to replace errors with suggestions. - When the error is the first word of the text, the replacement is not done. Nothing happens. - In a text area, when the text has more than one newline, and I try to make a

Re: LanguageTool for Chrome

On 22 October 2015 at 11:21, Jaume Ortolà i Font wrote: > Hi Daniel, > > Good job! > > I have tested it and I found some strange behavior when trying to replace > errors with suggestions. > > - When the error is the first word of the text, the replacement is not > done.

LanguageTool for Chrome

Hi, there's now an early version of a LT extension for Chrome available: https://chrome.google.com/webstore/detail/languagetool/oldceeleldhonbafppcapldpdifcinji?hl=de=DE Please give it a try and report bugs and ideas. The extension cannot be found yet by searching but only via the link above.