Fix for: 'WARNING: Could not find required font "X", it has not been embedded' #28
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
Fix for fonts not being found due to spaces inside the fontName
Fix for fonts not being found due to spaces inside the fontName
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.
Sometimes an embedded font can't be found because there's a mismatch between OpenFL's registered font names and the 'real' font name.
For example the font 'Arbuckle Remix NF' gets registered as 'ArbuckleRemixNF' and fails this check:
if (alpha.replace(font.fontName, "").substr(0, fontName.length) == fontName)
because 'ArbuckleRemixNF' is not 'Arbuckle Remix NF'.
This pull request takes care of this.