Marcin wrote:
Why do you want to ignore the default disambiguation rules? I understand 
why you don't want to have the default grammar rules but the more you 
disambiguate, the less false alarms altogether...?

Reason 1. When I started to write the STE rules, I thought that the simplest
option for me was to use a 'blank sheet'. Initially, the STE rules did not
have part-of-speech disambiguation. I could probably add the STE
disambiguation rules to the LT disambiguation rules. (Obviously, I need to
do some tests to make sure that all the STE rules operate correctly with the
LT rules.)

Reason 2. I am not sure about the legal implications of using LT and parts
of LT in a product that I sell. My business model is to use LT as a
framework. The STE issue 3 rules are free. I want to sell rules for other
issues of STE. If the rules are completely separate, I know that I will not
infringe copyright (because I sell only XML rule files that I wrote.)

Marcin wrote:
As Daniel noted, it might be tricky to turn it on and off. The only way 
I see is to offer STE as a separate module when we modularise the extension.

That would be great! I am happy to donate all the STE issue 3 rules.

But, users need a way to customize the disambiguation rules, and optionally,
the grammar rules. In addition to the core STE terms, the disambiguation
rules contain approved project terms and not-approved project terms. Because
some project terms are approved only for some contexts, the grammar rules
find the unknown terms, the not-approved terms, and the approved terms that
are used incorrectly.

Daniel wrote:
But with your approach, you have to provide your own modified download 
anyway, don't you?

Yes, initially I did that. I put the STE grammar file and STE disambiguation
file into the stand-alone version of LT. That bundle was on the
simplified-english website. Recently, I changed the download method. First,
I tell people to install the stand-alone version of LT. Next, over-write the
LT grammar and disambiguation files with the STE files. I changed the method
for 2 reasons:
1. The new method makes people aware that the rules for STE are separate to
LT.
2. I do not have to synchronize releases of the STE rules with the quarterly
releases of LT. (I need only to make sure that the rules operate correctly
with the latest release of LT.)

Daniel wrote:
> Is it possible to have a design/structure for OO/LO such that the 
> default LT
> grammar file and the default disambiguation file are optional?
This way a user could use your STE term checker and still switch to the 
standard English rules, while currently he can have your STE checker 
installed, *or* the standard LT, is that correct? 

Yes. Currently, for the stand-alone version of LT, there is only 1
grammar.xml file and only 1 disambiguation.xml file. Thus, at any time, a
user can have either the STE rules or the default rules. (To overcome that
problem, as an alternative to changing filenames, I have 2 installations of
the stand-alone version of LT.)

(Wasn't there a discussion about using LT to make sure that text conforms to
a particular style guide, such as the Economist style guide? To do that,
don't you need a way to select the grammar file that contains the rules?)

Daniel wrote:
The STE term checker 
should already work in LO/OO if you modify the grammar.xml to contain 
only your rules.

How do I modify the grammar.xml to contain only the STE rules? In the OO
installation directory, I cannot find grammar.xml. In OpenOffice Writer,
from Tools>LanguageTool, I cannot see an option to specify a grammar file.

I thought that for the LO/OO version of LT, to change the grammar.xml file,
I must check out LT from github
(http://www.languagetool.org/development/#checkout) and then make a new
version of LT that has the STE rules.

Regards,

Mike Unwalla
Contact: www.techscribe.co.uk/techw/contact.htm 






------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Languagetool-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/languagetool-devel

Reply via email to