Convert vocabulary for the new tokenizer to JSON #107
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.
The way the vocabulary is currently stored is a huge pain to parse in any language other than Python, so I propose we use something easier to parse but still as simple, like e.g. JSON.
I've made it so that the vocabulary is now encoded as a single map where the key is the token index and the value is the string to which the token corresponds to, or an array for those tokens which do not correspond to valid UTF-8 (basically only the 0x80-0xFF range).
This is how the file with the vocabulary looks like now:
This way I can use the tokenizer vocabulary as-is in my native tokenizer without having to first manually convert it. (And in fact, I updated my tokenizer so now it can load the vocabulary at runtime instead of it being hardcoded.)
Script used to convert the
.txt
into.json
: