We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.7.3dev
3.24.0dev
It does not happen when stopwords from NLTK are used - the problem is spaces beside the stopwords.
Read some data with Import documents and connect with Preprocess Text widget. Observe the output of Preprocess Text widget.
The text was updated successfully, but these errors were encountered:
@PrimozGodec So in essence NLTK has the wrong stopwords? 😱
Sorry, something went wrong.
They have additional space after each stopword. It at least holds for the Slovene language. The fix for this is in #456
I opened the issue on NLTK nltk/nltk_data#139, anyway I think #456 can be a quick fix. I think it is an OK solution since it is linear.
Successfully merging a pull request may close this issue.
Text version
0.7.3dev
Orange version
3.24.0dev
Expected behavior
Actual behavior
It does not happen when stopwords from NLTK are used - the problem is spaces beside the stopwords.
Steps to reproduce the behavior
Read some data with Import documents and connect with Preprocess Text widget. Observe the output of Preprocess Text widget.
Additional info (worksheets, data, screenshots, ...)
The text was updated successfully, but these errors were encountered: