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

Warning: Careful using a custom tokenizer... #122

Open
PetrochukM opened this issue Sep 15, 2020 · 0 comments
Open

Warning: Careful using a custom tokenizer... #122

PetrochukM opened this issue Sep 15, 2020 · 0 comments

Comments

@PetrochukM
Copy link

I tried to use the spaCy tokenizer, nltk word_tokenizer, sacremoses MosesTokenizer, nltk TreebankWordTokenizer, and nltk TweetTokenizer.

For this example, "inch BBL, unquote, cost $29.95" they will all output ['inch', 'BBL', ',', 'unquote', ',', 'cost', '$', '29.95', '.']. This output is incompatible with normalise because it'll predict "inch B B L, unquote, cost $twenty nine point nine five.".

@PetrochukM PetrochukM changed the title Careful using a custom tokenizer... Warning: Careful using a custom tokenizer... Sep 15, 2020
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

1 participant