Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support bitmap fonts #641

Merged
merged 22 commits into from
Aug 21, 2024
Merged

Support bitmap fonts #641

merged 22 commits into from
Aug 21, 2024

Conversation

DJMcNab
Copy link
Member

@DJMcNab DJMcNab commented Jul 25, 2024

Resolve bitmap Emoji fonts at scene construction time (rather than the ideal resolve time for glyph caching) for expedience.

Current status: Layout details aren't entirely correct

@DJMcNab DJMcNab requested a review from dfrg July 25, 2024 11:10
Copy link
Member

@xStrom xStrom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is any license issue here. Our licenses match exactly, and we already have Google LLC code in the repo as-is.

I think our generic LICENSE-MIT is sufficient. We can also add Colin Rothfels to our AUTHORS file, even though that doesn't have an impact on copyright.

Thus I think we should just keep it simple, use our standard copyright header, not modify the copyright check, not add LICENSE-MIT-SKRIFA, and not worry about making changes to the bitmap.rs file.

vello/src/scene/bitmap.rs Outdated Show resolved Hide resolved
.github/copyright.sh Outdated Show resolved Hide resolved
@@ -511,7 +511,8 @@ impl<'a> DrawGlyphs<'a> {

if !mask.is_packed {
// TODO: Error once?
log::warn!("Unpacked mask data not handled");
log::warn!("Unpacked mask data in font not yet supported");
// TODO: How do we get the font name here?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we were using tracing, we'd be able to have some context data around that made this more clear, perhaps? (Clearly not a thing for this PR to solve.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect that getting that information "just-in-case" all the time would be too expensive. This is a potentially hot-spot in the API.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, it would be somewhere further up the call stack, although for fonts, maybe not quite far enough.

@DJMcNab DJMcNab force-pushed the fontmap branch 2 times, most recently from 6a9c135 to 337d044 Compare August 2, 2024 10:56
@xorgy xorgy self-requested a review August 20, 2024 20:03
@DJMcNab DJMcNab enabled auto-merge August 21, 2024 07:57
@DJMcNab DJMcNab added this pull request to the merge queue Aug 21, 2024
Merged via the queue into linebender:main with commit 3c8dc79 Aug 21, 2024
17 checks passed
@DJMcNab DJMcNab deleted the fontmap branch August 21, 2024 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants