[LanguageTool]: Grammar check

[Doitsu]

Originally Posted by BetterRed

Double click on that Language Tool folder, and it will open. I would think the languagetool.jar file is in there somewhere. When I unpacked the zip it might have created a folder, in a folder, so you might have to drill down a couple of levels.

@BetterRed:
You're right, Gregg Bell'll have to double-click the folder that he unpacked the zip file to. But he'll need to select languagetool-commandline.jar. (All other files are filtered out by the file selection dialog box settings anyway.)
BTW, thanks for the continued tech support! I really appreciate it.

@Gregg Bell: If you have specific questions about the plugin, please:
1. re-read the first topic in the LanguageTool plugin thread, which should answer 99% of your questions,
2. send your questions directly to me.

[Gregg Bell]

Originally Posted by BetterRed

Double click on that Language Tool folder, and it will open. I would think the languagetool.jar file is in there somewhere. When I unpacked the zip it might have created a folder, in a folder, so you might have to drill down a couple of levels.

BR

Thanks Red. I'll check it later tonight when I get on that computer again.

[Gregg Bell]

Originally Posted by Doitsu

@BetterRed:
You're right, Gregg Bell'll have to double-click the folder that he unpacked the zip file to. But he'll need to select languagetool-commandline.jar. (All other files are filtered out by the file selection dialog box settings anyway.)
BTW, thanks for the continued tech support! I really appreciate it.

@Gregg Bell: If you have specific questions about the plugin, please:
1. re-read the first topic in the LanguageTool plugin thread, which should answer 99% of your questions,
2. send your questions directly to me.

Will do, Doitsu. Thanks.

[Gregg Bell]

1) Does it work automatically or do I have to run it (like I run FlightCrew and Epubcheck)?

2) When I went to run it I ran into this. (see screenshots) (I run Xubuntu 16.04 Distro)

[DiapDealer]

Originally Posted by Gregg Bell

2) When I went to run it I ran into this. (see screenshots) (I run Xubuntu 16.04 Distro)

sudo apt-get install python3-tk

The (Ubuntu-equivalent) python modules that ship with the Windows and Mac versions of Sigil are as follows:

• python3-tk
• python3-pyqt5
• python3-lxml
• python3-six
• python3-html5lib
• python3-regex
• python3-pillow
• python3-cssselect
• python3-cssutils
• python3-chardet

Plugin devs will assume that everyone has these python modules available. So Linux users who want to utilize Sigil plugins should make sure the above packages are installed when using Linux repository-supplied versions of Sigil.

Several may be installed already, but you can safely run the following command to insure they are all installed/updated:

sudo apt-get install python3-tk python3-pyqt5 python3-lxml python3-six python3-html5lib python3-regex python3-pillow python3-cssselect python3-cssutils python3-chardet

[Gregg Bell]

Originally Posted by DiapDealer

sudo apt-get install python3-tk

The (Ubuntu-equivalent) python modules that ship with the Windows and Mac versions of Sigil are as follows:

• python3-tk
• python3-pyqt5
• python3-lxml
• python3-six
• python3-html5lib
• python3-regex
• python3-pillow
• python3-cssselect
• python3-cssutils
• python3-chardet

Plugin devs will assume that everyone has these python modules available. So Linux users who want to utilize Sigil plugins should make sure the above packages are installed when using Linux repository-supplied versions of Sigil.

Several may be installed already, but you can safely run the following command to insure they are all installed/updated:

sudo apt-get install python3-tk python3-pyqt5 python3-lxml python3-six python3-html5lib python3-regex python3-pillow python3-cssselect python3-cssutils python3-chardet

