-
```
The model is always coupled to the language code parameter. There should be
additional parameters to override the model and the model encoding for the case
that somebody wants to specify a custo…
-
```
We should switch all unit tests to OpenNLP, since we then can use the models as
well and the tests run anywhere.
```
Original issue reported on code.google.com by `richard.eckart` on 7 Jun 2012 …
-
```
The TreeTagger module still uses custom mapping loading code. It should use a
MappingProvider and the default mappings from api.lexmorph.
```
Original issue reported on code.google.com by `richa…
-
```
Currently DKPro TreeTagger supports auto-lookup of model files. It looks up and
loads the appropriate language model automatically according to the document
language. All other DKPro analysis engi…
-
```
The analysis engine cannot deal with cases where TreeTagger does not output a
POS and lemma.
```
Original issue reported on code.google.com by `richard.eckart` on 2 Oct 2011 at 3:12
-
```
When setting a model using PARAM_MODEL_PATH, there is an NPE exception:
Caused by: java.lang.NullPointerException
at de.tudarmstadt.ukp.dkpro.core.treetagger.TreeTaggerPosLemmaTT4J$1.produceR…
-
```
I would be nice to optionally secify all neccessary properties, executables and
resources in the parameters of the analysis engine.
Example:
The TreeTagger installation for its wrapper in DKPro …
-
```
The model is always coupled to the language code parameter. There should be
additional parameters to override the model and the model encoding for the case
that somebody wants to specify a custo…
-
```
The TreeTaggerPosLemma annotation always creates POS Tags and Lemmas. In the
case that a corpus is read that already provides POS tags, it would be nice to
only add the lemmas. Thus there should…
-
```
What steps will reproduce the problem?
On the current trunk, trying to bundle the treetagger models fails.
>execute ant local-maven
BUILD FAILED
de.tudarmstadt.ukp.dkpro.core-asl\de.tudarmstadt…