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

Separate muxed/memory fonts from system fonts #761

Open
rcombs opened this issue May 15, 2024 · 0 comments
Open

Separate muxed/memory fonts from system fonts #761

rcombs opened this issue May 15, 2024 · 0 comments
Labels

Comments

@rcombs
Copy link
Member

rcombs commented May 15, 2024

It'd be useful to explicitly distinguish fonts that were muxed into the video file from fonts that we retrieved from a provider. By default, I think we should always prioritize name-matching memory fonts over system-provided fonts, even if the system-provided one is a closer match metrics-wise.

This should help protect against cases where a file's author had one weight of a font installed (and muxed it), but the user had another that matched the requested metrics more closely (this is quite common with weights, as typesetters often don't set \b to match the weight of the font they're requesting; there've also been cases where an author used faux-italics, not realizing that an actual italic version of the same font also existed).

This is technically distinct from VSFilter's behavior, but font provider stuff always is; this just affects the "effective set of installed fonts".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants