GlyphRun support #2387
Closed
GlyphRun support #2387
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
…/Avalonia into feature/SkiaTextLayout
…/Avalonia into feature/SkiaTextLayout
|
This was merged into the TextLayout branch |
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.
What does the pull request do?
It adds GlyphRun support to Avalonia
What is the current behavior?
Not supported
What is the updated/expected behavior with this PR?
The ability to work with low-level glyph renderings.
How was the solution implemented (if it's not obvious)?
GlyphTypeface was added to access a font's glyph data. This also makes it possible to map characters to glyphs. In theory, we could introduce a text formatter that is producing glyph runs. That formatter would look like the new skia text layout but would work for all platforms.
Checklist
Depends on #1950
#129
#132