Improve handling of byCapital font sizing #329
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 will allow users to use more precise alignment values, as we skip saving 3 redundant bits in the inheritance BitField.
These bounds should probably be cross-checked with common fonts.
This may seem arbitrary, but note that the [0, 1] range isn't even enough for some fonts—for example, Zapfino would need an offset below zero.
Having another bit or two of precision each would be great for large text. I don't feel qualified to judge the design decisions in BitEncodings, but this may be good to keep in mind for future changes (will
widthFill
/heightFill
still exist, are 12 bits forspacingX
needed…)