You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@opennlp.apache.org by "Rogério Pereira Araújo (JIRA)" <ji...@apache.org> on 2012/10/23 16:53:12 UTC
[jira] [Created] (OPENNLP-542) Missing arguments for
TokenNameFinderConverter
Rogério Pereira Araújo created OPENNLP-542:
----------------------------------------------
Summary: Missing arguments for TokenNameFinderConverter
Key: OPENNLP-542
URL: https://issues.apache.org/jira/browse/OPENNLP-542
Project: OpenNLP
Issue Type: Bug
Components: Command Line Interface
Reporter: Rogério Pereira Araújo
The documentation gives this example of command line for TokenNameFinderConverter
bin/opennlp TokenNameFinderConverter ad -encoding ISO-8859-1 -data amazonia.ad \ -lang pt -types per > corpus.txt
But for apache-opennlp-1.5.2-incubating the tool is reporting the following:
Usage: opennlp TokenNameFinderConverter ad -encoding encoding -data sampleData
Arguments description:
-encoding encoding
-data sampleData
Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-542) Missing arguments for
TokenNameFinderConverter
Posted by "Rogério Pereira Araújo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484877#comment-13484877 ]
Rogério Pereira Araújo commented on OPENNLP-542:
------------------------------------------------
It would be nice to have this info available on site.
> Missing arguments for TokenNameFinderConverter
> ----------------------------------------------
>
> Key: OPENNLP-542
> URL: https://issues.apache.org/jira/browse/OPENNLP-542
> Project: OpenNLP
> Issue Type: Bug
> Components: Command Line Interface
> Reporter: Rogério Pereira Araújo
>
> The documentation gives this example of command line for TokenNameFinderConverter
> bin/opennlp TokenNameFinderConverter ad -encoding ISO-8859-1 -data amazonia.ad \ -lang pt -types per > corpus.txt
> But for apache-opennlp-1.5.2-incubating the tool is reporting the following:
> Usage: opennlp TokenNameFinderConverter ad -encoding encoding -data sampleData
> Arguments description:
> -encoding encoding
> -data sampleData
> Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-542) Missing arguments for
TokenNameFinderConverter
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484760#comment-13484760 ]
Joern Kottmann commented on OPENNLP-542:
----------------------------------------
Yes, they are also deployed to the maven SNAPSHOT repo. It should be possible to depend on them.
Have a look at builds.apache.org.
The build is triggered by subversion changes.
> Missing arguments for TokenNameFinderConverter
> ----------------------------------------------
>
> Key: OPENNLP-542
> URL: https://issues.apache.org/jira/browse/OPENNLP-542
> Project: OpenNLP
> Issue Type: Bug
> Components: Command Line Interface
> Reporter: Rogério Pereira Araújo
>
> The documentation gives this example of command line for TokenNameFinderConverter
> bin/opennlp TokenNameFinderConverter ad -encoding ISO-8859-1 -data amazonia.ad \ -lang pt -types per > corpus.txt
> But for apache-opennlp-1.5.2-incubating the tool is reporting the following:
> Usage: opennlp TokenNameFinderConverter ad -encoding encoding -data sampleData
> Arguments description:
> -encoding encoding
> -data sampleData
> Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-542) Missing arguments for
TokenNameFinderConverter
Posted by "Aliaksandr Autayeu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482450#comment-13482450 ]
Aliaksandr Autayeu commented on OPENNLP-542:
--------------------------------------------
Workaround: use development version, 1.5.3
> Missing arguments for TokenNameFinderConverter
> ----------------------------------------------
>
> Key: OPENNLP-542
> URL: https://issues.apache.org/jira/browse/OPENNLP-542
> Project: OpenNLP
> Issue Type: Bug
> Components: Command Line Interface
> Reporter: Rogério Pereira Araújo
>
> The documentation gives this example of command line for TokenNameFinderConverter
> bin/opennlp TokenNameFinderConverter ad -encoding ISO-8859-1 -data amazonia.ad \ -lang pt -types per > corpus.txt
> But for apache-opennlp-1.5.2-incubating the tool is reporting the following:
> Usage: opennlp TokenNameFinderConverter ad -encoding encoding -data sampleData
> Arguments description:
> -encoding encoding
> -data sampleData
> Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-542) Missing arguments for
TokenNameFinderConverter
Posted by "Rogério Pereira Araújo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484638#comment-13484638 ]
Rogério Pereira Araújo commented on OPENNLP-542:
------------------------------------------------
Only available at svn or is there any daily/nightly builds?
> Missing arguments for TokenNameFinderConverter
> ----------------------------------------------
>
> Key: OPENNLP-542
> URL: https://issues.apache.org/jira/browse/OPENNLP-542
> Project: OpenNLP
> Issue Type: Bug
> Components: Command Line Interface
> Reporter: Rogério Pereira Araújo
>
> The documentation gives this example of command line for TokenNameFinderConverter
> bin/opennlp TokenNameFinderConverter ad -encoding ISO-8859-1 -data amazonia.ad \ -lang pt -types per > corpus.txt
> But for apache-opennlp-1.5.2-incubating the tool is reporting the following:
> Usage: opennlp TokenNameFinderConverter ad -encoding encoding -data sampleData
> Arguments description:
> -encoding encoding
> -data sampleData
> Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-542) Missing arguments for
TokenNameFinderConverter
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484879#comment-13484879 ]
Joern Kottmann commented on OPENNLP-542:
----------------------------------------
Yes, I agree, if you want to add it please open a jira issue for it and attach a patch to it with an update for our website.
> Missing arguments for TokenNameFinderConverter
> ----------------------------------------------
>
> Key: OPENNLP-542
> URL: https://issues.apache.org/jira/browse/OPENNLP-542
> Project: OpenNLP
> Issue Type: Bug
> Components: Command Line Interface
> Reporter: Rogério Pereira Araújo
>
> The documentation gives this example of command line for TokenNameFinderConverter
> bin/opennlp TokenNameFinderConverter ad -encoding ISO-8859-1 -data amazonia.ad \ -lang pt -types per > corpus.txt
> But for apache-opennlp-1.5.2-incubating the tool is reporting the following:
> Usage: opennlp TokenNameFinderConverter ad -encoding encoding -data sampleData
> Arguments description:
> -encoding encoding
> -data sampleData
> Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira