Update README and add utility for generating Table Keyed (Non Glyph) encoder configs #110
+510
−84
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
Allows it to be reused across utilities.
…issed codepoints to generate_table_keyed_config.
- Add examples of generating encoder configs. - Add a status section. - Add a section on how to generate compile_commands.json
skef
approved these changes
Mar 13, 2025
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.
The idea being that you can concatenate a table keyed config and a glyph keyed config (for example from closure_glyph_keyed_segmenter_util) to produce a completed mixed mode IFT encoder config.
Also this updates the README to add some examples of how configs can be generated.