First version of the tokenizer #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arsduo
force-pushed
the
first-go
branch
2 times, most recently
from
7425d0a
to
187fd92
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the first version of the tokenizer! It can take in texts and split them apart into words, each containing punctuation and sentence flow information.
While the tokenizer has several important gaps (as described in the readme) but should be sufficient to integrate into Markovian's text parsing without any loss of functionality. The Markov text can then start incorporating punctuation and sentence start/end data at the same time as the gaps in Tokeneyes get fixed.