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.

Sign up for GitHub

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

Jump to bottom

Words surrounded by backwards quotation marks causing inaccurate tokenization results #17

Open
rghavimi opened this issue Feb 16, 2023 · 0 comments
Open

Words surrounded by backwards quotation marks causing inaccurate tokenization results #17

rghavimi opened this issue Feb 16, 2023 · 0 comments

Comments

@rghavimi
Copy link

rghavimi commented Feb 16, 2023 •
edited
Loading

It seems that the occurrence of a backwards quotation marks (“end“) in the text causes different tokenization results compared to Python implementations. This is the only inconsistency I've run into thus far. Curious if anyone else has seen similar issues.

Example: “ends -> tokenizes to ##end and ##s instead of ##ends
@rghavimi rghavimi changed the title Backwards quotation mark causing different tokenization results Backwards quotation mark causing inaccurate tokenization results Feb 16, 2023
@rghavimi rghavimi changed the title Backwards quotation mark causing inaccurate tokenization results Words surrounded by backwards quotation marks causing inaccurate tokenization results Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rghavimi