Added option to output JSON file describing generated font glyphs and their unicode positions #55
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
…heir unicode positions. Useful for running custom templates after generating new font.
ghost
assigned 
|
A variation of this is now in 1.0.0.pre. |
|
Thanks. 1.0 is looking very promising |
|
👏 |
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.
Useful for providing data to run custom templates after generating new font.
Addresses the underlying issues from #39, #48 and #50
This approach would improve separation of concerns: FontCustom generates font files and data describing the generated font. Responsibility for CSS style/framework, test files, documentation generation, etc can be moved away from FontCustom and the JSON file used to populate any sort of template required, in any language or build system the user requires.