Skip to content
New issue

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

Question: Why NLTK TweetTokenizer? #26

Open
freecraver opened this issue Feb 7, 2022 · 2 comments
Open

Question: Why NLTK TweetTokenizer? #26

freecraver opened this issue Feb 7, 2022 · 2 comments

Comments

@freecraver
Copy link

Thanks for your work on this nice project.

I intend to create a library for text simplification, and potentially would like to integrate your package.
The selection of a tokenizer has an impact on the obtained readability scores and I was wondering how you approached this issue.

Was there any specific reason for choosing the Tweet-Tokenizer over e.g. the default/recommended Nltk-Tokenizer which better depicts the Penn Treebank's definition of word-boundaries?

tokenizer = TweetTokenizer()

@cdimascio
Copy link
Owner

@freecraver I'm open to changing the tokenizer. Would you be interested in investigating the effort to switch over?

@freecraver
Copy link
Author

Sure - please check #27 for my suggested changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants