Glyph Shaping #81
Draft
Glyph Shaping #81
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
- Remove stb_ttf implementation
…ndled differently on native and wasm sides
martinfouilleul
force-pushed
the
martin/text-layout
branch
from
ca45818 to
13f537f
Compare
martinfouilleul
force-pushed
the
martin/text-layout
branch
from
4a86225 to
d8b9c95
Compare
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.
This PR integrates harfbuzz to do glyph shaping on single-script runs. It also changes the text APIs so that you can create shaped
oc_glyph_runs from a unicode string and shaping settings. You can then use these runs to measure text, figure out where a caret should land / which grapheme was clicked, draw the run at some size, etc.(part of #77)