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

feat(reason-skia): bind to FontManager matchFamilyCharacterStyle #939

Merged
merged 5 commits into from
Jul 6, 2020

Conversation

zbaylin
Copy link
Member

@zbaylin zbaylin commented Jul 3, 2020

This does some non-traditional Caml operations like shifting/or-ing bits. I think I got it all right, but if not, please let me know! I'll add some examples to SkiaFontManagerCli for it.

@zbaylin zbaylin requested a review from bryphe July 6, 2020 16:23
Comment on lines +101 to +108
let maybeTypeface =
FontManager.matchFamilyStyleCharacter(
fontManager,
"Arial",
style,
["en_US"],
char,
);
Copy link
Member

Choose a reason for hiding this comment

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

Awesome!

Does this work on all platforms? If so - we might want to add a test case for this, too!

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'm actually not sure! We'll see when CI is finished, I guess!

Copy link
Member Author

Choose a reason for hiding this comment

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

Actually it looks like it does! The hard part about adding tests for it is Linux -- CI gives DejaVu Sans, but Im not sure what other distros will return. What do you think is the best course of action?

@zbaylin zbaylin merged commit ad7ebef into master Jul 6, 2020
@Et7f3 Et7f3 deleted the feat/reason-skia/match-family-character-style branch May 6, 2021 13:31
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.

2 participants