Thanks Diap. I ran that python command, but when I ran the Language Tool in Sigil I got this window (that I couldn't take a screenshot of) that was titled:

Select Language Tool Jar File

Then under that it had:

Directory: home/gregory
File name: (and an open box)

And on the bottom it had:

Files of type: Java archive files (languagetool-commandline.jar)

And then when I ran the Language Tool again in Sigil, the screen got snarky, bringing up a partial browser window.

[DiapDealer]

I'll defer to Doitsu for those details. I'm not familiar with the particulars of the plugin; I just recognized the tkinter error. But it sounds like you may need to download the language tool archive (from the System Requirements section of the first post) and tell the plugin where a portion of that archive can be found.

[Doitsu]

@DiapDealer: Thanks for the tech support.

Originally Posted by Gregg Bell

I ran that python command, but when I ran the Language Tool in Sigil I got this window (that I couldn't take a screenshot of) that was titled:

You'll need to download and unzip LanguageTool-3.8.zip.

For example, if you unzip LanguageTool-3.8.zip in the Downloads folder, languagetool-commandline.jar should be located in:

/home/gregory/Downloads/LanguageTool-3.8/languagetool-commandline.jar

(I wouldn't recommend using the Downloads folder, though. I'm just using it as an example.)

When you run the plugin for the first time, you'll need to change the default folder in the file selection dialog box to the folder that you extracted language tool to.
To change the folder either click the button right of the current directory and/or click the up arrow button to display the parent folder.
Once you've selected the correct folder you should see several subfolders and languagetool-commandline.jar. Click languagetool-commandline.jar and Open.

[Gregg Bell]

Originally Posted by DiapDealer

I'll defer to Doitsu for those details. I'm not familiar with the particulars of the plugin; I just recognized the tkinter error. But it sounds like you may need to download the language tool archive (from the System Requirements section of the first post) and tell the plugin where a portion of that archive can be found.

Okay. Thanks Diap.

[Gregg Bell]

Originally Posted by Doitsu

@DiapDealer: Thanks for the tech support.



You'll need to download and unzip LanguageTool-3.8.zip.

For example, if you unzip LanguageTool-3.8.zip in the Downloads folder, languagetool-commandline.jar should be located in:

/home/gregory/Downloads/LanguageTool-3.8/languagetool-commandline.jar

(I wouldn't recommend using the Downloads folder, though. I'm just using it as an example.)

When you run the plugin for the first time, you'll need to change the default folder in the file selection dialog box to the folder that you extracted language tool to.
To change the folder either click the button right of the current directory and/or click the up arrow button to display the parent folder.
Once you've selected the correct folder you should see several subfolders and languagetool-commandline.jar. Click languagetool-commandline.jar and Open.

Thanks Doitsu. I got it. (Nice instructions!) Only thing is when I ran it on a couple of epubs I got 'no errors.' Then I added your test line (I can has cheeseburgers?) and it brought that up as an error and a bunch of other errors as well. Would it probably be a good idea to add that cheeseburger test line whenever I run it?

[Doitsu]

Originally Posted by Gregg Bell

Only thing is when I ran it on a couple of epubs I got 'no errors.'

LanguageTool is not as thorough as many commercial grammar checkers and can only find certain types of errors. I.e., you shouldn't rely on it.

Originally Posted by Gregg Bell

Would it probably be a good idea to add that cheeseburger test line whenever I run it?

No. If it reported the errors once, it'll also do so in the future.

[Gregg Bell]

Originally Posted by Doitsu

LanguageTool is not as thorough as many commercial grammar checkers and can only find certain types of errors. I.e., you shouldn't rely on it.


No. If it reported the errors once, it'll also do so in the future.

Thanks Doitsu, but I didn't make myself clear. When I ran the language tool in an epub, it said it had no errors. Then I added the cheeseburger line to the epub and ran the language tool again, and the language tool identified the 'cheeseburger' error and six or seven additional errors.

That's why I was asking if I should add the cheeseburger sentence if the initial language tool run turned up no errors.

[Doitsu]

Originally Posted by Gregg Bell

Thanks Doitsu, but I didn't make myself clear. When I ran the language tool in an epub, it said it had no errors. Then I added the cheeseburger line to the epub and ran the language tool again, and the language tool identified the 'cheeseburger' error and six or seven additional errors.

This shouldn't happen. Can you please post two of the sentences that were flagged by LanguageTool only after you added the cheeseburger test sentence?
(I need the sentence and the type of error that LanguageTool has reported.)

To exclude plugin errors, also please check a paragraph that contains one of the flagged sentences with the online version of LanguageTool.

EDIT: If you paste text from other apps, you might have to select Tools > Reformat HTML > Mend and Prettify all HTML files and save the epub before running the LanguageTool plugin.

[Gregg Bell]

Originally Posted by Doitsu

This shouldn't happen. Can you please post two of the sentences that were flagged by LanguageTool only after you added the cheeseburger test sentence?
(I need the sentence and the type of error that LanguageTool has reported.)

To exclude plugin errors, also please check a paragraph that contains one of the flagged sentences with the online version of LanguageTool.

EDIT: If you paste text from other apps, you might have to select Tools > Reformat HTML > Mend and Prettify all HTML files and save the epub before running the LanguageTool plugin.

Hey.

16:14:21 screenshot is after I first ran Language Tool plugin

16:16:52 is after I added 'Cheezeburger' test sentence and ran LT again

128 is after running a paragraph with a flagged sentence (in line 86) in online LT

If you paste text from other apps, you might have to select Tools > Reformat HTML > Mend and Prettify all HTML files and save the epub before running the LanguageTool plugin.

I tested this (doing what's in the above quote) on the same epub I ran the first LT tests on and the results were the same: the first LT run said no errors and then I added the cheeseburger test line and ran it again and it got the same errors as in the 16:16:52 screenshot.

[Doitsu]

By default, the plugin will only check the file that is currently selected in the Book Browser dialog box. That's why you got no error message when you clicked cover.xhtml and ran the plugin.
If you want to check all files, either select all .xhtml files in the Book Browser or click the Text folder in the Book Browser before running the plugin. (Clicking the Text folder is the same as selecting no file.)